All Projects

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.

I do not see the reason for the existence of this menu item.

I can almost as easily key Ctrl-3 and choose which form to activate with the mouse.

Also, consider a form that occupies the whole of the screen. In this case, there is no way IMHO to activate the main menu in order for Alt-m to work. (See the Help as it now is.)

If you wish to keep the Forms menu item, perhaps there should be a function key that focuses Koda so the main menu is active, so Alt-m works.

Or am I missing something?

...chris

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.

If there are two Koda regions in a .au3 file, say foo.kxf and bar.kxf, will Update Script work both when foo.kxf is the active form and when bar.kxf is the active form?

It seems to me that this is possible, but the current documentation does not say so.

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.

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.

menu_align.png had Horizontal rather than Horizontally. etc.

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

New version is attached.

Save chosen template as one of form options.

Not rename form when loading (Form1?Form1_1)

Customizing fonts (by EulerG)

Remove ClientWidth/ClientHeight for the Form (Make Width=ClientWidth etc)

$Form1 = GUICreate(”Title”, 300, 200, -1,
= GUICtrlCreateListView(”A|B|C”, 15, 15, 270,
$LVM_SETCOLUMNWIDTH, 0,
$LVM_SETCOLUMNWIDTH, 1,
$LVM_SETCOLUMNWIDTH, 2,

Column widths are not imported from AU3 to KXF.

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.

RichEdit custom control since it’s UDF was added in the standard distributive.

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

Please add the ability to use array names in the Object Inspector for the control names: ControlName[Index]

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!

I am vietnamese,i use the unicode,but koda don’t support it,we need it,thanks

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:

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

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

Auto-sizing in Radio and Checkbox controls would be useful. Default should be False. Put it on the wish list?

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:

1. Setting the tab order for all controls, and
2. 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

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

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?

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.

In 1.7.3.0, it appears that when I run Koda, the form that automatically opens is the last one changed (I am not sure of this).

I would like to see Koda start by opening the form that was active when Koda was last exited. This makes more sense to me.

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:

1. Put them in the Styles tab, at the top of the list, or

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

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.

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.

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?

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.

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

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.

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.

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

It would make sense to me to have one Ctrl_Z undo all changes to a string, rather than character-by-character.

In object inspector is property Resizing generated code GUICtrlSetResizing()

But there are missing constants (defined in AutoIt’s helpfile): $GUI_DOCKSIZE, $GUI_DOCKMENUBAR, $GUI_DOCKSTATEBAR, $GUI_DOCKALL, $GUI_DOCKBORDERS

All these contants are defined by sum of base constants already defined in
I think it may be intentional to not add these contants.

But it would be pretty handy to have them all in Koda.

Generation options dialog is loose indent char selection, when opening options dialog by clicking “Manage” button, and then clicking “Ok” in options dialog.

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

In the string list editor, we can’t translate all the terms
attached image.

keyboard shortcut Ctrl+С copies of the element, although I need to copy the instance name of the element.

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.

In version 1.7.2.8 when I try to add an embedded IE control (Shell.Explorer.2) to a form Koda shows
‘Call to DllRegisterServer failed in

As consequence no AU3 code is generated for the control - although it shows on the form - and all attempts to open the definition file afterward fail with the same error message, so the only remaining option is to open KXF file as XML and remove the control manually.

Especially confusing is the fact that Koda wants to call DllRegisterServer at all. Why is it necessary? The DLL is already registered on the system, otherwise the control wouldn’t appear in the Koda’s object browser.

Version 1.7.2.8

Customize
Add “NewPage” or “NewButton” to a Toolbar (e.g. Standard Toolbar or User Toolbar n” will not show the Icons

with showing User Toolbar3**

User Toolbar 1 is configure well User Toolbar 2 is not configure User Toolbar 3 is configure “Apply” Button Result: User Toolbar 1 is shown, User Toolbar 3 is not shown! a1. User Toolbar 1 is configure well User Toolbar 2 is not configure User Toolbar 3 is configure After “Apply” Button User Toolbar 2 is setting up “Apply” Button Result: All Toolbars will shown b. User Toolbar 1 is configure well User Toolbar 2 is configure well User Toolbar 3 is configure “Apply” Button Result: User Toolbar 3 will not be shown!

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.

• I ran Koda. It brought up a form I had created earlier. Expand %var% variable was unchecked

• I created a label

• I entered %name% is a cat in Label | Caption

• I checked Expand %var% variable

• I clicked on Generate Code. ⇒ $name+”is a cat”

• I unchecked Expand %var% variable

• I clicked on Generate Code. ⇒ $name+”is a cat” again

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?

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.

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.

• GUICtrlSetLimit() sets max and min but not increment. Perhaps a _GuiCtrlSetLimit(max, min, incr) could be written. Then Koda could set a (new) Increment property. It is needed if UDS_ARROWKEYS is to work. You may have some influence over Jon to add to GUICtrlSetLimit().

• If no style is specified, Updown is placed to the right of the Input, but $GUI_SS_DEFAULT_UPDOWN alone puts the UpDown to the left of the Input. This is because UpDownConstants.au3 has

  Global Const $GUI_SS_DEFAULT_UPDOWN = $UDS_ALIGNLEFT

  To me, $GUI_SS_DEFAULT_* are equivalent to -1. AutoIt Help says that -1 means $UDS_ALIGNRIGHT. Right is where you expect to see an UpDown. So Koda should use $UDS_ALIGNRIGHT until AutoIt fixes $GUI_SS_DEFAULT_UPDOWN.

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

I suggest File | Close.

Documentation says Close, not Close Form.

...chris