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
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)
269KodaApplicationBug ReportLowForm lacks WS_EX_CLIENTEDGE and WS_EX_STATICEDGEUnconfirmedChris Haslam17.05.2011 Task Description

AutoIt has constants for them

270KodaApplicationBug ReportLowButton: SS_RIGHTJUST available but no way of specifying...UnconfirmedChris Haslam18.05.20112 Task Description

Also: should I remove mention if image from SS_CENTERIMAGE?

271KodaApplicationBug ReportLowInput styles: some suggested changesUnconfirmedChris Haslam18.05.20111 Task Description

I think that ES_MULTILINE should not appear in Object Inspector because an InputBox is by definition single-line.

ES_WANTRETURN is irrelevant to Input box because InputBox is single-line, so I think that it should not appear in Object Inspector. Same for ES_AUTOVSCROLL and WS_VSCROLL.

In C/C++, WS_GROUP is the way of marking a control as the first in a group, and another control as the last in the group. But AutoIt uses, and Koda generates, a pair of calls to GUICtrlCreateGroup. So I suggest removing WS_GROUP from TAInput in Object Inspector. The fewer styles there are, the easier it is for a user: some scrolling down is inevitable, but the less he needs to do so the less likely he is to miss a style that he needs to check or uncheck.

Koda shows WS_VISIBLE as forced, but AutoIt doesn’t. Further, WS_VISIBLE remains checked even when Visible is False. I suggest removing WS_VISIBLE.

I think that WS_CHILD only applies to Forms. So I suggest removing it from Object Inspector | TAInput.

With WS_HSCROLL checked, when a Form is run, the scroll bar is drawn over the Text. Koda insists that the Height be 21. It needs to allow a larger height when WS_HSCROLL is checked.

272KodaApplicationBug ReportLowLabel styles: some suggested changesUnconfirmedChris Haslam15.06.20111 Task Description

SS_NOTIFY is shown as checked and forced, even when OnCick has not been specified. But notification can be set/reset in OnClick. So I suggest removing SS_NOTIFY. I wonder whether SS_NOTIFY will work for a Label.

n C/C++, WS_GROUP is the way of marking a control as the first in a group, and another control as the last in the group. But AutoIt uses, and Koda generates, a pair of calls to GUICtrlCreateGroup. So I suggest removing WS_GROUP from TALabel in Object Inspector. The fewer styles there are, the easier it is for a user: some scrolling down is inevitable, but the less he needs to do so the less likely he is to miss a style that he needs to check or uncheck.

Koda shows WS_VISIBLE as forced, but AutoIt doesn’t. Further, WS_VISIBLE remains checked even when Visible is False. I suggest removing WS_VISIBLE.

I think that WS_CHILD only applies to Forms. So I suggest removing it from Object Inspector | TALabel.

273KodaApplicationBug ReportLowEdit styles: some suggested changesUnconfirmedChris Haslam09.06.20111 Task Description

I think that ES_MULTILINE should not appear in Object Inspector because an EditBox is by definition multi-line.

In C/C++, WS_GROUP is the way of marking a control as the first in a group, and another control as the last in the group. But AutoIt uses, and Koda generates, a pair of calls to GUICtrlCreateGroup. So I suggest removing WS_GROUP from TAEdit in Object Inspector. The fewer styles there are, the easier it is for a user: some scrolling down is inevitable, but the less he needs to do so the less likely he is to miss a style that he needs to check or uncheck.

Koda shows WS_VISIBLE as forced, but AutoIt doesn’t. Further, WS_VISIBLE remains checked even when Visible is False. I suggest removing WS_VISIBLE.

I think that WS_CHILD only applies to Forms. So I suggest removing it from Object Inspector | TAEdit.

274KodaApplicationBug ReportLowButton styles: some suggested changesUnconfirmedChris Haslam11.06.20112 Task Description

Microsoft and AutoIt say that BS_PUSHLIKE applies to Checkbox and Radio, but not to Button. I suggest removing it from Button.

BS_ICON and BS_BITMAP: I think these are redundant because the user tells Koda which icon or bitmap to use in Picture.

WS_GROUP, WS_VISIBLE and WS_CHILD: see discussion in FS$273

275KodaApplicationBug ReportLowCheckbox styles: some suggested changesUnconfirmedChris Haslam06.06.20112 Task Description

WS_GROUP, WS_VISIBLE and WS_CHILD: see discussion in FS#273

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.

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

...chris

278KodaApplicationBug ReportLowTAGroup styles - some suggestionsUnconfirmedChris Haslam19.05.2011 Task Description

BS_RIGHTBUTTON: does not seem to do anything. So perhaps remove it from OI.

BS_GROUPBOX: redundant in TAGroup. So perhaps remove it from OI.

WS_GROUP: irrelevant to code generation. AutoIt normally uses GuiCtrlCreateGroup. So perhaps remove it from OI.

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.

281KodaApplicationBug ReportLowTAPic styles: some suggestionsUnconfirmedChris Haslam20.05.2011 Task Description

I suggest not showing SS_BITMAP in OI because it is redundant and, for AutoIt, incorrect: AutoIt supports BMP, JPG, and GIF.

For transparency, Form needs WS_EX_LAYERED, so perhaps this should be added to Form.

I do not see how SS_NOPREFIX applies to Pic.

282KodaApplicationBug ReportLowIcon styles: some suggestionsUnconfirmedChris Haslam11.06.20112 Task Description

SS_ICON: could be dropped from OI because it doesn’t add any info: TAIcon only handles, and requires, an icon.

SS_PREFIX applies to text, but TAIcon has no text.

FS#281 relates

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.

284KodaApplicationBug ReportLowTreeview styles: some suggestionsUnconfirmedChris Haslam20.05.2011 Task Description

TVS_LINESATROOT is only intended by MS to work if TVS_HASLINES is also set, so Koda should check TVS_HASLINES when user checks TVS_LINESATROOT.

TVS_FULLROWSELECT is only intended by MS to work if TVS_HASLINES is not set, so Koda should uncheck TVS_HASLINES when user checks TVS_FULLROWSELECT.

TVS_NOTOOLTIPS and TVS_INFOTIP show in OI but Treeview Editor does not provide a way of entering tool tips. AutoIt only seems to provide ways of setting tool tips via GUICtrlSendMsg or by calling a UDF. So I suggest removing these two styles from OI for now.

285KodaApplicationBug ReportLowListview styles: some suggestionsUnconfirmedChris Haslam15.07.20112 Task Description
  1. Icon and SmallIcon views are available in AutoIt so LVS_ICON and LVS_SMALLICON should not be disabled. The points below assume the present situation: only List and Report view available. I have added to the doc “At this time, only Report and List views are available in Koda”.
  1. Koda can know that if if there are Columns, the view is Report else it is List. So until Icon and SmallIcon views are added, LVS_LIST and LVS_REPORT could be removed.
  1. With LVS_LIST checked, Koda generated BitOr($GUI_SS_DEF_LV,LVS_SMALLICON). It so happens that this has the same value as LVS_LIST – but untidy :-)
  1. LVS_COLUMNHEADERS only applies to Report style, so it should be disabled when LVS_LIST is checked
  1. Collection editor: if you enter only one row, no column header is created
  1. LVS_NOSORTHEADER should be removed from OI because it doesn’t work and AutoIt help says that double-click to sort rhas not been implemented.
  1. Multiple selection only works in Report view so LVS_SINGLESEL should be disabled in List view.
  1. Check LVS_SORTASCENDING and then check LVS_SORTDESCENDING: LVS_SORTASCENDING is still checked. Because mask is missing from styles.xml.
  1. LVS_AUTOARRANGE, LVS_ALIGNTOP and LVS_ALIGNLEFT are only intended for Icon and SmallIcon views, so should be removed.
  1. LVS_ALIGNTOP will not uncheck.
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?

287KodaApplicationBug ReportLowTab styles: some suggestionsUnconfirmedChris Haslam21.05.2011 Task Description

TCS_SCROLLOPPOSITE: I am not sure what this is supposed to do, but it does not seem to do anything. Googling didn’t help. Perhasp it should be removed from OI.

TCS_TOOLTIPS: There is no Hint property for a Page. Remove it from OI until there is?

See the doc for the many requirements. It would be good to have OI help the user not to choose combinations of styles that MS does not intend to work.

289KodaApplicationBug ReportLowToolbar: suggested changesUnconfirmedChris Haslam22.05.20111 Task Description

TBSTYLE_TOOLTIPS: not needed in OI because Koda knows whether Hints have been specified. So suggest remove TBSTYLE_TOOLTIPS for now.

TBSTYLE_ALTDRAG: Doc would say “Allows changing a button’s position by Alt-dragging it, rather than Shift-dragging it. Requires CCS_ADJUSTABLE”. Also doc would describe CCA_ADJUSTABLE as “enables user to add, delete, and rearrange buttons”. CCA_ADJUSTABLE is defined in Constants.au3. Suggesting adding styles is beyond my current scope, so I suggest removing TBSTYLE_ALTDRAG for now.

TBSTYLE_LIST does not seem to work, so I suggest removing it from OI.

TBSTYLE_CUSTOMERASE: Doc would say “Generates NM_CUSTOMDRAW notification codes when toolbar processes WM_ERASEBKGND messages”. This is not generated by Koda, so I suggest removing it from OI.

TBSTYLE_REGISTERDROP: Doc would say “Generates TBN_GETOBJECT notification codes to request drop target objects when the cursor passes over toolbar buttons”. This is not generated by Koda, so I suggest removing it from OI.

Extended Styles: Bug: won’t stay checked, so can’t test them.

TBSTYLE_EX_MIXEDBUTTONS: Requires TBSTYLE_LIST, which doesn’t seem to work. So I suggest removing TBSTYLE_EX_MIXEDBUTTONS from OI.

TBSTYLE_EX_HIDECLIPPEDBUTTONS: AutoIt help says “Hides partially clipped buttons”. To me buttons could only be partly clipped if buttons were added. CCS_ADJUSTABLE is not in OI, so I suggest removing TBSTYLE_EX_HIDECLIPPEDBUTTONS for now.

290KodaApplicationBug ReportLowTab Sequence (Order) Editor: a proposal UnconfirmedChris Haslam23.05.2011 Task Description

I am attaching a screen shot of what I have in mind. This dialog would be accessible from Edit | Tab Order and from each real (not substitute) control. From the menu, it would appear as in the screen shot. From a control, if the control is a group, the group would be highlighted. If the control is not in a group, Form1 would be highlighted.

Note that Koda would not show sequence numbers of tabstops. This would be internal to fd.exe. Users won’t need sequence numbers if they have the information visually. The user would no longer have to think the numbers. With the proposed dialog, he would get all the tabstop info in one place. This makes sense to me because tabstops are really inter-control rather than intra-control.

Optimally, Add would only be enabled when the Not tabstops .. list has focus and an item is selected. Up, Down and Remove would only be enabled when the Tabstops list has focus and an item is selected (and of course, Up would be disabled if the top item is selected, and Down would disabled if the last item is selected).

If this proposal is implemented, I would suggest:

  • In Properties, Tab Order would be replaced with Tabstop, which would be read-only boolean , with a ... button to the right to access the Editor
  • In Styles, WS_TABSTOP would be removed. fd.exe would continue to track WS_TABSTOP.

It is possible that, early in designing a form, a user may wish to make some controls tabstops, and others not; he may wish to refine the order later. So the Tabstop property could be read-write. If it is, I suggest:

  • If the user changes Tabstop for a control from False to True, the control would be placed at the end of the Tabstops list
  • If the user changes Tabstop for a control from True to False, the control would be moved from the Tabstops list to the Not tabstops, but can be list.
  • For Label (and other controls that cannot be tabbed to), the Tabstop property would be set to False and would be read-only.

I acknowledge that AutoIt tabs in the order in which calls to GuiCtrl functions that specify WS_TABSTOP appear in the script. The code generator could generate in the order shown: first the Tabstop list (with WS_TABSTOP set), then the others (without TABSTOP set), although this is not requisite.

I think that this proposal mostly improves the UI. It does clear up what I called an inconsistency in my previous post – although I may be wrong. I think that the code under the hood will change very little.

I have done some playing with (and thinking about) the names of the lists. Alternative names are: Un-tabable, Potential tabstops and Tabstops. I don’t like Un-tabable because it is bad English.

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.

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.

293KodaApplicationBug ReportLowForm style DS_FOREGROUND: Autoit only supports partiall...UnconfirmedChris Haslam26.05.2011 Task Description

Microsoft says of DS_FOREGROUND:

Causes the system to use the SetForegroundWindow function to bring the dialog box to the foreground

AutoIt does not seem to provide SetForegroundWindow functionality.

So I suggest the DS_FOREGROUND be removed.

WS_EX_TOPMOST provides “stay on top”.

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.

297KodaApplicationBug ReportLowPic Properties | PictureAssignedChris Haslam16.06.2011 Task Description

Properties | Picture always seems to show None even when a .bmp is loaded and appears in the Design Area.

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.

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

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.
302KodaApplicationBug ReportLowEtched Horizontal Labels and TabsUnconfirmedSect20.06.20111 Task Description

I noticed that labels with the style SS_ETCHEDHORZ would shrink when you switched tabs. It could be a bug in aligning to grid as it seems to step down 4 pixels on change.

303KodaApplicationBug ReportLowAU3 Import: BugAssignedChris Haslam19.06.2011 Task Description

I pasted this from the Clipboard (not expecting it to work):

	$testForm = GUICreate("Test Form", $vec[2]-20, $vec[3]-30, $vec[0]+10, $vec[1]+15,$WS_POPUP)
	Local $height = 17
	If IsChecked($chkHorizBar) Then $height = 35
	$t = "Koda"
	GUICtrlCreateInput($t, 8, 8, $vec[3]-16, $height,$gParamStyles,$gParamExStyles)
	GUICtrlCreateLabel("Press Esc key to continue", 8, 80, 164, 40)

and clicked on Process.

I got:

Exception handled 2011-06-19 at 17:41:29 by MainExceptionHandler
Could not convert variant of type (String) into type (Boolean)
Exception Address: 00410E21
Information about Source of Exception
Unit: Variants
Method: HandleConversionException
Line: 0

I expected graceful failure.

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?

306KodaApplicationBug ReportLowGenerate Code button | Save to fileUnconfirmedChris Haslam25.06.20112 Task Description
  1. I created a form in the Design Area but did not save it.
  2. I clicked the Generate icon.
  3. At the Code window, “Save to file” showed. I clicked on it.
  4. Koda said “Your current form is not saved. In order to use the Update function, you must save the form before saving the script”.

But I wasn’t using the Update function, so I suggest that “In order to use the Update function” be dropped from this messagebox.

BTW Yesterday I met a message that contained “it’s”. There is a growing tendency in English usage to use “it’s” rather than “its”. Correct usage is:

  • “it’s” is the abbreviated form of “it is”, just as “wasn’t” is an abbreviated form of “was not”. The “‘” shows that one or more characters are missing.
  • “its” is an exception to the general rule that “‘s” indicates possession, as in “Koda’s design”, which is exactly equivalent to “the design of Koda”
  • “its design” is good English.

There are cases in computer-eze where I do use “‘s” to indicate a plural because it seems to be the only way to be clear. An example: “there are five #include’s in my script”. :-)

308KodaApplicationBug ReportLowListbox test form includes GUIListBox.au3AssignedChris Haslam27.06.20111 Task Description

Should be ListBox.au3

See attached file

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

Probably not used much, but should be there.

310KodaApplicationBug ReportLow#Region includes pathUnconfirmedChris Haslam25.06.2011 Task Description

When code is generated for the attached .kxf, the #Region line is:

> #Region ### START Koda GUI section ### Form=F:\AutoIt scripts\Koda devel\Styles dialogs\List styles suggestion.kxf

I don’t know how the path got included in this line. I can tell you that I did the following early in developing the List script:

  • In Koda, saved the Group script as List styles suggestion.kxf in F:\AutoIt scripts\Koda devel\Styles dialogs
  • Changed Group to List in the form, and saved it again
  • Saved the Group script as List script
  • Changed the #Region line from Group to List
  • Exited Koda and ran it again
  • Chose Update script

Now Update script complains some of the time when I do Update script.

I know that on one occasion when I had trouble, I had most recently saved F:\AutoIt scripts\Koda devel\Listbox example.kxf. I had exited Koda and had run it again. I then probably opened the List script, then closed Listbox example.kxf. So for a time, forms in 2 different directories were open.

Sorry I can’t be more specific.

Now Update script is working OK. But I note that Generate shows the full path yet only fnam.ext is in the #Region line in the script.

I will try to be more specific when it happens again.

BTW The List form and script are still being designed.

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.

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 51 - 100 of 147 Page 2 of 3 - 1 - 2 - 3 -

Available keyboard shortcuts

Tasklist

Task Details

Task Editing