All Projects

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

IDProject  ascCategoryTask TypeSeveritySummaryStatusOpened byLast Edited
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.

323KodaApplicationBug ReportHigh$UDS_ARROWKEYS not definedUnconfirmedV@no27.12.2011 Task Description

When added a updown control and enabled UDS_ARROWKEYS style it fails run the
generated code is
<UpdownConstants.au3></code>

339KodaApplicationBug ReportHighI can't rename tab controlUnconfirmedVo Anh Kiet15.01.2015 Task Description

I’m using Windows 7 and Koda FormDesign Version 1.7.3.0 build 252
I add more a tab control into Form after that I rename this tab
have received a Exception handled: MainExceptionHandler
confirm attachment file

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.

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.

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]

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
324KodaApplicationBug ReportMediumColumns are lost when copying ListviewUnconfirmedChristian21.04.20121 Task Description

Sometimes the defined columns of a listview are lost when copy & pasting or cut & pasting a
watch the following screencast for visual

Operating System: Windows 7 Professional (Not selectable in New Task Dropdown)

335KodaApplicationBug ReportMediumAny objects (buttons, edit boxes) always snapping/resiz...UnconfirmedTrevor Blanc24.11.2012 Task Description

It snaps on to one more pixel above my actual client size, making it impossible to not have a scrollbar constantly popping up every time I want to make something as wide as the actual
am not sure if this is a bug or intentional, but it makes koda really hard to use for me.

337KodaImportBug ReportMediumUsing parenthesis "()" in tab names, breaks import.UnconfirmedVitaliy Maksimov24.09.2013 Task Description

1. Create a new “Tabbed Pages”
Change the name of the first tab to “TabSheet1
Generate form code
File, Import, Import Autoit GUI

338KodaApplicationBug ReportMediumLock controls in designerUnconfirmedHenrik24.08.2014 Task Description

The function “Edit→Control→Lock” works only in the actually
reloading the “KXF”-file, the “LOCK” no longer works.

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)

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.

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.

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.

79KodaApplicationFeature RequestLowRichEdit custom controlAssignedAdmin15.10.2009 Task Description

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

81KodaApplicationFeature RequestLowAbility to separate form generating code and event codeUnconfirmed04.11.20091 Task Description

Hello,

I would like to separate the code for generating the form, and my own event code.

One way to do this would be to let Koda generate an au3 file for generating the form, but no event handlers. I would just #include this file in my own au3 file. I am responsible myself for generating the right functions for the event handlers, or I could implement an event loop.

More complex options could be conceived, like in the following post :

   http://www.autoitscript.com/forum/index.php?showtopic=17612

I would be interested in contributing to Koda, and maybe implement this feature myself. I have 10 years of professional programming experience in Borland C++ Builder and Delphi.

Best

102KodaApplicationBug ReportLowIn String list editor all words are not translatable.UnconfirmedThierry05.02.20101 Task Description

In the string list editor, we can’t translate all the terms
attached image.

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.

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!

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.

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.

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?

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.

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.

154KodaApplicationBug ReportLowTAUpdown: Problems in AutoIt affect KodaUnconfirmedChris Haslam03.01.20112 Task Description
  • GUICtrlSetLimit() sets max and min but not increment. Perhaps a _GuiCtrlSetLimit(max, min, incr) could be written. Then Koda could set a (new) Increment property. It is needed if UDS_ARROWKEYS is to work. You may have some influence over Jon to add to GUICtrlSetLimit().
  • If no style is specified, Updown is placed to the right of the Input, but $GUI_SS_DEFAULT_UPDOWN alone puts the UpDown to the left of the Input. This is because UpDownConstants.au3 has
    Global Const $GUI_SS_DEFAULT_UPDOWN = $UDS_ALIGNLEFT

    To me, $GUI_SS_DEFAULT_* are equivalent to -1. AutoIt Help says that -1 means $UDS_ALIGNRIGHT. Right is where you expect to see an UpDown. So Koda should use $UDS_ALIGNRIGHT until AutoIt fixes $GUI_SS_DEFAULT_UPDOWN.


	
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

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.

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?

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.

...chris

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.

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

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

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.

188KodaApplicationFeature RequestLowWhich form should open when you run Koda?UnconfirmedChris Haslam01.03.20112 Task Description

In 1.7.3.0, it appears that when I run Koda, the form that automatically opens is the last one changed (I am not sure of this).

I would like to see Koda start by opening the form that was active when Koda was last exited. This makes more sense to me.

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.

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.

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.

198KodaApplicationBug ReportLowWhen CBS_DROPDOWNLIST is set, Koda generate CBS_SIMPLE ...NewAdmin15.04.2011 Task Description

When CBS_DROPDOWNLIST is set, Koda generate CBS_SIMPLE instead.

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.

208KodaApplicationBug ReportLowCollection editor: name ofUnconfirmedChris Haslam21.04.20112 Task Description

The screen shot in the doc, proped_collection_editor.png, does not agree with Koda 1.7.3.2: the caption is different.

The doc page on the Listview columns editor calls it Collection editor. It is really Column editor?

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

Available keyboard shortcuts

Tasklist

Task Details

Task Editing