2951
Mini-Reviews by Members / Re: Review of VistaDB
« Last post by Ath on June 16, 2011, 01:32 AM »Final Rating 9/10 - a buy rating.You wrote up a fine review wraith, thanks for that.-wraith808 (May 23, 2011, 11:12 PM)
Recent Posts
Final Rating 9/10 - a buy rating.You wrote up a fine review wraith, thanks for that.-wraith808 (May 23, 2011, 11:12 PM)
Attached, please find an attempt at an alternate view of the file in question.Thank you-ewemoa (June 15, 2011, 05:38 AM)
, I'll see if I can maintain this more readable than the txt version... 
. (I'm always the first to admit I can make errors 
)I'm willing to go away and leave you alone.I can handle the pressure-cranioscopical (June 13, 2011, 04:14 PM)
yup yup, thats the one,Ok thanks, I was just being curious-Stephen66515 (June 13, 2011, 09:06 AM)
As I was deleting nodes from the treeview, I tried the Delete key first, then discovered Control+D via the context menu. I got to thinking that I've got these unconscious expectations of shortcut keysAutoIt allows for application wide shortcuts only, for as far as I can see, so I choose Ctrl-D instead of Del, as that's quite indispensable during normal editing.-ewemoa (June 12, 2011, 05:03 PM)
I didn't figure out a way to get buttons to move among groups. Is this intentional?That's been a TODO item for a small while, I'll get to that later this week.-ewemoa (June 12, 2011, 05:03 PM)
I chose File -> New to eventually end up with an empty group. I noticed a Test button in the preview but no listing in the treeview. When I chose "Insert button" from the context menu of the treeview, I expected to see a new node in the treeview, but I didn't see one show up.I'll do some more testing, thought I had all issues here covered, but I may have missed a few situations.-ewemoa (June 12, 2011, 05:03 PM)
using the Arrow Keys, and # is close enough to them to make life very very easy!What kind of keyboard-layout do you use that has # near the arrow keys? (not an expert on keyboard layouts but on my 'standard' US layout, # is more than 3/4 keyboard size away from the arrow keys-Stephen66515 (June 12, 2011, 07:07 PM)
)Could someone with experience in Inno Setup scripting check out the following setup script and see if you can spot what I've done (or failed to do) that's causing the installer not to exit after the user checks the "Launch Hangman" checkbox and then clicks the installer's Finish button?Code: PHP [Select]
from Vista and up Ctrl-A selects the content of the edit. Seems that's a feature since Vista was introducedNot sure if I want to 'fix' that for Windows XP, as it's also not available in any standard Windows input control.-Ath (June 11, 2011, 08:19 AM)
I see we share the same low expectations of my mental facultiesYour reputation of tool-breaker / bug-finder is kindofa public secret around these forums-cranioscopical (June 11, 2011, 09:51 AM)
I was trying to create a button without first creating a group!The actual fix is that I create the (mandatory) '<no group>' treeview item, when you start a new Configuration using File/New. Creating a new group won't help you either, as you prolly have found out by now...-cranioscopical (June 11, 2011, 09:51 AM)
I find that I was expecting to create a panel from scratch using WBE and that I don't know how. This may mean that first I have to read something somewhereThanks for trying WinButtonEdit, I was kinda expecting you to find something-cranioscopical (June 10, 2011, 06:17 PM)
Rather than simply editing what's there (very easy to do with WBE) I wanted to start with a clean slate.I thought I had that all covered during testing, but I wasn't thorough enough it seems.
If I start with an empty .ini I can't use the button fields in WBE so, obviously, I've missed the point.
Looking through the winbuttons.ini, however, I did find one remarkably apposite variable, viz. dummy-cranioscopical (June 10, 2011, 06:17 PM)
Any chance of Control+A selecting all text in text fields?-ewemoa (June 10, 2011, 06:14 PM)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...No scripts running when I tested -- once via a VirtualBox Windows XP SP3 guest and once on a notebook running XP SP3. I hear a sound but there is no selection.)
-Ath (June 11, 2011, 06:27 AM)-ewemoa (June 11, 2011, 07:35 AM)
I'll see what I can come up with, sounds kinda intriguingRegarding 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.-ewemoa (June 10, 2011, 06:14 PM)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?I was thinking it might be nice if it were possible to specify in the configuration that a certain action would be taken upon drop (e.g. execute a command passing the path of what's dropped -- assuming what's dropped has a path or set of paths). Does that make sense?-Ath (June 11, 2011, 06:27 AM)-ewemoa (June 11, 2011, 07:35 AM)
(never did much drag&drop-related stuff)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-ewemoa (June 10, 2011, 06:14 PM)
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)-ewemoa (June 10, 2011, 06:14 PM)
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...-ewemoa (June 10, 2011, 06:14 PM)
)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.-ewemoa (June 10, 2011, 06:14 PM)
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.-ewemoa (June 10, 2011, 06:14 PM)
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> treeviewHm, 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.-ewemoa (June 10, 2011, 06:14 PM)
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"-ewemoa (June 10, 2011, 06:14 PM)
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-ewemoa (June 10, 2011, 06:14 PM)
, 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?-ewemoa (June 10, 2011, 06:14 PM)
Thank you for:Environment variables can be used by using %env.variable%-ewemoa (June 10, 2011, 06:14 PM)
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.-ewemoa (June 10, 2011, 06:14 PM)
Was this a lot of work?Ehm, yes the changelog starts on may 3rd-ewemoa (June 10, 2011, 02:26 AM)
and I worked on it for 1 to 'a few' hours, 3 or four days a week, but the hardest part was taking generated source from Koda (the AutoIt GUI designer) to Scite without all generated errors and unneeded crap . And then you move some controls a few pixels... should lower the barrier-to-entry-ewemoa (June 10, 2011, 02:26 AM)