So I've been trying out the editor (according to the about box, I see 0.8.1.0) a bit and have some initial feedback:
Great, thanks for this extensive feedback
I found choosing a color via the "Change..." button for Color to not work if starting with a blank value (no value got filled in to the text field for Color:), while I found that the corresponding choosing sequence of actions for Textcolor did work.
I can see no difference for these two buttons (not in code, nor when testing), but when 'creating' a custom color, it needs to be added to the colorset by using the button 'Add to Custom Colors' before it will stick. (This has been tested quite extensive before release. It uses the standard AutoIt Color Selection Dialog with any of it's 'peculiarities' that I can't do much about)
Any chance of Control+A selecting all text in text fields?
Eh, it does what you expect on my system, and I have done nothing in WBE to enable or disable that. Got another script catching ^A, perhaps? (AKA: Works on my machine...
I accidentally opened the WinButtonEdit.ini in the editor -- not a good idea right? Any chance of some kind of warning or protection?
I'll add a check/warning in the next release.
I see that clicking on a button in the preview will select a node in the tree -- except it doesn't appear to work for the Pink-Online button in <no group> in my default WinButtons.ini.
Correct. That button in the preview is disabled (that should be visible...) by a Condition, so the OnClick doesn't fire. In the Options menu there's ''Assume all Conditions True (not saved)" just for that. The 'not saved' part tells that this setting isn't persistent between sessions of WBE.
In the tree view, multiple nodes appear selected sometimes: view WinButtons.ini, choose <no group>, ensure the corresponding treeview is expanded, choose scite, ensure the corresponding treeview is expanded, click on the 'Push 1ce' button in the preview, click on the Notepad node under the <no group> treeview
Hm, another case of 'Works on my machine...' weird. I do the de-selection and selection of treenodes using standard AU3 included functions, and can not see what you describe. I'll test some more, and add a small delay in between, that might improve things.
Could be something with the OS/Video drivers, what's your configuration? (Tested with Win7 with Aero on nVidia GTS 250 with drivers 126.96.36.19996.)
Also tested on WinXP running on VMWare and on 125%/120 DPI, and I see some odd behavior there. I'll try to fix that, if possible. The treeview control is a nasty beast sometimes, I've seen in the past
When I open WinButtons.ini, initially I don't see a + expander next to the scite group in the left pane. When I select the scite group though, the + expander appears.
I've seen that and don't know how to solve it. The + expander appears when I move my mousepointer over it (on Win7). The current 'workaround' is to set option "Expand all button groups after load"
On WinXP I can duplicate this issue, I'll try to fix this if possible, too.
When there isn't much space in the preview, is there a good way to move it without accidentally pushing the buttons that fill most of the space?
Besides aiming very accurately
, you could enable "Show Window Border" and "Display Windows Close button" in the "Global parameters" tab, so the default 'handles' appear, or increase the "Button margin" value a bit. For this reason I've positioned the preview by default on the right/top side of WBE (instead of the runtime position for WinButtons), so it isn't covering any part of WBE.
Regarding WinButtons itself, is there any support for dropping things on to buttons? I searched for relevant information in this topic and WinButtons.Readme.txt unsuccessfully.
WinButtons is not a drop-target, but I could add that if you want/need it. Could you give a more elaborate description for what/how you'd expect to happen there?
Thank you for:
Environment variables can be used by using %env.variable%
That's just the default Environment variables expansion available in AutoIt. It was a 'nice to have' feature and quite easy to add
I didn't find it in the docs, but by looking at the samples I noticed that it looks like one can use relative paths.
Yep, I try to use a relative path after the executable file for WinSendKeys is picked using the file-browse dialog. It's not in the same subdirectory on my system, as the sample shows. The Run/RunWait AutoIt function is quite flexible in this.
I'll try to release an updated version this weekend.