V3.0.102 Unstable Updated

[Jos]

Jon. Error output to stdout works great ... tnx..

You just double click the error line and it jumps right to the code line with the error:

Will publish the changes in the next upload of the Scite install set.

http://www.autoitscript.com/fileman/users/jdeb/test/scripterror2.png

Edited June 6, 2004 by JdeB

[Josbe]

Jon. Error output to stdout works great ...  tnx..

You just double click the error line and it jumps right to the code line with the error:

Will publish the changes in the next upload of the Scite install set.

http://www.autoitscript.com/fileman/users/jdeb/test/scripterror2.png

Brilliant!.

[Valik]

Jon, think you could add a simple wrapper around printf() to accompany this? Something simple that takes one parameter and forwards it to printf() would suffice since AutoIt can already use & to format numbers and strings.

[Jon]

Updated:

- Added: ReDim

[Valik]

Updated:

- Added: ReDim

Cool, glad to see this.

[Josbe]

Cool, glad to see this.

Me too.

[Jon]

http://www.autoitscript.com/autoit3/files/unstable/autoit/

Updated:

- Added GuiSetGroup() and fixed internal WS_GROUP usage

For an example of how grouped controls and a "group" box control are different try this example:

expandcollapse popup

#include <GUIconstants.au3>

Opt("GUICoordMode", 1)
Opt("GUINotifyMode", 1)
GUICreate("Radio Box Demo", 400,280)

; Create the controls
$button_1 = GUISetControl("button", "B&utton 1", 30, 20, 120, 40)
$group_1 = GUISetControl("group", "Group 1", 30, 90, 165, 160)
GUISetGroup()
$radio_1 = GUISetControl("radio", "Radio &0", 50, 120, 70, 20)
$radio_2 = GUISetControl("radio", "Radio &1", 50, 150, 60, 20)
$radio_3 = GUISetControl("radio", "Radio &2", 50, 180, 60, 20)
GUISetGroup()
$radio_4 = GUISetControl("radio", "Radio &A", 120, 120, 70, 20)
$radio_5 = GUISetControl("radio", "Radio &B", 120, 150, 60, 20)
$radio_6 = GUISetControl("radio", "Radio &C", 120, 180, 60, 20)
GUISetGroup()
$input_1 = GUISetControl("input", "Input 1", 200, 20, 160, 30)
$input_2 = GUISetControl("input", "Input 2", 200, 70, 160, 30)

; Set the defaults (radio buttons clicked, default button, etc)
GUISetControlEx($radio_1, $GUI_CHECKED)
GUISetControlEx($radio_6, $GUI_CHECKED)
GUISetControlEx($button_1, $GUI_FOCUS + $GUI_DEFBUTTON)

; Init our vars that we will use to keep track of GUI events
$radioval1 = 0   ; We will assume 0 = first radio button selected, 2 = last button
$radioval2 = 2

GuiShow()

; In this message loop we use variables to keep track of changes to the radios, another
; way would be to use GuiRead() at the end to read in the state of each control
While 1
   $msg = GuiMsg()
   Select
      Case $msg = -3
         Exit
         
      Case $msg = $button_1
         MsgBox(0, "Default button clicked", "Radio " & $radioval1 & @LF & "Radio " & Chr($radioval2 + Asc("A")) & @LF & GuiRead($input_1) & @LF & GuiRead($input_2))
         
      Case $msg = $radio_1 OR $msg = $radio_2 OR $msg = $radio_3
         $radioval1 = $msg - $radio_1
         
      Case $msg = $radio_4 OR $msg = $radio_5 OR $msg = $radio_6
         $radioval2 = $msg - $radio_4

   EndSelect
WEnd

[jpm]

Jon,

I don't really like the example because usualy in the gui I saw radiobox inside a group are related. I understand that somebody want to have the left radidoxes working independantly than the right ones. But grouping them mean something different from my point of view. If I Have to design a gui as such I will have put 2 groups.

More with the new modification the control-tab is not working to switch from tab to tab as usually under other window gui

Edited June 15, 2004 by jpm

[CyberSlug]

Hmm, I wonder what happens if you span a group across multiple tab controls....

[Jon]

Jon,

I don't really like the example because usualy in the gui I saw radiobox inside a group are related. I understand that somebody want to have the left radidoxes working independantly than the right ones. But grouping them mean something different from my point of view. If I Have to design a gui as such I will have put 2 groups.

More with the new modification the control-tab is not working to switch from tab to tab as usually under other window gui

If you want to use a group box everytime you want to use radio buttons then that's fine - but it's not a "rule" that has to be followed as lots of programs have grouped controls without the visible group box, here are my Eurdora options:

I could make it so that when you create a group control a new grouping is automatically started? But you still need a way of ending a group and would be confusing to switch between two methods depending on if you wanted to draw a group box or not.

[jpm]

True Jon, I still like the group around the radiobox which are related.

With my proposal I certainly can hide the group control to have it not displayed to achieve the same result as yours.

My solution will be easier if group is often used.

[Jon]

I'll make a group control force a new grouping in addition then... But you are all clearly mad...having to create and then hide a control indeed...

[SlimShady]

That's your opinion but I would like that.

[jpm]

I'll make a group control force a new grouping in addition then...  But you are all clearly mad...having to create and then hide a control indeed...

that's fine and will allow both utilization.

[Jon]

http://www.autoitscript.com/autoit3/files/unstable/autoit/

Updated & recent changes:

3.0.102 (16th June, 2004) (Beta)

- Changed: RegWrite accepts just the keyname to create a key (with no value)

- Changed: Creating a "group" control also forces GUISetGroup()

- Added: GUISetGroup() and improved automatic WS_GROUP and WS_TABSTOP to be as per MS dialog standards

- Added: ReDim

- Added: Command line option /ErrorStdOut

- Added: $GUI_DEFBUTTON (Default button) style for GuiSetControlEx()

- Changed: Colors now default to the standard RGB format rather than the previous BGR format.

This affects PixelSearch, PixelGetColor, GuiCreateEx and GuiSetControlEx.

The "ColorMode" option has been added to allow old scripts to run with the old BGR mode, just

place this line at the top of your script to use the old method:

Opt("ColorMode", 1)

[Jon]

Updated:

3.0.102 (21st June, 2004) (Beta)

- Added: @DesktopDepth macro

- Changed: RunAsSet() supports extra profile handling options

- Changed: An explicit GuiShow() call is now required to show the GUI.

[midiaxe]

Jon,

Thanks for the update! I use RunAsSet(() most of the time in my installations and the extra options really help me. Here some of my observations (I'm using XP SP1):

Current User: user1

User used in RunAsSet(): user2

Using option 0:

It loads "Default User" profile

Using option 1:

It loads "user2" profile

Using option 2:

It retains "user1" profile. This is what I always use.

Thanks again!

=MX=

Edited June 21, 2004 by midiaxe

[Jon]

Hmm, I would have throught that option 0 just keeps the current profile... I'll have to test some more when I get chance.

[jpm]

Jon,

Any idea why a winActivate is need after a guishow

see CyberSlug post

[Valik]

Jon,

Any idea why a winActivate is need after a guishow

see CyberSlug post

Jon said in another thread that the GUI was being shown with SW_SHOWNA which is "show normal but don't activate". I think he said he was changing it to SW_SHOWNORMAL.