|
339 | Koda | Application | Bug Report | High | I can't rename tab control | Unconfirmed | Vo Anh Kiet | 15.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
|
|
338 | Koda | Application | Bug Report | Medium | Lock controls in designer | Unconfirmed | Henrik | 24.08.2014 |
Task Description
The function “Edit→Control→Lock” works only in the actually reloading the “KXF”-file, the “LOCK” no longer works.
|
|
337 | Koda | Import | Bug Report | Medium | Using parenthesis "()" in tab names, breaks import. | Unconfirmed | Vitaliy Maksimov | 24.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
|
|
336 | Koda | Application | Bug Report | Low | Height property value of certain fields (input, combobo... | Unconfirmed | vvoois | 18.09.2013 |
Task Description
I have been working with Koda for quite a few years of the most annoying parts of the GUI editor is where i alter the height of inputboxes, comboboxes etc and adjust them to a value where these objects become smaller than the original value (input boxes have a value of 21, i rather cram the contents in 16 pixels which works just as nice).
Koda does accept it and adjusts on the form, but the minute i do something with the form in general or drag the object that is carrying it (frame) somewhere else, the height-value is being set back to the original can also save the form with its values, but when i reload, all values are reset to the original values that seem to be the “minimum” for those objects.
I rather don’t have Koda to touch these properties in any situation, they are manually adjusted for a reason.
|
|
335 | Koda | Application | Bug Report | Medium | Any objects (buttons, edit boxes) always snapping/resiz... | Unconfirmed | Trevor Blanc | 24.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.
|
|
334 | Koda | Application | Bug Report | Low | Code Generator Template being ignored? | Unconfirmed | David | 22.10.2012 |
Task Description
I created a duplicate of the “Events Example” template, renamed it, then edited it to my I select the new template and generate code, the code is still based on “Events Example” instead of my template.
|
|
333 | Koda | Application | Bug Report | Low | label width value is being forgotten | Unconfirmed | Vitas | 22.10.2012 |
Task Description
I have some labels in my program but when I set longer text in them it overflows and line breaks. So I prolonged them in Koda, saved, updated script with CTRL+U and it worked. Unfortunatelly next time after opening the KXF file I found all labels to have width and height reset back to the values set after their creation! Pretty dumb...I think this is a bug I found out it happens not only after reopening the form, but randomly during development when the project is open. The only workaround seems to be to add a lot of spaces to a label’s caption
|
|
324 | Koda | Application | Bug Report | Medium | Columns are lost when copying Listview | Unconfirmed | Christian | 21.04.2012 |
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)
|
|
323 | Koda | Application | Bug Report | High | $UDS_ARROWKEYS not defined | Unconfirmed | V@no | 27.12.2011 |
Task Description
When added a updown control and enabled UDS_ARROWKEYS style it fails run the generated code is <UpdownConstants.au3></code>
|
|
322 | Koda | Application | Bug Report | Low | access vilolation error | Unconfirmed | wenyibing | 24.10.2011 |
Task Description
I added a listbox, deleted it, and then was adding a combobox. A error window popped up. See using the latest version. My OS is Windows 7 64bit.
|
|
298 | Koda | Application | Bug Report | Low | Styles dialogs suggestions | Unconfirmed | Chris Haslam | 08.09.2011 |
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.
|
|
321 | Koda | Application | Bug Report | Low | TAListView: code generation funny | Unconfirmed | Chris Haslam | 15.07.2011 |
Task Description
$ListView1 = GUICtrlCreateListView("|", 128, 56, 257, 289, BitOR($GUI_SS_DEFAULT_LISTVIEW,$LVS_NOCOLUMNHEADER))
was generated by Koda, and does not work with 2 columns: the second column shows as blank.
$ListView1 = GUICtrlCreateListView(" | ", 128, 56, 257, 289, BitOR($GUI_SS_DEFAULT_LISTVIEW,$LVS_NOCOLUMNHEADER))
does work.
Koda then generated:
GUICtrlSendMsg(-1, $LVM_SETCOLUMNWIDTH, 0, 50)
GUICtrlSendMsg(-1, $LVM_SETCOLUMNWIDTH, 1, 200)
Apparently AutoIt needs a space before and after the |.
I consider this to be an AutoIt bug, but Koda is the servant of AutoIt, so ...
If AutoIt ever fixes this bug, Koda code generation will still be OK with “<space>|<space> “.
|
|
285 | Koda | Application | Bug Report | Low | Listview styles: some suggestions | Unconfirmed | Chris Haslam | 15.07.2011 |
Task Description
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”.
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.
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
LVS_COLUMNHEADERS only applies to Report style, so it should be disabled when LVS_LIST is checked
Collection editor: if you enter only one row, no column header is created
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.
Multiple selection only works in Report view so LVS_SINGLESEL should be disabled in List view.
Check LVS_SORTASCENDING and then check LVS_SORTDESCENDING: LVS_SORTASCENDING is still checked. Because mask is missing from styles.xml.
LVS_AUTOARRANGE, LVS_ALIGNTOP and LVS_ALIGNLEFT are only intended for Icon and SmallIcon views, so should be removed.
LVS_ALIGNTOP will not uncheck.
|
|
320 | Koda | Application | Bug Report | Low | Designer: How to keep Object Inspector on top | Unconfirmed | Chris Haslam | 13.07.2011 |
Task Description
I am working on the ListView styles dialog. It is almost full-screen: about 40 controls.
I would like to keep Object Inspector on top of the Form. When I am working on controls on the right-hand side, it can sit over the left side of the form. How do I do it? OI keeps getting under the Form.
|
|
309 | Koda | Application | Bug Report | Low | TAList: Caption missing from Properties | Unconfirmed | Chris Haslam | 08.07.2011 |
Task Description
Probably not used much, but should be there.
|
|
319 | Koda | Application | Bug Report | Low | Hint or Tooltip? | Unconfirmed | Chris Haslam | 08.07.2011 |
Task Description
Koda calls them hints but AutoIt and Windows call them tooltips.
I think that Koda should use the same term as AutoIt.
Right now, the Treeview Styles dialog has a checkbox called Hints (tooltips) show.
|
|
318 | Koda | Application | Bug Report | Low | TAMonthCal: Centering problem | Assigned | Chris Haslam | 08.07.2011 |
Task Description
The auto-height seems to be correct at 168, but the vertical centering is off a bit, so when Autosize is True, the bottom of the Today line is hidden.
It is likely that there are other cases where centering is a bit off, e.g. Align | Center Vertically in Window.
|
|
311 | Koda | Application | Bug Report | Low | TAEDIT: bad line wrapping with custom font | Unconfirmed | Chris Haslam | 07.07.2011 |
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.
|
|
313 | Koda | Application | Bug Report | Low | Background color: entering numeric values | Unconfirmed | Chris Haslam | 06.07.2011 |
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.
|
|
317 | Koda | Application | Bug Report | Low | AU3 Import GuiCtrlSetData bug | Unconfirmed | Chris Haslam | 06.07.2011 |
Task Description
The first attached file shows AU3 Import code I pasted. (It is from Date Picker styles with presets suggestion.au3.)
The second shows the result of clicking on Process.
It appears that Koda did not process the GuiCtrlSetData.
|
|
314 | Koda | Application | Bug Report | Low | File | Open: Split into two? | Unconfirmed | Chris Haslam | 06.07.2011 |
Task Description
I think it would be clearer if File | Open were split into two:
The filter on the first one would be *.kxf, and on the second *.au3
I realize that Open Forms in Script is not optimum, but I think it would be an improvement on the present situation. It could have a hint: Open all forms referenced in a script.
|
|
312 | Koda | Application | Feature Request | Low | Undoing strings | Unconfirmed | Chris Haslam | 06.07.2011 |
Task Description
It would make sense to me to have one Ctrl_Z undo all changes to a string, rather than character-by-character.
|
|
316 | Koda | Application | Bug Report | Low | Font size inconsistent for Courier New | Unconfirmed | Chris Haslam | 04.07.2011 |
Task Description
The attached .kxf shows one font size in Design Area and a smaller size when run.
This problem may be related to another. This dialog shows as designed if I change the font size to 8.5 points in AutoIt. Koda won’t let me set the font size to 8.5.
|
|
315 | Koda | Application | Bug Report | Low | Send to Back, Bring to Front: bug? | Unconfirmed | Chris Haslam | 04.07.2011 |
Task Description
The attached .kxf does not display as I would expect.
|
|
152 | Koda | Application | Bug Report | Low | TAUpdown: Appearance in Preview is inconsistent with ap... | Assigned | Chris Haslam | 30.06.2011 |
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.
|
|
308 | Koda | Application | Bug Report | Low | Listbox test form includes GUIListBox.au3 | Assigned | Chris Haslam | 27.06.2011 |
Task Description
Should be ListBox.au3
See attached file
|
|
310 | Koda | Application | Bug Report | Low | #Region includes path | Unconfirmed | Chris Haslam | 25.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.
|
|
306 | Koda | Application | Bug Report | Low | Generate Code button | Save to file | Unconfirmed | Chris Haslam | 25.06.2011 |
Task Description
I created a form in the Design Area but did not save it.
I clicked the Generate icon.
At the Code window, “Save to file” showed. I clicked on it.
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”.
|
|
300 | Koda | Application | Bug Report | Low | Multiple selection of controls within a Group | Unconfirmed | Chris Haslam | 25.06.2011 |
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.
|
|
304 | Koda | Application | Bug Report | Low | Button icon bug: not visible at run time | Assigned | Chris Haslam | 24.06.2011 |
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?
|
|
299 | Koda | Application | Bug Report | Low | File | Recent Files: non-existent file | Unconfirmed | Chris Haslam | 21.06.2011 |
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”.
|
|
302 | Koda | Application | Bug Report | Low | Etched Horizontal Labels and Tabs | Unconfirmed | Sect | 20.06.2011 |
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.
|
|
303 | Koda | Application | Bug Report | Low | AU3 Import: Bug | Assigned | Chris Haslam | 19.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.
|
|
297 | Koda | Application | Bug Report | Low | Pic Properties | Picture | Assigned | Chris Haslam | 16.06.2011 |
Task Description
Properties | Picture always seems to show None even when a .bmp is loaded and appears in the Design Area.
|
|
272 | Koda | Application | Bug Report | Low | Label styles: some suggested changes | Unconfirmed | Chris Haslam | 15.06.2011 |
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.
|
|
279 | Koda | Application | Bug Report | Low | Graphics: graphic may not show in control | Assigned | Chris Haslam | 14.06.2011 |
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.
|
|
280 | Koda | Application | Bug Report | Low | Graphics styles: some suggestions | Unconfirmed | Chris Haslam | 11.06.2011 |
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.
|
|
274 | Koda | Application | Bug Report | Low | Button styles: some suggested changes | Unconfirmed | Chris Haslam | 11.06.2011 |
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
|
|
286 | Koda | Application | Bug Report | Low | Statusbar styles: some suggestions | Assigned | Chris Haslam | 11.06.2011 |
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?
|
|
282 | Koda | Application | Bug Report | Low | Icon styles: some suggestions | Unconfirmed | Chris Haslam | 11.06.2011 |
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
|
|
283 | Koda | Application | Bug Report | Low | Slider styles: some suggestions | Unconfirmed | Chris Haslam | 10.06.2011 |
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.
|
|
292 | Koda | Application | Bug Report | Low | Form styles: Code generation error | Unconfirmed | Chris Haslam | 10.06.2011 |
Task Description
Style 94C8 0000 generates $WS_SYSMENU,$WS_POPUP. It should generate $WS_POPUPWINDOW, $WS_CAPTION.
|
|
277 | Koda | Application | Bug Report | Low | Menutitem: Object Inspector shows styles and exstyles f... | Unconfirmed | Chris Haslam | 10.06.2011 |
Task Description
...chris
|
|
291 | Koda | Application | Bug Report | Low | Form styles: a few definitely don't belong to Form | Unconfirmed | Chris Haslam | 09.06.2011 |
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.
|
|
273 | Koda | Application | Bug Report | Low | Edit styles: some suggested changes | Unconfirmed | Chris Haslam | 09.06.2011 |
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.
|
|
275 | Koda | Application | Bug Report | Low | Checkbox styles: some suggested changes | Unconfirmed | Chris Haslam | 06.06.2011 |
Task Description
WS_GROUP, WS_VISIBLE and WS_CHILD: see discussion in FS#273
|
|
158 | Koda | Application | Bug Report | Low | TALabel: Autosize | Assigned | Chris Haslam | 03.06.2011 |
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
|
|
296 | Koda | Application | Bug Report | Low | TAList: Code Generator error | Assigned | Chris Haslam | 01.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.
|
|
77 | Koda | Application | Feature Request | Low | Making Code Templates more flexible | Waiting feedback | David | 30.05.2011 |
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.
|
|
294 | Koda | Application | Bug Report | Medium | Adding context menu to an icon error in on event mode | Assigned | Martin Gibson | 29.05.2011 |
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
|