|
4 | Koda | Application | Feature Request | Low | Save chosen template as one of form options | Assigned | Admin | 13.11.2008 |
Task Description
Save chosen template as one of form options.
|
|
6 | Koda | Application | Feature Request | Low | Not rename form when loading (Form1->Form1_1) | Assigned | Admin | 13.11.2008 |
Task Description
Not rename form when loading (Form1?Form1_1)
|
|
8 | Koda | Application | Feature Request | Low | Customizing fonts | Assigned | Admin | 13.11.2008 |
Task Description
Customizing fonts (by EulerG)
|
|
11 | Koda | Application | Feature Request | Low | Remove ClientWidth/ClientHeight | Assigned | Admin | 13.11.2008 |
Task Description
Remove ClientWidth/ClientHeight for the Form (Make Width=ClientWidth etc)
|
|
24 | Koda | Application | Bug Report | Low | Generation options dialog is loose indent char selectio... | Assigned | Admin | 06.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.
|
|
79 | Koda | Application | Feature Request | Low | RichEdit custom control | Assigned | Admin | 15.10.2009 |
Task Description
RichEdit custom control since it’s UDF was added in the standard distributive.
|
|
129 | Koda | Application | Bug Report | Medium | Dummy controls appears behind menus | Assigned | Admin | 15.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.
|
|
141 | Koda | Application | Bug Report | Low | Ability to generate more then one tab on one form | Postponed | Admin | 07.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.
|
|
161 | Koda | Application | Feature Request | Low | Auto-sizing in Radio and Checkbox controls | Postponed | Chris Haslam | 02.02.2011 |
Task Description
Auto-sizing in Radio and Checkbox controls would be useful. Default should be False. Put it on the wish list?
|
|
198 | Koda | Application | Bug Report | Low | When CBS_DROPDOWNLIST is set, Koda generate CBS_SIMPLE ... | New | Admin | 15.04.2011 |
Task Description
When CBS_DROPDOWNLIST is set, Koda generate CBS_SIMPLE instead.
|
|
214 | Koda | Application | Bug Report | Low | TrayMenu | Undo | Assigned | Chris Haslam | 21.04.2011 |
Task Description
I clicked on New Form icon
I created a Tray Menu control
I added File as a menu item and gave it Exit as a sub-menu item
I did Ctrl_Z several times
I was then unable to select the form.
|
|
237 | Koda | Application | Bug Report | Low | ListView Properties | Unconfirmed | Chris Haslam | 04.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.
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.
|
|
247 | Koda | Application | Bug Report | Low | Koda menu | Help | Content | Unconfirmed | Chris Haslam | 05.05.2011 |
Task Description
The correct English usage is Contents.
|
|
248 | Koda | Documentation | Bug Report | Low | Creating a Tab control | new screenshot | Unconfirmed | Chris Haslam | 06.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.
|
|
249 | Koda | Application | Bug Report | Low | Tab control: Hint being set for ccontrol on a page | Unconfirmed | Chris Haslam | 06.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.
|
|
251 | Koda | Application | Bug Report | Low | Toolbar | Style | tbsDropDown | Unconfirmed | Chris Haslam | 06.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?
|
|
252 | Koda | Application | Bug Report | Low | My first pass through the documentation is now complete | Unconfirmed | Chris Haslam | 06.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.
|
|
268 | Koda | Application | Feature Request | Low | Form | WS_EX_ACCEPTFILES requires GUI_DROPACCEPTED in o... | Unconfirmed | Chris Haslam | 17.05.2011 |
Task Description
I don’t see how to check GUI_DROPACCEPTED in Edit control.
|
|
269 | Koda | Application | Bug Report | Low | Form lacks WS_EX_CLIENTEDGE and WS_EX_STATICEDGE | Unconfirmed | Chris Haslam | 17.05.2011 |
Task Description
AutoIt has constants for them
|
|
276 | Koda | Application | Bug Report | Low | TAComboBox: Height behaviour abnormal | Assigned | Chris Haslam | 19.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.
|
|
278 | Koda | Application | Bug Report | Low | TAGroup styles - some suggestions | Unconfirmed | Chris Haslam | 19.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.
|
|
281 | Koda | Application | Bug Report | Low | TAPic styles: some suggestions | Unconfirmed | Chris Haslam | 20.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.
|
|
284 | Koda | Application | Bug Report | Low | Treeview styles: some suggestions | Unconfirmed | Chris Haslam | 20.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.
|
|
287 | Koda | Application | Bug Report | Low | Tab styles: some suggestions | Unconfirmed | Chris Haslam | 21.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.
|
|
290 | Koda | Application | Bug Report | Low | Tab Sequence (Order) Editor: a proposal | Unconfirmed | Chris Haslam | 23.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.
|
|
293 | Koda | Application | Bug Report | Low | Form style DS_FOREGROUND: Autoit only supports partiall... | Unconfirmed | Chris Haslam | 26.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”.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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>
|
|
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.
|
|
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.
|
|
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
|
|
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.
|
|
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
|
|
81 | Koda | Application | Feature Request | Low | Ability to separate form generating code and event code | Unconfirmed | | 04.11.2009 |
Task Description
Hello,
I would like to separate the code for generating the form, and my own event code.
One way to do this would be to let Koda generate an au3 file for generating the form, but no event handlers. I would just #include this file in my own au3 file. I am responsible myself for generating the right functions for the event handlers, or I could implement an event loop.
More complex options could be conceived, like in the following post :
http://www.autoitscript.com/forum/index.php?showtopic=17612
I would be interested in contributing to Koda, and maybe implement this feature myself. I have 10 years of professional programming experience in Borland C++ Builder and Delphi.
Best
|
|
102 | Koda | Application | Bug Report | Low | In String list editor all words are not translatable. | Unconfirmed | Thierry | 05.02.2010 |
Task Description
In the string list editor, we can’t translate all the terms attached image.
|
|
114 | Koda | Application | Bug Report | Low | Ctlr+с copy elements but not the value | Assigned | | 06.03.2010 |
Task Description
keyboard shortcut Ctrl+С copies of the element, although I need to copy the instance name of the element.
|
|
139 | Koda | Application | Feature Request | Very Low | add a option 'set caption also set name' | Postponed | thesnow | 25.08.2010 |
Task Description
add a option ‘set caption also set name’,set name do nothing with caption.
or add a right menu ‘set caption as form name’ to property list.
thanks!
|
|
140 | Koda | Application | Feature Request | Very Low | Unicode support | Unconfirmed | Thong | 30.10.2010 |
Task Description
I am vietnamese,i use the unicode,but koda don’t support it,we need it,thanks
|
|
159 | Koda | Documentation | Regular Task | Low | Help | Property Editors | Waiting feedback | Chris Haslam | 18.01.2011 |
Task Description
It would be helpful if the Help mentioned how to access the property editors. A few are obvious, but one that is not is the TreeView Editor. There may be more that have this problem.
|
|
171 | Koda | Application | Feature Request | Low | Distinctive colors for grab handles of "No insert in" a... | Researching | Chris Haslam | 07.05.2011 |
Task Description
Perhaps also a “Insert in” and “Allow copy” menu items, so user doesn’t have to close the form and reopen it to regain full editing capability over controls.
...chris
|
|
217 | Koda | Application | Feature Request | Low | Strings Editot | Show Hard Return? | Unconfirmed | Chris Haslam | 26.04.2011 |
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.
|
|
225 | Koda | Application | Feature Request | Low | Menu Designer: OK and Cancel buttons | Researching | Chris Haslam | 05.05.2011 |
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.
|
|
231 | Koda | Application | Bug Report | Low | Combo: Remarks | Unconfirmed | Chris Haslam | 04.05.2011 |
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.
|