Recent Posts
The problem was that the disk image was being mounted on the sata controller. When I mounted it on the IDE controller it worked.
Changed File/New to do nothing if Cancel was clicked on the Save File dialog
Improved File Selection (Open/Save) dialogs to include *.wbuc + *.ini and *.* selections and each choice separate
Fixed Drag&Drop ignored .ini files-Ath
Windows Virtual PC VHDs for testing websites with different Internet Explorer versions [Last Updated: 5/01/11]
The password to login to all of these images is Password1 and the username will be present when you first login.
*Note: You may be required to activate the OS as the product key has been deactivated. This is the expected behavior. The VHDs will not pass genuine validation. Immediately after you start the Windows 7 or Windows Vista images they will request to be activated. You can cancel the request and it will login to the desktop. You can activate up to two “rearms” (type slmgr –rearm at the command prompt) which will extend the trial for another 30 days each time OR simply shutdown the VPC image and discard the changes you’ve made from undo disks to reset the image back to its initial state. By doing either of these methods, you can technically have a base image which never expires although you will never be able to permanently save any changes on these images for longer than 90 days.
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...They are both there-ewemoa (June 19, 2011, 05:55 AM)-Ath (June 19, 2011, 07:04 AM)
Maybe I should add *.* to that dialog too?I don't have an opinion on this...yet-Ath
Ah, the joys of backward-compatibility...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...-ewemoa (June 18, 2011, 04:52 PM)-Ath (June 19, 2011, 04:01 AM)
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.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.-Ath-ewemoa (June 18, 2011, 04:52 PM)-Ath
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...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-ewemoa (June 18, 2011, 04:52 PM)
If preferred I could add 'Edit with WinButtonEdit' to the context menu in Explorer? (And change 'Open' to 'Open with WinButtonEdit')-Ath
Preferred file extension changed from .ini to .wbuc (WinButtons Configuration)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?-Ath (June 18, 2011, 02:31 PM)
WinButtonEdit 0.9.0.0 (RC6)This worked for me.
Buttons can now be moved between groups (Treeview context menu)-Ath
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.-Ath
Sorry if my phrasing was unclear / wrong. Do you think this "drop on to .exe" feature is a possibility?I've been using a little freebie called BatchCompiler for some years, as a way to lock down batchfiles against casual modification and ensure maximum portability. (Can't remember where I got it now, and the readme only quotes the author's name -- Ricardo Arias -- but hey, Google is your friend.)Apparently, I wasn't Google's really good friend today-oblivion (June 17, 2011, 07:47 AM)
I think the former would be more useful, but wonder about the potential persistence-consistency issue for multiple instances of WBE running...When I wrote my request, I was sloppy in my wording. What I had in mind might be more accurately described by:BTW, any chance of being able to drop WinButtons config files on WinButtonEdit.exe to have the config file opened up in WBE?Would you expect it to run 3 instances of WBE, if 3 files are dropped on a single instance, or just open the first and ignore the rest?-ewemoa (June 16, 2011, 04:22 PM)-Ath (June 17, 2011, 12:10 PM)
The book "Windows NT Shell Scripting" by Timothy Hill has about the best coverage of how to do complex processing with batch files that I've come across (get a used/remaindered one for the cost of shipping).-mwb1100 (June 17, 2011, 02:15 AM)
AutoHotKey (and friends) is one of the exceptions as I understand it - build the script to an exe and nothing else is needed on the end-user's machine (I imagine that's one of the reasons it's quite popular on DC's coding snacks).-mwb1100
So, a usable solution for the non-functional Close button on Windows XP was found: It shouldn't be combined with the movable option.
In this particular case (XP, and options: border, closebutton and movable) the movable option is ignored. 'movable' was originally implemented to be able to move a border-less WinButtons window, but the caption bar is available so the window can still be moved around the screen (the movable option could easily be mis-interpreted)
-Ath (June 16, 2011, 06:05 PM)
Also fixed was the defective :dropItem1: feature-Ath
I'll be searching for a final solution for this Closebutton/movable/Windows XP combination-issue...-Ath
I can find no issues with either the Close button or pressing <Esc> with WinButtons having focus. Is there perhaps an extra (older) instance of WinButtons running that's waiting for a condition/hanging/cycling perpetually? (You could check that using Process Explorer or Task manager)I don't think there was, and I reproduced the issue just now. I am also running XP SP3. Similar results to cranioscopical -- pressing the escape key works while clicking on the close button doesn't seem to.-Ath (June 16, 2011, 02:18 PM)
Update will be posted later this evening.
