All Projects

Currently, the development of the Koda project is frozen, the ability to register new users and add new bugreports is disabled.

IDProjectCategoryTask TypeSeveritySummaryStatusOpened byLast Edited  desc
147KodaApplicationFeature RequestLowTAGroup: A suggestionWaiting feedbackChris Haslam17.01.201111 Task Description

Koda works well at grouping if the user creates a group and then adds radio buttons to it: he decides in advance what area of the form will be needed for the radios, and then adds the radios. For example, he creates Group1 and then creates Radio1 and Radio2 within it.

But two scenarios:

  1. But what if he later realizes that he needs a third radio in this group? When he enlarges the Group area and adds Radio 3, Radio3 is not placed in Group1. It should be.
  1. The user creates Checkbox1 and CheckBox2. He then surrounds them with Group2. The checkboxes are not made part of Group2. They should be.

I suggest that code be added to Koda: when a group is created, include in it all controls which are within the area of the group.

170KodaApplicationFeature RequestLowTab Order - 2 casesAssignedChris Haslam23.05.201111 Task Description

As well as Edit→Tab Order, I now see Tab Order in Object Inspector (e.g. for Button). (perhaps Tab Stop Number would be more precise). So I think that there are two cases:

  1. Setting the tab order for all controls, and
  2. Setting the tab stop number for the currently selected control.

Tab Order Editor handles the first case.

Now for the second case.

In Object Inspector, Koda permits the user to enter the tab stop number. But what if he enters 2, and there is already a control that has tab stop 2. What happens?

I think it would be preferable to have clicking to the right of tab order bring up a dialog something like my screenshot:

This would allow the user to position the selected control relative to other controls. Note that he would no longer be concerned with the tab stop number, so conflicts in number could not occur.



187KodaApplicationFeature RequestLowOnClick => Notify ?AssignedChris Haslam05.05.201111 Task Description

I don’t see why OnClick brings up a dialog.

It only has two values: Notify and don’t notify.

It seems to me that it would be more obvious if it were called Notify and its values were True and False. It would then work like, for example, Enabled.

Just a thought.

131KodaApplicationBug ReportHighUnable to insert embedded IE controlAssignedND04.05.20109 Task Description

In version when I try to add an embedded IE control (Shell.Explorer.2) to a form Koda shows
‘Call to DllRegisterServer failed in

As consequence no AU3 code is generated for the control - although it shows on the form - and all attempts to open the definition file afterward fail with the same error message, so the only remaining option is to open KXF file as XML and remove the control manually.

Especially confusing is the fact that Koda wants to call DllRegisterServer at all. Why is it necessary? The DLL is already registered on the system, otherwise the control wouldn’t appear in the Koda’s object browser.

292KodaApplicationBug ReportLowForm styles: Code generation errorUnconfirmedChris Haslam10.06.20119 Task Description

Style 94C8 0000 generates $WS_SYSMENU,$WS_POPUP. It should generate $WS_POPUPWINDOW, $WS_CAPTION.

304KodaApplicationBug ReportLowButton icon bug: not visible at run timeAssignedChris Haslam24.06.20119 Task Description

With the attached .kxf file, the icon is visible at design time but not at run time. The icon is number 0 in shell32.dll. Other icons in shell32.dll work OK. Icon 0 in moricons.dll also does not work.

This may be an AutoIt error. If it is, is there a way for Koda to work around AutoIt’s bug?

184KodaApplicationFeature RequestLowTemplate GalleryAssignedChris Haslam05.05.20118 Task Description

I note that the documentation calls this “Templates Gallery” but 1.7.3 .0 and the screen shot call it “Form Templates”. I suggest that “Form Templates” is the better name: it fits with “Code Generation Templates”. I will change the documentation to “Form Templates”.

I note that shows two tabs: “Standard” and “My own templates”, but that the help and the documentation shows only “Standard”. Further, one of the templates in the “My own templates” tab has no icon. I suggest that “My own templates” be dropped. THe documentation will tell the user how to add templates and tabs.

How can the user add a description and icon to a template he creates?

How can the user delete a template he creates?

How can the user delete a tab that he creates?

150KodaApplicationBug ReportLowExpand %var% variablePostponedChris Haslam17.01.20117 Task Description
  • I ran Koda. It brought up a form I had created earlier. Expand %var% variable was unchecked
  • I created a label
  • I entered %name% is a cat in Label | Caption
  • I checked Expand %var% variable
  • I clicked on Generate Code. ⇒ $name+”is a cat”
  • I unchecked Expand %var% variable
  • I clicked on Generate Code. ⇒ $name+”is a cat” again

This seems illogical.

What is the scope of Expand %var% variable? Is it specific to the form/.kxf file, or is it application level? Is it working as intended?

182KodaApplicationBug ReportLowTools | Generating Options | Template doesn't show Even...AssignedChris Haslam24.02.20117 Task Description

But Events Example is in Code Templates dialog

201KodaDocumentationBug ReportLowOptions | Options | Windows: which windows?UnconfirmedChris Haslam05.05.20117 Task Description

Are the Windows here all the windows in Koda, i.e. Object Treeview, Object Inspector, Form List, and forms?

I have not figured out what the following checkboxes really do:

  • Keep standard layout
  • Snap wimdows (to the grid?)
  • Choices in Size and position saving (especially the difference between Don’t save abd Manually)

I have looked at the doc as I received it. It doesn’t help.

BTW the screen shot here is obsolete: we need a new one. Please supply.

BTW “Always full expand” should be “Always fully expand”

202KodaApplicationFeature RequestLowOvercoming MS's confusion in styles for formsAssignedChris Haslam05.05.20117 Task Description

MS‘s mess (discussed previously) is driving me nuts!

So for Styles of TAForm I suggest that you add some pseudo-styles. Some I think of: Title bar, Close box, Minimize box, Normal frame, Dialog frame, perhaps Modal.

There are two ways you could add them:

  1. Put them in the Styles tab, at the top of the list, or
  1. Put a Clearer styles for Form checkbox in Options | Designer. When it is checked, have Koda replace all the WS styles which are equivalent to pseudo-styles.

You have more experience than I do with these bloody styles. Perhaps there is no way to get around MS‘s confusion!

There is another way: document the translation from pseudo-styles to WS_ constants in Controls | Form. For that I would need your help.

216KodaApplicationBug ReportLowPicture Editor: some observationsUnconfirmedChris Haslam04.05.20117 Task Description

See the doc for the way I understand it.

The Load | File Open dialog filter only offers .jpg, .jpeg, .bmp and .gif.

Via Load, I moused to, and selected, D:\WINDOWS\system32\setup.bmp. This appeared in Custom path to image, and the .bmp appeared in Selected image.

I then changed the path to @SystemDir\setup.bmp. Select image cleared. A bug?

In the course of this, I discovered that there is only one level of Undo here.


  • The File Open dialog filter may be too tight, e.g. .exe should be permitted, perhaps others; however it did allow me to enter F:\Program Files\AutoIt3\SciTE\Koda\FD.exe .
  • @ScriptDir should be permitted in Custom path to image. This would be helpful to a user who puts his .bmps, etc. in the same tree as his script. As Run (F9) is now, running the form would show a blank picture. Perhaps Koda could instead temporarily create a picture containing the file spec. Or one saying “File not available to Koda”. Being able to use @ScriptDir is hugely important to me!
  • Koda could, when it generates code, replace a path that begins !:\WINDOWS (where ! is any drive leter) with @WindowsDir. Similarly for @SystemDir and @TempDir I see no harm in this.

Perhaps a filename and ext should be generated by Koda as @ScriptDir\fnam.ext

  • I had a case a while back where picture being a %varaible would have been useful.

Some of these thoughts come from consideration of updating a form in a .au3. I would rather not have to change the file spec whenever I update the script.

  • Having only one input field for the file spec is not user-unfriendly for people like me who make mistakes! I suggest Custom path to image be replaced the fields in the screen shot attached.
219KodaApplicationFeature RequestLowTreeview Editor: ObservationsAssignedChris Haslam27.04.20117 Task Description

I suggest that:

  • Image index be changed to Image index when unselected
  • Selected be changed to Image index when selected

Selecting a node created earlier without a name is challenging: you have to click exactly in the right place. I suggest that when a node is created, Koda assign it a temporary name, e.g. Node1 (like Menu Editor). This name would be highlighted in the Text input box, ready for the user to enter his own name.

A related question: should Koda even allow a node to exist neither an image nor a name?

It would be user-friendly if images could be selected from a list: see how I have written the doc for To add a node.

It would be nice if icons showed in the treeview control as they do at run time.

Is image the correct word? Aren’t they always icons?

222KodaDocumentationBug ReportLowForm controlUnconfirmedChris Haslam04.05.20117 Task Description

Description is in the doc but not in Object Inspector. Do I remove Description from doc?

261KodaApplicationFeature RequestLowDisable a tabstopUnconfirmedChris Haslam24.05.20117 Task Description

An example from External Link:

GUICtrlCreateButton("Two", 10, 140, 80, 30)
_WinAPI_SetWindowLong(GUICtrlGetHandle(-1), $GWL_STYLE, BitAND(_WinAPI_GetWindowLong(GUICtrlGetHandle(-1), $GWL_STYLE), BitNOT($WS_TABSTOP)))

But first the inconsistency between Tab Order and WS_TABSTOP needs to be resolved.

309KodaApplicationBug ReportLowTAList: Caption missing from PropertiesUnconfirmedChris Haslam08.07.20117 Task Description

Probably not used much, but should be there.

153KodaApplicationBug ReportLowTAInput with TAUpdown always sets initial value to UpDo...PostponedChris Haslam17.01.20116 Task Description

I set the Min to 1 and the Max to 9 in Updown. I could not then change the Text in Input to 3. I should be able to do this.

194KodaApplicationBug ReportLowOptions | Options | General | Recent filesUnconfirmedChris Haslam12.05.20116 Task Description

I suggest that the caption be changed to Recent files in File menu. This is consistent with Undo levels. I also think that it is clearer.

77KodaApplicationFeature RequestLowMaking Code Templates more flexibleWaiting feedbackDavid30.05.20115 Task Description

I would like to see additional variables available for the Code

  %FORMNAME% - the name of the form as assigned in the form's properties.

The ability to inject code into general event

  Func MyGUIClose()
    $MyVar="Some Value"

The reason for this request is that most of the time, when I create a GUI, I create it within a function in an include file, with additional control structures. I typically spend 5-10 minutes each time I generate new code using KODA to fit it into my format. I would like to be able to use custom Code Templates to create them already in my format, so I can jump right into the application coding.

152KodaApplicationBug ReportLowTAUpdown: Appearance in Preview is inconsistent with ap...AssignedChris Haslam30.06.20115 Task Description

In Koda, it is possible to widen an updown control. This change shows in Preview and can make some very wide updown controls.

Running the generated code produces the same overall width (Input plus Updown) but the width of the Updown is fixed. The extra width is added to the Input.

See attached screenshots.

AutoIt help shows

GUICtrlCreateUpdown ( inputcontrolID [,style] 

so there is no opportunity to enter the left, top, width and height.

So left, top, width and height should not appear in Properties for Updown. The left and top are always “to the right of the Input”. The height is taken from the Input, and should be set there. The width is always 17 in AutoIt.

Autoit only recognizes UpDown as a buddy window.

MSDN says that “The width of the buddy window is decreased to accommodate the width of the up-down control”. This is not the way AutoIt behaves.

235KodaApplicationBug ReportLowSlider | PositionWaiting feedbackChris Haslam11.05.20115 Task Description

I take Position to be the initial position (value) of the slider.

I set Position to 40. It appeared not to generate any code. I did run. The slider showed at the left end of its range.

242KodaApplicationFeature RequestLowIP address: EnabledAssignedChris Haslam11.05.20115 Task Description

I am surprised that there is no Enabled property in Object Inspector

299KodaApplicationBug ReportLowFile | Recent Files: non-existent fileUnconfirmedChris Haslam21.06.20115 Task Description

When I tried to open a file that I had moved, Koda said “F:\ ... is not exists”. Correct English usage is “does not exist”.

311KodaApplicationBug ReportLowTAEDIT: bad line wrapping with custom fontUnconfirmedChris Haslam07.07.20115 Task Description

The attached .kxf file shows that for the dd code, zero fits easily on the line when the form is run. If I remove the \n\r in Strings Editor, they return when I close SE. SE does not seem to know that the font is Courier New 8pt.

168KodaApplicationBug ReportLowEdit | Align menu | Center ... in WindowAssignedChris Haslam11.02.20114 Task Description

I suggest that Center Horizontally in Window be changed to Center Horizontally in Parent or Center Horizontally in Container.


“Parent”: As I understand it, Koda now considers a control to be in a group if it is a son of a group in Object TreeView.

“Container”: This can mean both son in Object TreeView and what surrounds a control visually in the Form display. This term would allow for Koda automatically making a control a son of a group if it is visually within the group.

“Window”: to me, this is an imprecise term. It can mean any window.



191KodaApplicationRegular TaskLowMultiple selection of controlsUnconfirmedChris Haslam13.03.20114 Task Description

Where is this mentioned in the Help? I have not found it.

I find it a little surprising that the user shift-clicks to add a control to the selection.

In Explorer (and elsewhere), control-click adds a file to the selection; shift-click adds a range of files to the selection.

Just a thought.

212KodaApplicationFeature RequestLowControl Palette: Reorganize?PostponedChris Haslam05.05.20114 Task Description

I understand why there are four tabs, but I wonder if there is a better way of organizing them.

I find that I easily forget where to find a control: which tab is it on? and which icon is it? A few icons are clear as to what the control is, but some are not. I often have to wait for the telltale to show to be sure. This is not the fault of the picture on the icon: icons are only a limited number of pixels.

So Idea #1 is to add a main menu item called Controls, with all the controls as sub-items. In the future, it may be necessary to have 3 levels, with Native and UDFs as the second level.

Idea #2 is to group the controls alphabetically, e.g. A to E for the first tab, F to M for the second, etc.

215KodaApplicationBug ReportLowTrayMenu | MouseClick | DefaultAssignedChris Haslam26.04.20114 Task Description

I have problems with Koda generating TraySetClick(”0”) as the default:

  • AutoIt help says that the default is 9 (tray menu shows when left or right mouse button is pressed)
  • The Koda default being Tray menu will never be shown through a mouseclick can lead the inexperienced user to think that creating the Tray Menu has failed.
  • The Tray Menu doc says that the default is mcPriPress + mcSecPress.

It is not clear to me what ShowStdMenu does when a Tray Menu control is on a form.

Any thoughts?

229KodaApplicationBug ReportLowData separator charAssignedChris Haslam05.05.20114 Task Description

I find it a little surprising that Data separator char is in Options but not in Generating Options. My understanding is that it is not saved with the form, so if the form was created when Options | Data separator char was (say) $ and the user later adds a ListBox where one of the items is $10, he has to recreate his form from scratch.


234KodaApplicationBug ReportLowDummy: notifyAssignedChris Haslam04.05.20114 Task Description

I read in the doc:

The control will “notify” as normal

but do not see an OnClick property.

So how does the user tell a Dummy control to notify?

240KodaApplicationBug ReportLowTab Control: Focus and reorganizing pagesUnconfirmedChris Haslam06.05.20114 Task Description

While Alt-Left and Alt-Right have worked for me, I have just spent several minutes trying to get Alt-Left to work for me.

Screen shot and .kxf file are attached.

I wish I could be clearer as to what is happening. Alt-Left seems not to be working because the focus is not on TabSheet1. I also notice that the Form is active but Koda is not: odd.

When I first tried Alt-Left and Alt-Right they didn’t work. Then somehow they did.

277KodaApplicationBug ReportLowMenutitem: Object Inspector shows styles and exstyles f...UnconfirmedChris Haslam10.06.20114 Task Description


279KodaApplicationBug ReportLowGraphics: graphic may not show in controlAssignedChris Haslam14.06.20114 Task Description

If the graphic created in Graphics Editor is too far down in the GE design area, and/or is to far the right, it may not be seen in the design area.

There are 3 possible solutions that I can think of:

  • Have Koda reposition the graphic, and perhaps decrease it in size, so that all of it shows in the Graphics control
  • Make the size of the design area in the Graphics Editor the same size as the Graphics control
  • Add to the Graphics Editor the right and bottom bounds of the control, showing them as thick dashed lines. It would then be the responsibility of the user either to keep within the bounded design area or, when he leaves GE, to change the size of the control to fit the graphics.
280KodaApplicationBug ReportLowGraphics styles: some suggestionsUnconfirmedChris Haslam11.06.20114 Task Description

SS_LEFTNOWORDWRAP appears in OI but is not, I think, applicable to a control that has no text

SS_SIMPLE seems to do nothing

SS_ETCHEDHORZ reduces the Height to 2, and when the Height is restored in OI, the graphic is not drawn. Indeed, Graphics Editor no longer shows the graphic although Item still shows 1 item.

SS_ETCHEDVERT behaves similarly except that the Width increased to about 630.

These tests were with a graphic that was larger than the control.

291KodaApplicationBug ReportLowForm styles: a few definitely don't belong to FormUnconfirmedChris Haslam09.06.20114 Task Description

WS_GROUP and WS_MINIMIZEBOX have the same value, so WS_GROUP is not a constant for a Form. So remove WS_GROUP. See  FS#267 .

The value of WS_OVERLAPPED is zero. It has no mask. So I suggest that it be removed from OI.

WS_SIZEBOX and WS_THICKFRAME have the same value, so I suggest removing WS_THICKFRAME.

WS_TABSTOP and WS_MAXIMIZE have the same value, so WS_TABSTOP is not a constant for a Form. So I suggest removing WS_TABSTOP.

298KodaApplicationBug ReportLowStyles dialogs suggestionsUnconfirmedChris Haslam08.09.20114 Task Description

I have made some more progress: I have improved the Form dialog, and present the Label dialog for the first time.

I am beginning to think about Pic, Icon and Graphic. Here are my thoughts:

The following SS constants only apply to an image: SS_BITMAP, SS_ICON, SS_REALSIZECONTROL, SS_REALSIZEIMAGE and SS_RIGHTJUST. Which of these does Picture Editor handle? Which does the proposed Styles Editor need to handle?

I have learnt that ControlSetText() can be used to show text in an apparently image-only Static control. So the Styles Editor for Pic, Icon and Graphic could look much the same as that for Label. Would it be identical?

It occurs to me that if Koda will have a Styles Dialog for images that has styles for text, it would make sense to have Code Generator generate the call to ControlSetText().

More thoughts are in the attached readmes.

318KodaApplicationBug ReportLowTAMonthCal: Centering problemAssignedChris Haslam08.07.20114 Task Description

The auto-height seems to be correct at 168, but the vertical centering is off a bit, so when Autosize is True, the bottom of the Today line is hidden.

It is likely that there are other cases where centering is a bit off, e.g. Align | Center Vertically in Window.

89KodaApplicationBug ReportMediumWrong form height in the generated codeResearching29.05.20113 Task Description

If a dialog form is created with the certain style bits (s. below) in Koda the window height in the generated AutoIt code is set to ClientHeight + 1 instead of Height which cuts off a stripe of the height of the window’s title bar (mostly 26 px) at the bottom of the form at the time is displayed from the script.

Example as followed.


<object type="TAForm" name="dlgTest">
		<property name="Left" vt="Int16">1626</property>
		<property name="Top" vt="Int16">262</property>
		<property name="Width" vt="Int16">321</property>
		<property name="Height" vt="Int16">407</property>
		<property name="Caption" vt="String">Sample Dialog</property>
		<property name="Color" vt="Ident">clBtnFace</property>
		<property name="Font.Charset" vt="Ident">DEFAULT_CHARSET</property>
		<property name="Font.Color" vt="Ident">clWindowText</property>
		<property name="Font.Height" vt="Int8">-11</property>
		<property name="Font.Name" vt="String">MS Sans Serif</property>
		<property name="Font.Style" vt="Set"/>
		<property name="OldCreateOrder" vt="False">False</property>
		<property name="Position" vt="Ident">poDesktopCenter</property>
		<property name="ParentForm" vt="String">owner</property>
		<property name="Style" vt="Int32">273154176</property>
		<property name="ExStyle" vt="Int8">0</property>
		<property name="Version" vt="String">1.04</property>
		<property name="PixelsPerInch" vt="Int8">96</property>
		<property name="TextHeight" vt="Int8">13</property>

SampleDialog.au3 (generated)

#Region ### START Koda GUI section ### Form=SampleDialog.kxf
    Local $dlgTest = GUICreate("Sample Dialog", 314, 374, -1, -1, BitOR($WS_SYSMENU,$WS_DLGFRAME,$DS_MODALFRAME), 0, $owner)
#EndRegion ### END Koda GUI section ###

As far as I evaluated this concerns only (modal) dialog frames with system menu but without minimize/maximize boxes, normal overlapped windows are not affected though their heights are also set to ClientHeight. It may be the strange way AutoIt’a GUICreate() works but I think Koda should reflect its behavior even if it’s inconsistent.

37KodaImportFeature RequestLowImport - Listview column widths - not importedAssignedZedna03.02.20103 Task Description

$Form1 = GUICreate(”Title”, 300, 200, -1,
= GUICtrlCreateListView(”A|B|C”, 15, 15, 270,

Column widths are not imported from AU3 to KXF.

158KodaApplicationBug ReportLowTALabel: AutosizeAssignedChris Haslam03.06.20113 Task Description

I would like to see the default for TALabel | Autosize be False. It is frustrating to create a label which will be populated/set from the AutoIt script and have its default to the size of the text Label1 – because part of my mental process is to make the size be enough for the longest value GUICtrlSetData() will provide.

For example, when I am upgrading a script, I usually put the word “Development” as a label in the first dialog the script creates. When the script is no longer a development version, the script leaves this label blank. So in Koda I make lblDevel long enough for the word “Development”. Here is the

If StringInStr(@ScriptName,"(Devel)")<>0 Then
	GUICtrlSetData($lblDevel,"Development version")

As Koda is now, I have to create the label, change AutoSize to False, then increase the length of the label. A bit of a pain!

This is not a major issue with me, but I would prefer AutoSize to default to False (as VB has it).


164KodaApplicationBug ReportLowFile | Close Form is inconsistent with File | Open and ...UnconfirmedChris Haslam02.02.20113 Task Description

I suggest File | Close.

Documentation says Close, not Close Form.


165KodaDocumentationBug ReportLowEdit | Paste doesn't paste to the current cursor positi...UnconfirmedChris Haslam08.02.20113 Task Description

The Help says “Paste previously copied/cut objects from clipboard into current cursor position”.

Attached is what actually happened when I tried it.

All I can say is that Paste didn’t work as documented. I don’t know how it should work: I am thinking about it.

For the time being, I will document it the way it actually works.

VB5 pastes to the top left of the client area, independent of where the cursor is.


197KodaDocumentationRegular TaskLowTools | Update Script with multiple Koda regions in the...UnconfirmedChris Haslam15.04.20113 Task Description

If there are two Koda regions in a .au3 file, say foo.kxf and bar.kxf, will Update Script work both when foo.kxf is the active form and when bar.kxf is the active form?

It seems to me that this is possible, but the current documentation does not say so.

218KodaApplicationBug ReportLowTreeView bug?AssignedChris Haslam26.04.20113 Task Description

I am trying to understand Image index and Selected index. BTW in the doc proped_treeview_editor.png lacks these controls.

When I tried to generate from the attached form, I got an AutoIt error. See attached screenshot.

220KodaApplicationBug ReportLowFD launch bugUnconfirmedChris Haslam05.05.20113 Task Description

On the first launch of the day, I got an exception error. Screen shot attached.

The other screen shot is after clicking OK to the message box.

I was able to close Koda.

Then I was able to launch Koda normally.


226KodaApplicationBug ReportLowMenuItem | RadioItemUnconfirmedChris Haslam05.05.20113 Task Description

Either MenuItem | RadioItem is not working or I don’t understand it. .kxf file, attached, generated:

#include <GUIConstantsEx.au3>
#include <StaticConstants.au3>
#include <WindowsConstants.au3>
#Region ### START Koda GUI section ### Form=F:\Koda forms for PerfectScript\Menu radio test.kxf
$Form1 = GUICreate("Form1", 623, 449, 192, 114)
$mnuFile = GUICtrlCreateMenu("&File")
$mnuOpen = GUICtrlCreateMenuItem("Open", $mnuFile, -1 , 1)
$mnuSave = GUICtrlCreateMenuItem("Save", $mnuFile, -1 , 1)
$MenuItem1 = GUICtrlCreateMenuItem("", $mnuFile)
$mnuExit = GUICtrlCreateMenuItem("Exit", $mnuFile)
$mnuEdit = GUICtrlCreateMenu("&Edit")
$mnuOpts = GUICtrlCreateMenu("&Options")
$mnuHelp = GUICtrlCreateMenu("&Help")
$Label1 = GUICtrlCreateLabel("Label1", 224, 184, 36, 17)
#EndRegion ### END Koda GUI section ###
While 1
	$nMsg = GUIGetMsg()
	Switch $nMsg
#include <GUIConstantsEx.au3>
#include <StaticConstants.au3>
#include <WindowsConstants.au3>
#Region ### START Koda GUI section ### Form=F:\Koda forms for PerfectScript\Menu radio test.kxf
$Form1 = GUICreate("Form1", 623, 449, 192, 114)
$mnuFile = GUICtrlCreateMenu("&File")
$mnuOpen = GUICtrlCreateMenuItem("Open", $mnuFile, -1 , 1)
$mnuSave = GUICtrlCreateMenuItem("Save", $mnuFile, -1 , 1)
$MenuItem1 = GUICtrlCreateMenuItem("", $mnuFile)
$mnuExit = GUICtrlCreateMenuItem("Exit", $mnuFile)
$mnuEdit = GUICtrlCreateMenu("&Edit")
$mnuOpts = GUICtrlCreateMenu("&Options")
$mnuHelp = GUICtrlCreateMenu("&Help")
$Label1 = GUICtrlCreateLabel("Label1", 224, 184, 36, 17)
#EndRegion ### END Koda GUI section ###
While 1
	$nMsg = GUIGetMsg()
	Switch $nMsg
283KodaApplicationBug ReportLowSlider styles: some suggestionsUnconfirmedChris Haslam10.06.20113 Task Description

TBS_ENABLESELRANGE, TBS_FIXEDLENGTH: I do not see a way of setting the selection range. It appears that GuiCtrlSlider... does not have selection range but _GuiCtrlSlider... does. TBS_ENABLESELRANGE is in SliderConstants.au3

TBS_NOTHUMB appears twice in OI.

286KodaApplicationBug ReportLowStatusbar styles: some suggestionsAssignedChris Haslam11.06.20113 Task Description

SBARS_SIZEGRIP and SBARS_TOOLTIPS: need some extra code to be generated to work. For now, doc says “Requires ... message”.

SBARS_TOOLTIPS: no way to specify hint(s).

Remove them from OI for now?

300KodaApplicationBug ReportLowMultiple selection of controls within a GroupUnconfirmedChris Haslam25.06.20113 Task Description

I have written in the proposed Help:

To select all controls in an area of the active form, hold the left mouse button down and drag to select an area of the form. All controls wholely within, and partly within, this area are selected.

This often does not work when I try to select several controls in a Group, and is driving me nuts with the Style dialogs. :-)

I suggest that Koda be changed such that:

  • clicking within a Group in the Design area does not select the Group
  • a Group can only be selected in the Design Area by clicking on (or near) its border, not on a drag handle.
313KodaApplicationBug ReportLowBackground color: entering numeric valuesUnconfirmedChris Haslam06.07.20113 Task Description

I have not figured out how this works.

From a color wheel in another app, I chose a light yellow: RGB (248,248,164). I converted to hex: (F8,F8,A4). In TAEdit Properties, I entered 0xF8F8A4. It showed as light cyan.

Please explain.

Showing tasks 1 - 50 of 147 Page 1 of 31 - 2 - 3 -

Available keyboard shortcuts


Task Details

Task Editing