v1.0.44 released: New GUI controls: TreeView and Status Bar
Fixed OnClipboardChange to work even when the script is displaying a MsgBox or other dialog.
Fixed FileCreateDir not to report ErrorLevel 1 when the specified directory ends in "\". [thanks Wesley]
Fixed hotkeys Control::, Shift::, and Alt:: to fire on release of the key rather than press-down (broken by v1.0.41).
Fixed loading of icon #1 from nonstandard file types such as .bin.
Fixed ListView creation to obey the text color set by "Gui Font".
Changed and fixed the hotkey tilde prefix (~) so that hotkeys like ~Esc and Esc are considered duplicates; that is, a script cannot define both ~Esc and Esc unless they are under different #IfWin criteria (in which case ~Esc and Esc have been fixed to work properly). [thanks jballi]
Changed and improved ListViews: 1) a new option WantF2 is in effect by default, which causes an F2 keystroke to edit the current row (when not ReadOnly); 2) added LV_Modify(Row, "Vis") to scroll an item into view; 3) drag notifications occur even without AltSubmit; 4) item-change notifications have A_EventInfo set to the row number; 5) ErrorLevel no longer mirrors A_EventInfo in cases where it was never documented to do so (same for GuiContextMenu).
Improved Edit controls to select all text in response to Control-A. This can be disabled via -WantCtrlA.
Added new GUI control types TreeView and StatusBar.
The select all hotkey in Edit controls are fantastic, they make a lot of things so much easier.
Thanks Chris, great job.
autohotkey.com/net Site Manager
Contact me by email (polyethene at autohotkey.net) or message tidbit
Using "Gui, Add, TreeView, -Lines +Buttons" I don't see the buttons?Buttons: Specify -Buttons (minus Buttons) to avoid displaying a plus or minus button to the left of each item that has children.
Lines: Specify -Lines (minus Lines) to avoid displaying a network of lines connecting parent items to their children.
autohotkey.com/net Site Manager
Contact me by email (polyethene at autohotkey.net) or message tidbit
Ah, that's a limitation of the control that should have been documented. I've added the following: "However, specifying -Lines also prevents the plus/minus buttons from being shown for top-level items.""Gui, Add, TreeView, -Lines +Buttons" I don't see the buttons?
Thanks.
I updated my ahk.properties file in AutoHotkey.net (for the newest lexer, I no longer maintain the old, asm-based one).
I will explore the new GUI capabilities.
there's a bug with the statusbar and updown-controls:
#persistent Gui, 1:Default Gui,Show,h400 w400 Gui, Add, StatusBar SB_SetParts(120) SB_SetText( " Test1", 1) SB_SetText( " Test2", 2) Gui, Add, Edit, x+5 yp-4 w40 vas_MonthlyDay_tmp gTest, Gui, Add, UpDown, Range-3-28, 234 Return GuiClose: GuiEscape: ExitApp Return Test: Return
superb! great job.
I'm sure that everybody who uses my Treeview-dll are glad, that they can get rid of of the dll with all its dependencies and problems.
Perhaps a stupid question: Is it planed to support Treeviews in other applications (remotely controlling them) or is it already possible?
Ciao
Micha
evl provided a hint: the Up-Down control is associated to the status bar instead of the edit control.
The workaround is obvious: put the status bar definition at the end of the GUI declarations.
@evl: why not. In SciTE, I implemented the single click in the status bar to make it cycling its infos: simple, easy and effective.
Details: This is caused by status bars needing to be kept at the bottom of the Z-order to alleviate other controls getting drawn on top of them. But doing this causes an UpDown to auto-buddy with the bar rather than the most recently added control.
There is a plan to add data-extraction feature for TreeView similar to the one that already exists for ListView (ControlGet List).Is it planed to support Treeviews in other applications (remotely controlling them) or is it already possible?
Thanks.
Fixed StatusBar's grabbing of UpDowns that are added after it. [thanks Tekl]
Changed Round() to display exactly N decimal places rather than obeying SetFormat.
thanks for the fast bugfix. Btw. is there a way to differ the parts which has been clicked? I want different actions an different parts of the status-bar (double-click).
The variable A_EventInfo contains the part number.