|
89 | Koda | Application | Bug Report | Medium | Wrong form height in the generated code | Researching | | 29.05.2011 |
Task Description
If a dialog form is created with the certain style bits (s. below) in Koda the window height in the generated AutoIt code is set to ClientHeight + 1 instead of Height which cuts off a stripe of the height of the window’s title bar (mostly 26 px) at the bottom of the form at the time is displayed from the script.
Example as followed.
SampleDialog.kxf
<object type="TAForm" name="dlgTest">
<properties>
<property name="Left" vt="Int16">1626</property>
<property name="Top" vt="Int16">262</property>
<property name="Width" vt="Int16">321</property>
<property name="Height" vt="Int16">407</property>
<property name="Caption" vt="String">Sample Dialog</property>
<property name="Color" vt="Ident">clBtnFace</property>
<property name="Font.Charset" vt="Ident">DEFAULT_CHARSET</property>
<property name="Font.Color" vt="Ident">clWindowText</property>
<property name="Font.Height" vt="Int8">-11</property>
<property name="Font.Name" vt="String">MS Sans Serif</property>
<property name="Font.Style" vt="Set"/>
<property name="OldCreateOrder" vt="False">False</property>
<property name="Position" vt="Ident">poDesktopCenter</property>
<property name="ParentForm" vt="String">owner</property>
<property name="Style" vt="Int32">273154176</property>
<property name="ExStyle" vt="Int8">0</property>
<property name="Version" vt="String">1.04</property>
<property name="PixelsPerInch" vt="Int8">96</property>
<property name="TextHeight" vt="Int8">13</property>
</properties>
</object>
SampleDialog.au3 (generated)
#Region ### START Koda GUI section ### Form=SampleDialog.kxf
Local $dlgTest = GUICreate("Sample Dialog", 314, 374, -1, -1, BitOR($WS_SYSMENU,$WS_DLGFRAME,$DS_MODALFRAME), 0, $owner)
#EndRegion ### END Koda GUI section ###
As far as I evaluated this concerns only (modal) dialog frames with system menu but without minimize/maximize boxes, normal overlapped windows are not affected though their heights are also set to ClientHeight. It may be the strange way AutoIt’a GUICreate() works but I think Koda should reflect its behavior even if it’s inconsistent.
|
|
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
|
|
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.
|
|
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.
|
|
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.
|
|
147 | Koda | Application | Feature Request | Low | TAGroup: A suggestion | Waiting feedback | Chris Haslam | 17.01.2011 |
Task Description
Koda works well at grouping if the user creates a group and then adds radio buttons to it: he decides in advance what area of the form will be needed for the radios, and then adds the radios. For example, he creates Group1 and then creates Radio1 and Radio2 within it.
But two scenarios:
But what if he later realizes that he needs a third radio in this group? When he enlarges the Group area and adds Radio 3, Radio3 is not placed in Group1. It should be.
The user creates Checkbox1 and CheckBox2. He then surrounds them with Group2. The checkboxes are not made part of Group2. They should be.
I suggest that code be added to Koda: when a group is created, include in it all controls which are within the area of the group.
|
|
170 | Koda | Application | Feature Request | Low | Tab Order - 2 cases | Assigned | Chris Haslam | 23.05.2011 |
Task Description
As well as Edit→Tab Order, I now see Tab Order in Object Inspector (e.g. for Button). (perhaps Tab Stop Number would be more precise). So I think that there are two cases:
Setting the tab order for all controls, and
Setting the tab stop number for the currently selected control.
Tab Order Editor handles the first case.
Now for the second case.
In Object Inspector, Koda permits the user to enter the tab stop number. But what if he enters 2, and there is already a control that has tab stop 2. What happens?
I think it would be preferable to have clicking to the right of tab order bring up a dialog something like my screenshot:
This would allow the user to position the selected control relative to other controls. Note that he would no longer be concerned with the tab stop number, so conflicts in number could not occur.
IMHO
...chris
|
|
187 | Koda | Application | Feature Request | Low | OnClick => Notify ? | Assigned | Chris Haslam | 05.05.2011 |
Task Description
I don’t see why OnClick brings up a dialog.
It only has two values: Notify and don’t notify.
It seems to me that it would be more obvious if it were called Notify and its values were True and False. It would then work like, for example, Enabled.
Just a thought.
|
|
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.
|
|
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?
|
|
184 | Koda | Application | Feature Request | Low | Template Gallery | Assigned | Chris Haslam | 05.05.2011 |
Task Description
I note that the documentation calls this “Templates Gallery” but 1.7.3 .0 and the screen shot call it “Form Templates”. I suggest that “Form Templates” is the better name: it fits with “Code Generation Templates”. I will change the documentation to “Form Templates”.
I note that 1.7.3.0 shows two tabs: “Standard” and “My own templates”, but that the 1.7.3.0 help and the documentation shows only “Standard”. Further, one of the templates in the “My own templates” tab has no icon. I suggest that “My own templates” be dropped. THe documentation will tell the user how to add templates and tabs.
How can the user add a description and icon to a template he creates?
How can the user delete a template he creates?
How can the user delete a tab that he creates?
|
|
150 | Koda | Application | Bug Report | Low | Expand %var% variable | Postponed | Chris Haslam | 17.01.2011 |
Task Description
This seems illogical.
What is the scope of Expand %var% variable? Is it specific to the form/.kxf file, or is it application level? Is it working as intended?
|
|
182 | Koda | Application | Bug Report | Low | Tools | Generating Options | Template doesn't show Even... | Assigned | Chris Haslam | 24.02.2011 |
Task Description
But Events Example is in Code Templates dialog
|
|
201 | Koda | Documentation | Bug Report | Low | Options | Options | Windows: which windows? | Unconfirmed | Chris Haslam | 05.05.2011 |
Task Description
Are the Windows here all the windows in Koda, i.e. Object Treeview, Object Inspector, Form List, and forms?
I have not figured out what the following checkboxes really do:
I have looked at the doc as I received it. It doesn’t help.
BTW the screen shot here is obsolete: we need a new one. Please supply.
BTW “Always full expand” should be “Always fully expand”
|
|
202 | Koda | Application | Feature Request | Low | Overcoming MS's confusion in styles for forms | Assigned | Chris Haslam | 05.05.2011 |
Task Description
MS‘s mess (discussed previously) is driving me nuts!
So for Styles of TAForm I suggest that you add some pseudo-styles. Some I think of: Title bar, Close box, Minimize box, Normal frame, Dialog frame, perhaps Modal.
There are two ways you could add them:
Put them in the Styles tab, at the top of the list, or
Put a Clearer styles for Form checkbox in Options | Designer. When it is checked, have Koda replace all the WS styles which are equivalent to pseudo-styles.
You have more experience than I do with these bloody styles. Perhaps there is no way to get around MS‘s confusion!
There is another way: document the translation from pseudo-styles to WS_ constants in Controls | Form. For that I would need your help.
|
|
216 | Koda | Application | Bug Report | Low | Picture Editor: some observations | Unconfirmed | Chris Haslam | 04.05.2011 |
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
@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!
Perhaps a filename and ext should be generated by Koda as @ScriptDir\fnam.ext
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.
|
|
219 | Koda | Application | Feature Request | Low | Treeview Editor: Observations | Assigned | Chris Haslam | 27.04.2011 |
Task Description
I suggest that:
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?
|
|
222 | Koda | Documentation | Bug Report | Low | Form control | Unconfirmed | Chris Haslam | 04.05.2011 |
Task Description
Description is in the doc but not in Object Inspector. Do I remove Description from doc?
|
|
261 | Koda | Application | Feature Request | Low | Disable a tabstop | Unconfirmed | Chris Haslam | 24.05.2011 |
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.
|
|
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.
|
|
153 | Koda | Application | Bug Report | Low | TAInput with TAUpdown always sets initial value to UpDo... | Postponed | Chris Haslam | 17.01.2011 |
Task Description
I set the Min to 1 and the Max to 9 in Updown. I could not then change the Text in Input to 3. I should be able to do this.
|
|
194 | Koda | Application | Bug Report | Low | Options | Options | General | Recent files | Unconfirmed | Chris Haslam | 12.05.2011 |
Task Description
I suggest that the caption be changed to Recent files in File menu. This is consistent with Undo levels. I also think that it is clearer.
|
|
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.
|
|
235 | Koda | Application | Bug Report | Low | Slider | Position | Waiting feedback | Chris Haslam | 11.05.2011 |
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.
|
|
242 | Koda | Application | Feature Request | Low | IP address: Enabled | Assigned | Chris Haslam | 11.05.2011 |
Task Description
I am surprised that there is no Enabled property in Object Inspector
|
|
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”.
|
|
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.
|
|
168 | Koda | Application | Bug Report | Low | Edit | Align menu | Center ... in Window | Assigned | Chris Haslam | 11.02.2011 |
Task Description
I suggest that Center Horizontally in Window be changed to Center Horizontally in Parent or Center Horizontally in Container.
Why?
“Parent”: As I understand it, Koda now considers a control to be in a group if it is a son of a group in Object TreeView.
“Container”: This can mean both son in Object TreeView and what surrounds a control visually in the Form display. This term would allow for Koda automatically making a control a son of a group if it is visually within the group.
“Window”: to me, this is an imprecise term. It can mean any window.
IMHO
...chris
|
|
191 | Koda | Application | Regular Task | Low | Multiple selection of controls | Unconfirmed | Chris Haslam | 13.03.2011 |
Task Description
Where is this mentioned in the Help? I have not found it.
I find it a little surprising that the user shift-clicks to add a control to the selection.
In Explorer (and elsewhere), control-click adds a file to the selection; shift-click adds a range of files to the selection.
Just a thought.
|
|
212 | Koda | Application | Feature Request | Low | Control Palette: Reorganize? | Postponed | Chris Haslam | 05.05.2011 |
Task Description
I understand why there are four tabs, but I wonder if there is a better way of organizing them.
I find that I easily forget where to find a control: which tab is it on? and which icon is it? A few icons are clear as to what the control is, but some are not. I often have to wait for the telltale to show to be sure. This is not the fault of the picture on the icon: icons are only a limited number of pixels.
So Idea #1 is to add a main menu item called Controls, with all the controls as sub-items. In the future, it may be necessary to have 3 levels, with Native and UDFs as the second level.
Idea #2 is to group the controls alphabetically, e.g. A to E for the first tab, F to M for the second, etc.
|
|
215 | Koda | Application | Bug Report | Low | TrayMenu | MouseClick | Default | Assigned | Chris Haslam | 26.04.2011 |
Task Description
I have problems with Koda generating TraySetClick(”0”) as the default:
It is not clear to me what ShowStdMenu does when a Tray Menu control is on a form.
Any thoughts?
|
|
229 | Koda | Application | Bug Report | Low | Data separator char | Assigned | Chris Haslam | 05.05.2011 |
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?
|
|
234 | Koda | Application | Bug Report | Low | Dummy: notify | Assigned | Chris Haslam | 04.05.2011 |
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?
|
|
240 | Koda | Application | Bug Report | Low | Tab Control: Focus and reorganizing pages | Unconfirmed | Chris Haslam | 06.05.2011 |
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.
|
|
277 | Koda | Application | Bug Report | Low | Menutitem: Object Inspector shows styles and exstyles f... | Unconfirmed | Chris Haslam | 10.06.2011 |
Task Description
...chris
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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
|
|
164 | Koda | Application | Bug Report | Low | File | Close Form is inconsistent with File | Open and ... | Unconfirmed | Chris Haslam | 02.02.2011 |
Task Description
I suggest File | Close.
Documentation says Close, not Close Form.
...chris
|
|
165 | Koda | Documentation | Bug Report | Low | Edit | Paste doesn't paste to the current cursor positi... | Unconfirmed | Chris Haslam | 08.02.2011 |
Task Description
The Help says “Paste previously copied/cut objects from clipboard into current cursor position”.
Attached is what actually happened when I tried it.
All I can say is that Paste didn’t work as documented. I don’t know how it should work: I am thinking about it.
For the time being, I will document it the way it actually works.
VB5 pastes to the top left of the client area, independent of where the cursor is.
...chris
|