Popup directory history

Jan 15, 2009
16
0
#1
XP SP2 TCC 9.02.155, TCC/LE 11 Build 33

After Installing TCC/LE, and running TCC (9.02.155) at the same time I noticed that in TCC (9.02) if I type the command (for example):

cd temp*

I no longer see a popup directory listing. If I hit enter TCC changes directory as if the popup is completely hidden but functional. Is this an unintended consequence of the "fix" of the TCC/LE 11 build 33 popup directory history that is affecting my TCC 9.02?

Matt
 

rconn

Administrator
Staff member
May 14, 2008
10,551
97
#2
> After Installing TCC/LE, and running TCC (9.02.155) at the same time I
> noticed that in TCC (9.02) if I type the command (for example):
>
> cd temp*
>
> I no longer see a popup directory listing. If I hit enter TCC changes
> directory as if the popup is completely hidden but functional. Is this
> an unintended consequence of the "fix" of the TCC/LE 11 build 33 popup
> directory history that is affecting my TCC 9.02?
No; there's no way it could affect TCC v9. What's more likely is that the
popup window is coming up underneath another window. (This is an
unfortunate Windows bug that shows up from time to time.)

Rex Conn
JP Software
 
Jan 15, 2009
16
0
#3
Strange, my testing of TCC/LE (10.76) with TCC (9.02.156) versus TCC/LE (11.33) with TCC (9.02.156) indicates the behavior I reported. So, I'm not sure what you "fixed" in TCC/LE 11.33 with respect to the dir history popup. On my system the dir history popup problem with TCC (9.02.156) no popup appears at all (ie. it is not "under" any window, it just acts like it is invisible but functional). My system does not have this problem with TCC/LE 10.76 and TCC (9.02.156) running together. Of course, if no interaction is possible.... I'm not sure what to make of it.

Matt


No; there's no way it could affect TCC v9. What's more likely is that the
popup window is coming up underneath another window. (This is an
unfortunate Windows bug that shows up from time to time.)

Rex Conn
JP Software
 
Jan 15, 2009
16
0
#4
Sorry, I may be using the wrong terminology here. It is not the dir "history" popup, but the popup you get when you type:

cd temp*

which maybe is called the "change directory" popup? This loads the directories from jpstree.idx?

Matt

Strange, my testing of TCC/LE (10.76) with TCC (9.02.156) versus TCC/LE (11.33) with TCC (9.02.156) indicates the behavior I reported. So, I'm not sure what you "fixed" in TCC/LE 11.33 with respect to the dir history popup. On my system the dir history popup problem with TCC (9.02.156) no popup appears at all (ie. it is not "under" any window, it just acts like it is invisible but functional). My system does not have this problem with TCC/LE 10.76 and TCC (9.02.156) running together. Of course, if no interaction is possible.... I'm not sure what to make of it.

Matt
 
#5
Matt:

When I type cd temp* nothing happens. Are there additional keystrokes
that you are pressing?

Also, is it true you are running TCC and not TCMD? I'll happily test
your situation if you give a little more detail. I do not have TCC
9.02.156 installed, but do have TCC and TCMD 9.02.157 and TCC/LE
9.02.156


On Wed, Nov 11, 2009 at 11:51 AM, Matt <> wrote:

> Sorry, I may be using the wrong terminology here. *It is not the dir "history" popup, but the popup you get when you type:
>
> cd temp*
>
> which maybe is called the "change directory" popup? *This loads the directories from jpstree.idx?
>
> Matt
>
>
> ---Quote (Originally by Matt)---
> Strange, my testing of TCC/LE (10.76) with TCC (9.02.156) versus TCC/LE (11.33) with TCC (9.02.156) indicates the behavior I reported. *So, I'm not sure what you "fixed" in TCC/LE 11.33 with respect to the dir history popup. *On my system the dir history popup problem with TCC (9.02.156) no popup appears at all (ie. it is not "under" any window, it just acts like it is invisible but functional). My system does not have this problem with TCC/LE 10.76 and TCC (9.02.156) running together. *Of course, if no interaction is possible.... I'm not sure what to make of it.
>
> Matt
> ---End Quote---
>
>
>
>


--
Jim Cook
2009 Saturdays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Sunday.
 

rconn

Administrator
Staff member
May 14, 2008
10,551
97
#7
> ---Quote (Originally by Matt)---
> Strange, my testing of TCC/LE (10.76) with TCC (9.02.156) versus TCC/LE
> (11.33) with TCC (9.02.156) indicates the behavior I reported. So, I'm
> not sure what you "fixed" in TCC/LE 11.33 with respect to the dir
> history popup. On my system the dir history popup problem with TCC
> (9.02.156) no popup appears at all (ie. it is not "under" any window,
> it just acts like it is invisible but functional). My system does not
> have this problem with TCC/LE 10.76 and TCC (9.02.156) running
> together. Of course, if no interaction is possible.... I'm not sure
> what to make of it.
> ---End Quote---
Barring an unbelievably catastrophic Windows bug, there's no way for two
versions of TCC to interfere with each other in that fashion.

What you may be seeing is your .INI files interfering. A "cdd temp*" by
itself will never display any popup. However, if you have Extended
Directory Search enabled, doing a "cdd temp*<return>" will display a popup
if you have more than one matching directory. Run the OPTION command, go to
the "Command Line" page, and see what you have set for your Extended
Directory Search / Search Level.

Rex Conn
JP Software
 
Jan 15, 2009
16
0
#8
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 10"><meta name="Originator" content="Microsoft Word 10"><link rel="File-List" href="file:///C:%5Ctemp%5Cmsohtml1%5C01%5Cclip_filelist.xml"><!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:Compatibility> <w:BreakWrappedTables/> <w:SnapToGridInCell/> <w:WrapTextWithPunct/> <w:UseAsianBreakRules/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><style> <!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman";} </style> <![endif]--> XP SP2, TCC (9.02.156), TCC/LE (10.76), TCC/LE (11.33)
<o:p> </o:p>
Thanks to everyone who has commented. Ok, I think I have the terminology down. I have been describing a problem I am having with extended directory search popup. For the above products (and versions) I have my “search level” set to 2. For a good part of the last year I have used TCC (9.02) to control the size of the extended directory search popup for TCC/LE (10). The only guess I have of how this might work is that TCC (9.02) writes the size and placement information to the registry and TCC/LE (10) reads the size and placement from the registry. Maybe this technique is just a coincidence and not a cause and effect. In any case, it worked. It no longer seemed to work for TCC/LE (11.33). In addition, using TCC/LE (11.33) and TCC (9.02.156) at the same time seems to make the popup “invisible” for TCC (9.02) but still functional. In other words, I can arrow up and down the invisible directory popup list (obviously I cannot tell which entry I am on) and when I press enter I change to a directory in the invisible popup list. I do have an alias for ‘cd’ which is ‘cd /d’ which I have used for a long, long time. I just tried the command “cdd *temp” (without the quotes) and it works (ie the extended search popup pops up in TCC (9.02)); so it must be an issue with my ‘cd’ alias combined with some fix for TCC/LE (11.33) that somehow finds its way back to effect TCC (9.02).
Or not!

<o:p> </o:p>
Matt


Barring an unbelievably catastrophic Windows bug, there's no way for two
versions of TCC to interfere with each other in that fashion.

What you may be seeing is your .INI files interfering. A "cdd temp*" by
itself will never display any popup. However, if you have Extended
Directory Search enabled, doing a "cdd temp*<return>" will display a popup
if you have more than one matching directory. Run the OPTION command, go to
the "Command Line" page, and see what you have set for your Extended
Directory Search / Search Level.

Rex Conn
JP Software
</return>
 

rconn

Administrator
Staff member
May 14, 2008
10,551
97
#9
> Thanks to everyone who has commented. Ok, I think I have the
> terminology down. I have been describing a problem I am having with
> extended directory search popup. For the above products (and versions)
> I have my "search level" set to 2. For a good part of the last year I
> have used TCC (9.02) to control the size of the extended directory
> search popup for TCC/LE (10). The only guess I have of how this might
> work is that TCC (9.02) writes the size and placement information to
> the registry and TCC/LE (10) reads the size and placement from the
> registry. Maybe this technique is just a coincidence and not a cause
> and effect. In any case, it worked. It no longer seemed to work for
> TCC/LE (11.33). In addition, using TCC/LE (11.33) and TCC (9.02.156)
> at the same time seems to make the popup "invisible" for TCC (9.02) but
> still functional. In other words, I can arrow up and down the
> invisible directory popup list (obviously I cannot tell which entry I
> am on) and when I press enter I change to a directory in the invisible
> popup list. I do have an alias for 'cd' which is 'cd /d' which I
> have used for a long, long time. I just tried the command "cdd *temp"
> (without the quotes) and it works (ie the extended search popup pops up
> in TCC (9.02)); so it must be an issue with my 'cd' alias combined with
> some fix for TCC/LE (11.33) that somehow finds its way back to effect
> TCC (9.02).
> Or not!
The CDD popup window position & size is saved in the .INI file, not the
registry.

A couple of years ago, the popup window arguments were changed from
row/colum to x/y pixel coordinates.

Look at your TCMD.INI and see what the CDDWinLeft / CDDWinTop / CDDWinWidth
/ CDDWinHeight values are. If you want to reset them to the default values,
delete those lines & TCC will recreate them when you size a CDD window.

Note that it's really *not* a very good idea to try to use the same .INI
file for multiple versions. As new directives are added or modified &
obsolete ones deleted, you're going to see a lot of errors whenever you
start a new TCC session.

Rex Conn
JP Software
 

samintz

Scott Mintz
May 20, 2008
1,270
11
Solon, OH, USA
#10
Didn't the jpstree.idx file format change between version 9 and 10? Is it
possible he's attempting to use a V11 database due to a shared INI file?

-Scott

Matt <> wrote on 11/11/2009 08:33:30 PM:


> XP SP2, TCC (9.02.156), TCC/LE (10.76), TCC/LE (11.33)
> > >
> Thanks to everyone who has commented. Ok, I think I have the
> terminology down. I have been describing a problem I am having with
> extended directory search popup. For the above products (and
> versions) I have my ?search level? set to 2. For a good part of the
> last year I have used TCC (9.02) to control the size of the extended
> directory search popup for TCC/LE (10). The only guess I have of how
> this might work is that TCC (9.02) writes the size and placement
> information to the registry and TCC/LE (10) reads the size and
> placement from the registry. Maybe this technique is just a
> coincidence and not a cause and effect. In any case, it worked. It
> no longer seemed to work for TCC/LE (11.33). In addition, using
> TCC/LE (11.33) and TCC (9.02.156) at the same time seems to make the
> popup ?invisible? for TCC (9.02) but still functional. In other
> words, I can arrow up and down the invisible directory popup list
> (obviously I cannot tell which entry I am on) and when I press enter
> I change to a directory in the invisible popup list. I do have an
> alias for ?cd? which is ?cd /d? which I have used for a long, long
> time. I just tried the command ?cdd *temp? (without the quotes) and
> it works (ie the extended search popup pops up in TCC (9.02)); so it
> must be an issue with my ?cd? alias combined with some fix for
> TCC/LE (11.33) that somehow finds its way back to effect TCC (9.02).
> Or not!
>
> > >
> Matt
>

> Quote:
>
> Originally Posted by rconn [image removed]
> Barring an unbelievably catastrophic Windows bug, there's no way for two
> versions of TCC to interfere with each other in that fashion.
>
> What you may be seeing is your .INI files interfering. A "cdd temp*" by
> itself will never display any popup. However, if you have Extended
> Directory Search enabled, doing a "cdd temp*" will display a popup
> if you have more than one matching directory. Run the OPTION command, go
to

> the "Command Line" page, and see what you have set for your Extended
> Directory Search / Search Level.
>
> Rex Conn
> JP Software
>
>
>
 
Jan 15, 2009
16
0
#11
Just to clear up a few issues. Each of my JPSoft install directories (for TC 9, TCC/LE 10 and TCC/LE 11) each have their own TCMD.INI file so I don't think I'm sharing an ini file. And the option command for versions 10 and 11 of TCC/LE point to their respective TCMD.INI files.
Also I ran TC (9.02) (which I rarely use, I use TCC) and its extended dir search popup was left and pushed up so that 90% of it was off the screen. I managed to drag and resize the popup which seems to have corrected the TCC popup. So, maybe the TC popup was affecting the placement of the TCC popup (ie. making it completely off the screen). So, what I thought were related events where most likely just highly correlated.

Thanks again to everyone who took the time to try and assist.

Matt



Didn't the jpstree.idx file format change between version 9 and 10? Is it
possible he's attempting to use a V11 database due to a shared INI file?

-Scott

Matt <> wrote on 11/11/2009 08:33:30 PM:






to