I've just noticed a consistent issue with nearly all the WS/NS browse-type dialogs - no matter what the path is set to in the little path box, whenever I click "browse", the browser always starts at "My Computer". Every time!

Even if I browse to the directory/folder and click "OK" in the Browse For Folder, clicking "Browse" immediately again takes me right back to My Computer.

This happens for almost all browse dialogs (definitely all the browse dialogs in WorkShelf, and for many in NextStart, although Nexus appears to browse to a reasonable default (...\Winstep\Icons), it still doesn't update the default if another path is chosen.

Is this behaviour modifiable? Do others see the same thing? Maybe it's just an XP x64 thing...

Normally, this kind of behaviour is just annoying (a lot of installer packages and windows objects do the same thing), but while I'm in "try things out" mode, I seem to be manually navigating to the same folder in at least 10 different areas of NS/WS.... I know it's possible to set the default in the Windows browse component, but it's a separate step that needs to be taken before instantiating the browser dialog...

Unfortunately the Browse dialog does not remember the last folder. Kind of my fault, no need to blame XP 64 bit this time.

Fixed for the next release!

Thanks so much Jorge! I'm looking forward to all the fixes.

I hope it wasn't OpenFileDialog.InitialDir := CurrentForm.FileEditText.Path....

Nah, I'm using the shell API, had to use a call back procedure:

bi.lpfn = GetAddressofFunction(AddressOf BrowseCallbackProc)

SHBrowseForFolder(bi)

...

and

...

Case BFFM_INITIALIZED
Call SendMessage(hWnd, BFFM_SETSELECTION, 1, m_CurrentDirectory)

I have a letter from my mum for use in case of emergencies:

Dear Sir,

PC Pete is allergic to callback programming in any language, and is unable to properly code in C, C++, C#, or any other real language.

Please excuse him from Windows UI programming.

He can code in Pascal and Machine Language, and he has a Bronze Swimming Certificate.

Signed,
PC Pete's Mum

Ah, Pascal, the second language I learned. So much nicer than Fortran 77 (which was the third).

I actually have a working copy of Borland Turbo Pascal 3.01 on a CP/M box that I keep running for fun. I've even got one of the very few copies of Turbo Pascal 16-bit on a TurboDOS machine as well. And the original TP manual, with the cut-out coupons for TurboPascal for US$49.99

I cut my teeth on Z80 assembler and migrated to TP when it came out. In fact, I've never NOT used some form of TP/Pascal/Delphi in all the years since. That's one of the reasons I like Pascal - I can go back to a 20-year-old application and improve it based on stuff I've learned since.

I did a course on ADA, and played quite a bit with Modula2, but I missed out on FORTH and FORTRAN (which I've regretted ever since). I have copies of most languages still, but most won't run on a 64-bit OS (not a problem with the application/compilers themselves, just the install packages won't run).

I even played a bit with Euphoria and Eiffel, but they turned into corporate monsters that real people couldn't afford. And a smattering of smalltalk, and even Prolog, which I keep meaning to learn, but never get a round tuit. Now, I'm trying to figure out if Ruby will work for future development. It's just hard turning my hardwired Pascal brain into a truly object oriented language like Ruby. Constructs like tuple spaces and concepts like self inheritance just make my eyes water... Must be getting old...

LD HL,16384
LD D,H
LD E,L
INC E
LD BC,6144
XOR A
LD (HL),A
LDIR

Fastest way (if you count the T-Cycles) to clear the screen on a ZX Spectrum.

Now THAT was a blast from the past! I've still got a couple of Microbees in my treasure pile. A 16k and a 256k Colour job. They're all stacked in with the Apple IIe and IIGS, and the Commodore 64 and the Motorola D2 kit. I'm a magpie, my wife just rolls her eyes and keeps nagging me to move it out of the garage and under the house so she doesn't trip over 5 1/4" floppy drives and printers and stuff. Sigh.

Back on topic.....

I've found a couple more bits of hopefully useful information regarding defaults and stuff.

First, WRT the quicklaunch issue, the shortcut properties in NextStart's quicklaunch "import" are correct (they use C:\Program Files\....), but when I try to drag them to another dock, shelf, or anywhere else, the dropped item properties are all reset to C:\Program Files (x86)\...

So I think (!) that somewhere along the line, the drag/drop code is "reinterpreting" the shortcut's path text. Can you check that out? I've got a couple of small screenshots of the property pages before/after if that would help.

BTW, many of the minor issues (like CPU load over time) and some of the instability when a lot of menus were opened and closed, and a lot of small config changes were attempted, seems to have been "fixed" by the new OS install. It's still early days, but so far, I've been thrashing NS and WS, and they've both stayed running and reasonable!