Disappearing Get File dialog

[BobWilkes]

I know support for SDT ended some time ago, and I'm really glad to see that it's still ticking here, BUT...

I still use it almost daily for table/view definition maintenance and basic run-time tasks such as validating meta data, updating defs & opening tables, reorg & packing data. It's the cat's meow and at the top of the list of items in my tool box, so many thanks and more Kudos!

(I'm too 'old-school' to embrace the newer Db functions, like AutoNumber fields, so it's the perfect tool for me.)

There is one nagging anomaly that I'd like to get rid of but am reluctant to dive into the source code.

(I'm using SDT V 6.2b, which should be the latest official release, and Windows 10, VFP 9 w/ SP2.)

In the development environment, when I open SDT, I get the starting dialog, as expected.

When I click on the folder icon to select a DBCXReg file, the GetFIle dialog appears and immediately runs to the upper left corner of the screen and hides behind the VFP window. (I think it's afraid of the mouse!)

I've gotten past this by keeping my VFP window down from the top of the screen a few pixels, just enough to be able to click on the header of the GetFile dialog, so I can click on it, which brings it back to the foreground.

Sounds like an 'Always On Top' flag isn't set or being honored...

No big deal, just a 'Nag' to consider some rainy day when you've nothing better to 'play' with...

Bob

[DougHennig]

I hadn't noticed that before but now I see it happening too. I wonder if it's a Windows 10 issue; the code displaying that dialog (SFCommonDialog in SFUtility.vcx) uses the Windows API GetOpenFileNameA function in comdlg32.dll. I Googled around a bit but didn't find anything helpful.

[GTGeek88]

Weird that you've never seen that before this post. I've been seeing it for years, but it's not really a big deal since you can pull it up from behind VFP using the Windows taskbar. I kind of assumed something in SDT returned focus to the main SDT window. Seems like it shouldn't. Seems like it's going to simply be waiting on the dialog, but is there a timer, perhaps? Never have looked (see not a big deal mention above). Granted, having it fixed would be nice, too, because it is a great tool that I use day in and day out. :-)

[DougHennig]

I'm not sure how to fix it since it's a Windows dialog called with an API function.