All Projects

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

IDProjectCategoryTask TypeSeveritySummaryStatus  descOpened byLast Edited
21KodaApplicationBug ReportLowResizing property - missing some constantsPostponedZedna16.03.20092 Task Description

In object inspector is property Resizing generated code GUICtrlSetResizing()

But there are missing constants (defined in AutoIt’s helpfile): $GUI_DOCKSIZE, $GUI_DOCKMENUBAR, $GUI_DOCKSTATEBAR, $GUI_DOCKALL, $GUI_DOCKBORDERS

All these contants are defined by sum of base constants already defined in
I think it may be intentional to not add these contants.

But it would be pretty handy to have them all in Koda.

136KodaApplicationFeature RequestMediumUse array namesPostponedOmYcroN07.05.20112 Task Description

Please add the ability to use array names in the Object Inspector for the control names: ControlName[Index]

139KodaApplicationFeature RequestVery Lowadd a option 'set caption also set name'Postponedthesnow25.08.20101 Task Description

add a option ‘set caption also set name’,set name do nothing with caption.

or add a right menu ‘set caption as form name’ to property list.

         thanks!
141KodaApplicationBug ReportLowAbility to generate more then one tab on one formPostponedAdmin07.11.2010 Task Description

While this is cause not too consistent bahaviour (in case of one tab - code generating in one manner, in case of more - fully different), this can be done with only pure Autoit functions. So probably we can give a try.

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?

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.

161KodaApplicationFeature RequestLowAuto-sizing in Radio and Checkbox controlsPostponedChris Haslam02.02.2011 Task Description

Auto-sizing in Radio and Checkbox controls would be useful. Default should be False. Put it on the wish list?

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.

266KodaApplicationFeature RequestLowCheckbox: initialize with $GUI_INDETERMINATEPostponedChris Haslam17.05.20111 Task Description

When BS_3STATE is checked, Check would offer True, Indeterminate and False. If Indeterminate is too long, Gray would fit.

If the user chose Gray and subsequently unchecked BS_3STATE, Check would automatically become False.

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"
  EndFunc

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.

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.

159KodaDocumentationRegular TaskLowHelp | Property EditorsWaiting feedbackChris Haslam18.01.20111 Task Description

It would be helpful if the Help mentioned how to access the property editors. A few are obvious, but one that is not is the TreeView Editor. There may be more that have this problem.

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.

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.

SampleDialog.kxf

<object type="TAForm" name="dlgTest">
	<properties>
		<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>
	</properties>
</object>

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.

171KodaApplicationFeature RequestLowDistinctive colors for grab handles of "No insert in" a...ResearchingChris Haslam07.05.20111 Task Description

Perhaps also a “Insert in” and “Allow copy” menu items, so user doesn’t have to close the form and reopen it to regain full editing capability over controls.

...chris

225KodaApplicationFeature RequestLowMenu Designer: OK and Cancel buttonsResearchingChris Haslam05.05.20111 Task Description

I am finding that it is very easy to loose the last menu item created. I was testing Creating a menu control.

I suggest that Menu Designer have OK and Cancel buttons. This would be user friendly – allowing a user to back out of a change – and could ensure that the last menu item added does indeed get added to the menu control.

4KodaApplicationFeature RequestLowSave chosen template as one of form optionsAssignedAdmin13.11.2008 Task Description

Save chosen template as one of form options.

6KodaApplicationFeature RequestLowNot rename form when loading (Form1->Form1_1)AssignedAdmin13.11.2008 Task Description

Not rename form when loading (Form1?Form1_1)

8KodaApplicationFeature RequestLowCustomizing fontsAssignedAdmin13.11.2008 Task Description

Customizing fonts (by EulerG)

11KodaApplicationFeature RequestLowRemove ClientWidth/ClientHeightAssignedAdmin13.11.2008 Task Description

Remove ClientWidth/ClientHeight for the Form (Make Width=ClientWidth etc)

24KodaApplicationBug ReportLowGeneration options dialog is loose indent char selectio...AssignedAdmin06.02.2009 Task Description

Generation options dialog is loose indent char selection, when opening options dialog by clicking “Manage” button, and then clicking “Ok” in options dialog.

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

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

Column widths are not imported from AU3 to KXF.

79KodaApplicationFeature RequestLowRichEdit custom controlAssignedAdmin15.10.2009 Task Description

RichEdit custom control since it’s UDF was added in the standard distributive.

114KodaApplicationBug ReportLowCtlr+с copy elements but not the valueAssigned06.03.20101 Task Description

keyboard shortcut Ctrl+С copies of the element, although I need to copy the instance name of the element.

129KodaApplicationBug ReportMediumDummy controls appears behind menusAssignedAdmin15.04.2010 Task Description

Dummy controls appears behind menus. Not worth to create some small hack again: new similar bug will appear surely. Better to rethink and rewrite this part of codegen.

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

In version 1.7.2.8 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.

133KodaApplicationBug ReportLowProblems with Toolbar ConfigurationAssignedSpence29.06.20102 Task Description

Version 1.7.2.8

Customize
Add “NewPage” or “NewButton” to a Toolbar (e.g. Standard Toolbar or User Toolbar n” will not show the Icons


with showing User Toolbar3**


User Toolbar 1 is configure well User Toolbar 2 is not configure User Toolbar 3 is configure “Apply” Button Result: User Toolbar 1 is shown, User Toolbar 3 is not shown! a1. User Toolbar 1 is configure well User Toolbar 2 is not configure User Toolbar 3 is configure After “Apply” Button User Toolbar 2 is setting up “Apply” Button Result: All Toolbars will shown b. User Toolbar 1 is configure well User Toolbar 2 is configure well User Toolbar 3 is configure “Apply” Button Result: User Toolbar 3 will not be shown!

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.

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")
EndIf</code>

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).

...chris

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.

Why?

“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.

IMHO

...chris

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.

IMHO

...chris

175KodaApplicationRegular TaskLowForms main menu item: Why?AssignedChris Haslam11.02.20112 Task Description

I do not see the reason for the existence of this menu item.

I can almost as easily key Ctrl-3 and choose which form to activate with the mouse.

Also, consider a form that occupies the whole of the screen. In this case, there is no way IMHO to activate the main menu in order for Alt-m to work. (See the Help as it now is.)

If you wish to keep the Forms menu item, perhaps there should be a function key that focuses Koda so the main menu is active, so Alt-m works.

Or am I missing something?

...chris

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

But Events Example is in Code Templates dialog

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 1.7.3.0 shows two tabs: “Standard” and “My own templates”, but that the 1.7.3.0 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?

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.

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.

214KodaApplicationBug ReportLowTrayMenu | UndoAssignedChris Haslam21.04.2011 Task Description
  1. I clicked on New Form icon
  1. I created a Tray Menu control
  1. I added File as a menu item and gave it Exit as a sub-menu item
  1. I did Ctrl_Z several times
  1. I was then unable to select the form.
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?

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.

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?

223KodaApplicationBug ReportLowForm | OnClose, OnMaximize, OnMinimize in MessageLoop ...AssignedChris Haslam04.05.20112 Task Description

With OnClose, OnMaximize, OnMinimize set to Notify, Koda generated the following code with Generating Options set to MessageLoop mode:

#include <StaticConstants.au3>
#include <WindowsConstants.au3>
#Region ### START Koda GUI section ### Form=F:\Koda forms for PerfectScript\Pic ed test.kxf
$Form1 = GUICreate("Form1", 623, 449, 192, 114)
$Icon1 = GUICtrlCreateIcon("D:\WINDOWS\system32\freecell.exe", -1, 136, 136, 121, 121)
$Pic1 = GUICtrlCreatePic("D:\WINDOWS\system32\setup.bmp", 392, 120, 177, 169)
GUISetState(@SW_SHOW)
#EndRegion ### END Koda GUI section ###
 
While 1
	$nMsg = GUIGetMsg()
	Switch $nMsg
		Case $GUI_EVENT_CLOSE
			Exit
 
		Case $Form1
		Case $Form1
		Case $Form1
	EndSwitch
WEnd

The last 3 cases look odd to me.

I would expect in MessageLoop mode:

  • OnClose to default to Notify unless the code which is run by Koda is not the same as that generated
  • As well as $GUI_EVENT_CLOSE, two cases: $GUI_EVENT_MAXIMIZE and $GUI_EVENT_MINIMIZE

I then switched to OnEvent mode and got:

#include <GUIConstantsEx.au3>
#include <StaticConstants.au3>
#include <WindowsConstants.au3>
Opt("GUIOnEventMode", 1)
#Region ### START Koda GUI section ### Form=F:\Koda forms for PerfectScript\Pic ed test.kxf
$Form1 = GUICreate("Form1", 623, 449, 192, 114)
GUISetOnEvent($GUI_EVENT_CLOSE, "Form1Close")
GUISetOnEvent($GUI_EVENT_MINIMIZE, "Form1Minimize")
GUISetOnEvent($GUI_EVENT_MAXIMIZE, "Form1Maximize")
$Icon1 = GUICtrlCreateIcon("D:\WINDOWS\system32\freecell.exe", -1, 136, 136, 121, 121)
$Pic1 = GUICtrlCreatePic("D:\WINDOWS\system32\setup.bmp", 392, 120, 177, 169)
GUISetState(@SW_SHOW)
#EndRegion ### END Koda GUI section ###
 
While 1
	Sleep(100)
WEnd
 
Func Form1Close()
 
EndFunc
Func Form1Maximize()
 
EndFunc
Func Form1Minimize()
 
EndFunc

I don’t see Exit, so it appears that this is not the code that is run by Koda. This is only an observation.

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.

Thoughts?

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?

242KodaApplicationFeature RequestLowIP address: EnabledAssignedChris Haslam11.05.20115 Task Description

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

265KodaApplicationBug ReportLowInputBox+UpDown | disabled : Code Generator errorAssignedChris Haslam17.05.20111 Task Description

I set InputBox | Enabled to False. Koda generated:

$Input1 = GUICtrlCreateInput("1", 112, 56, 96, 21, 0)
$Updown1 = GUICtrlCreateUpdown($Input1)
GUICtrlSetLimit(-1, 1, 100)
GUICtrlSetState(-1, $GUI_DISABLE)

It should be:

$Input1 = GUICtrlCreateInput("1", 112, 56, 96, 21, 0)
GUICtrlSetState(-1, $GUI_DISABLE)
$Updown1 = GUICtrlCreateUpdown($Input1)
GUICtrlSetLimit(-1, 1, 100)
276KodaApplicationBug ReportLowTAComboBox: Height behaviour abnormalAssignedChris Haslam19.05.2011 Task Description

With CBS_SIMPLE set, at design time, when I mouse to change the height of the control, the Height property does not change.

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.
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?

294KodaApplicationBug ReportMediumAdding context menu to an icon error in on event modeAssignedMartin Gibson29.05.20111 Task Description

Using On Event mode, if you add a context menu to an icon there is an error in the code generated. The code for the menus is inserted between the code for the icon and the code for the onclick definition for the icon

$IconBox = GUICtrlCreateIcon("shell32.dll", -10, 748, 223, 34, 34, BitOR($GUI_SS_DEFAULT_ICON,$SS_SUNKEN))
GUICtrlSetResizing(-1, $GUI_DOCKRIGHT+$GUI_DOCKTOP+$GUI_DOCKWIDTH+$GUI_DOCKHEIGHT)
GUICtrlSetTip(-1, "Create a containing rectangle")
$IconBoxcontext = GUICtrlCreateContextMenu($IconBox)
$MenuAskMargins = GUICtrlCreateMenuItem("Always ask for the margins", $IconBoxcontext)
GUICtrlSetOnEvent(-1, "MenuAskMarginsClick")
$MenuFixedMargins = GUICtrlCreateMenuItem("Use the set margins", $IconBoxcontext)
GUICtrlSetOnEvent(-1, "MenuFixedMarginsClick")
$MenuSetMargins = GUICtrlCreateMenuItem("Set the container margins", $IconBoxcontext)
GUICtrlSetOnEvent(-1, "MenuSetMarginsClick")
$MenuRemoveBox = GUICtrlCreateMenuItem("delete the Container", $IconBoxcontext)
GUICtrlSetOnEvent(-1, "MenuRemoveBoxClick")
GUICtrlSetOnEvent(-1, "IconBoxClick") ;<---------------------------------this line should be before CreateContextMenu line
296KodaApplicationBug ReportLowTAList: Code Generator errorAssignedChris Haslam01.06.2011 Task Description

I set the Color of a Listbox to clBtnFace. It showed OK in the Design Area but when Run. the box was white.

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

Available keyboard shortcuts

Tasklist

Task Details

Task Editing