All Projects

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

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

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

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

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

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.

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.

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.

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?

269KodaApplicationBug ReportLowForm lacks WS_EX_CLIENTEDGE and WS_EX_STATICEDGEUnconfirmedChris Haslam17.05.2011 Task Description

AutoIt has constants for them

268KodaApplicationFeature RequestLowForm | WS_EX_ACCEPTFILES requires GUI_DROPACCEPTED in o...UnconfirmedChris Haslam17.05.2011 Task Description

I don’t see how to check GUI_DROPACCEPTED in Edit control.

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.

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

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?

261KodaApplicationFeature RequestLowDisable a tabstopUnconfirmedChris Haslam24.05.20117 Task Description

An example from External Link:

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

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

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

Please

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

Please update with your color scheme

257KodaDocumentationRegular TaskLowProblem updating menu_align.pngUnconfirmedChris Haslam11.05.20112 Task Description

menu_align.png had Horizontal rather than Horizontally. etc.

I uploaded an updated version, but the old version still shows.

New version is attached.

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.

253KodaDocumentationRegular TaskLowCombobox | Remarks | Height parameterUnconfirmedChris Haslam19.05.20111 Task Description

The doc as I received it says:

Starting 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 quite understand.

Does this say the same thing:

Windows XP and up set the opened height of a Combobox. The Height property is the height of the closed Combobox.

My playing around shows that the height of the closed control is fixed in Design Area and at run-time (perhaps font-size dependent), and that when opened, the height is sufficient to show at least 15 items.

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.

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?

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

Please update this image with your selection color.

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.

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.

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

The correct English usage is Contents. :-)

246KodaApplicationRegular TaskLowOptions | Options | General | Recent Files 2UnconfirmedChris Haslam06.05.20111 Task Description

I notice that the caption in 1.7.3.1 is Number of recent file list. This does not make sense to me. It makes it look like recent file list has an ID number (or something).

I wrote:

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.

Other wordings are possible.

Number of is redundant: the input box shows numbers.

:-)

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)

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.

242KodaApplicationFeature RequestLowIP address: EnabledAssignedChris Haslam11.05.20115 Task Description

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

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?

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.

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.

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.

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.

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?

233KodaApplicationBug ReportLowCannot set OnClick to be noneUnconfirmedMartin Gibson04.05.20112 Task Description

The OnClick property does not work for me if I choose none. With none I expect that there will be no line GuiCtrlSetOnEvent for that control and for lots of things, like labels, I might not have an event.

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?

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.

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?

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?

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

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.

222KodaDocumentationBug ReportLowForm controlUnconfirmedChris Haslam04.05.20117 Task Description

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

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!

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?

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.

217KodaApplicationFeature RequestLowStrings Editot | Show Hard Return?UnconfirmedChris Haslam26.04.20111 Task Description

It would be nice if Hard Return showed. My experience elsewhere is that, because the width of the Edit control and the width of the Strings Editor are usually different, showing HRt can relieve some confusion.

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

Showing tasks 51 - 100 of 147 Page 2 of 3 - 1 - 2 - 3 -

Available keyboard shortcuts

Tasklist

Task Details

Task Editing