If .wbuc is now the preferred file extension, do you think it would make sense for the default WinButtons.ini to be renamed to use the new file extension?I didn't do that on purpose, as users would be surprised to see the original WinButtons configuration where they may have created a personal one with the old filename, and the .wbuc file gets preference...
Ah, the joys of backward-compatibility...
On a related note, are there some reasons why it is that some of the dialogs for WBE don't have both *.wbuc and *.ini for their value in "Save as type"? For example, "New" and "Save as..." both lead to one where the value is only *.wbuc...
Ah, btw, choosing File -> New and then pressing the Cancel button leads to the file dialog appearing again here...I get a feeling of Deja Vu.
It should work equally well for both .wbuc and .ini files (these are the only supported extensions, ATM).
WBE supports Drag&Drop, configurable for either a single file or multiple files into multiple (new) WBE sessions (details in the readme)This works for me sometimes. My current guess is that it works for .wbuc files but not .ini files.
I'm sorry to say that it doesn't seem to work here for ini files that I have tried. I created a file via WBE called "Test.ini" (a new file, one button, saved as "Test.ini", quit WBE, open WinButtons.ini, then drop "Test.ini" on to the treeview). Whether the "Multiple files dropped..." is enabled or disabled appears to make no difference.
I tried opening various appropriate *.ini files manually (works fine -- e.g. start with the newly created Test.ini), then followed this by dropping any of the other appropriate *.ini files on to the treeview -- the result was no change in the treeview.
Do you think this "drop on to .exe" feature is a possibility?I'd have to figure out how to do that, I'm not familiar with that feature (aka: I never open files that way myself). If the file association is set to open with WBE, a double click would suffice
If preferred I could add 'Edit with WinButtonEdit' to the context menu in Explorer? (And change 'Open' to 'Open with WinButtonEdit')
Hmm...well if it's too much trouble, please punt on it (at least for now...). Since I don't do file associations because of the registry involvement, context menu entries in Windows Explorer fall under the same class of things I don't go for either, so unless someone else asks for it...