All Projects

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

IDProjectCategoryTask Type  ascSeveritySummaryStatusOpened byLast Edited
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.

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.

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.

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.

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.

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.

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

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

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

But Events Example is in Code Templates dialog

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.

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”

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?

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?

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.

Thoughts

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

Weird!

222KodaDocumentationBug ReportLowForm controlUnconfirmedChris Haslam04.05.20117 Task Description

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

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.

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)
GUISetState(@SW_SHOW)
#EndRegion ### END Koda GUI section ###
 
While 1
	$nMsg = GUIGetMsg()
	Switch $nMsg
		Case $GUI_EVENT_CLOSE
			Exit
 
	EndSwitch
#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)
GUISetState(@SW_SHOW)
#EndRegion ### END Koda GUI section ###
 
While 1
	$nMsg = GUIGetMsg()
	Switch $nMsg
		Case $GUI_EVENT_CLOSE
			Exit
 
	EndSwitch
WEnd
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?

230KodaApplicationBug ReportLowCombo: ItemIndex and TextUnconfirmedChris Haslam05.05.20112 Task Description

I take ItemIndex to be the ordinal number of the Item that is shown initially ref 1).

With a List, I have played with Text. It seems always to show the Item with the ordinal that is assigned to ItemIndex. So why does Koda have both ItemIndex and Text? Or should Text be read-only?

231KodaApplicationBug ReportLowCombo: RemarksUnconfirmedChris Haslam04.05.20111 Task Description

The doc
from WinXP the “visual” height of combo cannot be set. Height parameter is showing height of opened combo. Koda allow you to change it manually.

I don’t understand. Is the doc saying that the collapsed height is fixed by XP and up, but that the user can set (with the Height property) the expanded height? If so.I have not been able to see this.

232KodaApplicationBug ReportLowControl | PicUnconfirmedChris Haslam04.05.20111 Task Description

I have written:

sRealSize - Width and height are determined by original size of image

Is this correct?

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?

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.

236KodaApplicationBug ReportLowTreeView :PropertiesUnconfirmedChris Haslam04.05.20111 Task Description

I suggest that Images be called ImageList. This will be clearer.

I suggest that Items be called Nodes.

237KodaApplicationBug ReportLowListView PropertiesUnconfirmedChris Haslam04.05.2011 Task Description

I suggest that Images be called ImageList. Clearer

Alignment

I read the info on Alignment:

According to MSDN, the alignment of the leftmost column is always left-justified; it cannot be changed.

MSDN says in full:

If a column is added to a list-view control with index 0 (the leftmost column), it is always LVCFMT_LEFT. Setting other flags on column 0 does not override that alignment. Therefore if you keep inserting columns with index 0, the text in all columns are left-aligned. If you want the first column to be right-aligned or centered you can make a dummy column, then insert one or more columns with index 1 or higher and specify the alignment you require. Finally delete the dummy column.
  • Based on MSDN, Koda would not allow me to right justify column 0, Animal
  • So, following the MSDN procedure, I inserted another column and moved it up to be column 0.
  • I set Animal, now column 1, to right justified
  • I deleted column 0.

The form ran OK. The part of the generated code that does the ListView is here:

$ListView2 = GUICtrlCreateListView("Animal|Coat|Feet", 96, 384, 169, 113)
GUICtrlSendMsg(-1, $LVM_SETCOLUMNWIDTH, 0, 50)
GUICtrlSendMsg(-1, $LVM_SETCOLUMNWIDTH, 1, 50)
GUICtrlSendMsg(-1, $LVM_SETCOLUMNWIDTH, 2, 50)
_GUICtrlListView_JustifyColumn(GUICtrlGetHandle($ListView2), 0, 1)
$ListView2_0 = GUICtrlCreateListViewItem("Lucas|furry|paws", $List

I am wondering whether Koda would be able to do the work-around automatically, rather than the user having to do it manually. Perhaps Koda would need to create a zero-width column 0 so Object Inspector would allow the first column that shows in Collection editor to be right or center justified.

Just a thought.

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.

241KodaApplicationBug ReportLowTab: HintUnconfirmedChris Haslam05.05.20111 Task Description

The doc says;

If one of pages has “Hint” property set, Koda will always generate GUICtrlSetTip for first page - this is the only way to correct setting tip to previous pages.

I am not sure what this means.

Here is what I think it may mean:

If you set a Hint for a page other than the first page, Koda will also generate a Hint for the first page.

Does this mean that a Hint will be set for all pages?

Is this an AutoIt limitation?

Is the Hint on the first page the same as on the subsequent page?

243KodaApplicationBug ReportLowToolbar | Button | HeightUnconfirmedChris Haslam05.05.20111 Task Description
  1. Selected Height value
  2. Pressed Del
  3. Pressed Enter

Exception
Exception handled 2011-05-04 at 22:35:49 by
is not a valid integer
Address:
about Source of
Method: Line:

Same thing happened when Backspace key (rather than Del) was pressed.

245KodaApplicationBug ReportLowToolbar: Properties: discrepancy between Koda and the d...UnconfirmedChris Haslam05.05.20111 Task Description

The following properties are in Object Inspector but not in the doc:

  • TAToolbar - Enabled, Height, Hint, Tab Order, Top, Visible, Width
  • TAToolButton - Caption, Enabled, Height, Hint, ImageIndex, Top, Visible, Width

Please tell me which should be added to the doc. (Some I know, e.g. ImageIndex)

247KodaApplicationBug ReportLowKoda menu | Help | ContentUnconfirmedChris Haslam05.05.2011 Task Description

The correct English usage is Contents. :-)

248KodaDocumentationBug ReportLowCreating a Tab control | new screenshotUnconfirmedChris Haslam06.05.2011 Task Description

Please update controls_tab_add.png, i.e. with Add a Page rather than New Page. I could do it, but my colors are different from yours.

249KodaApplicationBug ReportLowTab control: Hint being set for ccontrol on a pageUnconfirmedChris Haslam06.05.2011 Task Description

The attached .kxf file, when run, shows a Hint for the Label on the third Page. The Hint should be for the Page.

250KodaApplicationBug ReportLowToolbar : controls_toolbutton_add.pngUnconfirmedChris Haslam06.05.20111 Task Description

Please update this image with your selection color.

251KodaApplicationBug ReportLowToolbar | Style | tbsDropDownUnconfirmedChris Haslam06.05.2011 Task Description

A button with tbsDropDown does not show correctly when the form is run. Koda generates

_GUICtrlToolbar_AddButton($ToolBar1, 0, 20, 0, $BTNS_DROPDOWN)

The AutoIt help says:

_GUICtrlToolbar_AddButton($hWnd, $iID, $iImage[, $iString = 0[, $iStyle = 0[, $iState = 4[, $iParam = 0]]]])

Is this a code generator problem? Or is _GUICtrlToolbar flaky?

252KodaApplicationBug ReportLowMy first pass through the documentation is now completeUnconfirmedChris Haslam06.05.2011 Task Description

My first pass through the documentation is now complete, except for issues I have raised in open Bugtracker tasks. I will be proceeding to Pass 2. This will include replacing many #term_definitions with #remarks_headers.

255KodaApplicationBug ReportLowDummy: How to show Context MenuUnconfirmedChris Haslam11.05.20111 Task Description

How can I get a context menu to show when I press the accelerator key?

See attached for AutoIt error.

258KodaApplicationBug ReportLowdialog_generating_options.png is out of dateUnconfirmedChris Haslam08.05.20111 Task Description

Please update with your color scheme

259KodaApplicationBug ReportLowproped_treeview_editor.png: update from Item to NodeUnconfirmedChris Haslam08.05.20111 Task Description

Please

263KodaDocumentationBug ReportLowAdd styles and exstyles to documentation?UnconfirmedChris Haslam17.05.20112 Task Description

I am inclined to think that Styles and ExStyles should be added to the documentation – for each control in the Controls section. That way, Koda goes even further to being the “one stop” place for GUIs.

Any thoughts?

Include would make the process less painful. There are some WS_ constants that are available to almost all controls, so it would be nice to be able to include multiple rows of a table in one VAR. Can Include do this?

I would copy the stuff from AutoIt, perhaps doing some re-wording where I can make things clearer (but mostly the AutoIt doc is fairly clear on Styles).

The Styles for Form are a problem: Microsoft defined them in odd ways. I can’t do much about that!

Should I create a commstyle page like commctrl?

264KodaApplicationBug ReportLowChoose Script: move from startup to Tools | Update Scri...UnconfirmedChris Haslam23.05.20112 Task Description

I think that it would be more user-friendly to move Choose Script from start-up to when the info is needed, i.e. when the user first does Tools | Update Script in a session (and, of course, when more than one .au3 file uses the active form).

Choose Script would then be changed to ask: “Update which script?”. Otherwise the dialog would be the same as it is now.

Moving Choose Script would significantly help with the documentation effort. It is not documented because I haven’t thought of where to weave it in.

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)
Showing tasks 1 - 50 of 147 Page 1 of 31 - 2 - 3 -

Available keyboard shortcuts

Tasklist

Task Details

Task Editing