Koda ver 1.5 uploaded

[Zedna]

Behaviour of Combo with Text property imho is too messing. And this is do nothing different then just add one more item in list - exactly what Items did. This is reason why this property was not processed before.

I'm think better get rid Text property at all. When you need to have some text in combo by default, you can just add this as line in the Items property and set item index.

I don't agree. I discovered elegant way with "Default" parameter in GUICtrlSetData()

Property Text is like Default value in this case.

GUICtrlCreateCombo("", 128, 64, 129, 21)
GUICtrlSetData(-1, "Items", "Text")oÝ÷ Ù±!?Û«z«¨´^Ê®¢

Edited August 22, 2006 by Zedna

[Lazycat]

The problem here, that Text property can't be default. For example, look for situation: you have few items in list, set some ItemIndex, and then change Text property. What now Koda should treat as default? If Text - what in this case ItemIndex mean?

[Groumphy]

Hello,

Here is the last traduction (v1.4 production).

The beta follow

G.

<edit> 23.09.2006 13:54 : v1.4 updated (production version, error in the scheme numbering) ; beta translation follow !

Edited August 23, 2006 by Groumphy

[Lazycat]

<edit> : v1.5 updated (production version) ; beta translation follow !

Thanks, waiting.

@Zedna

Well, the only way I see:

1. When ItemIndex = 0, you can change Text, this will be added as first item to list and set to default.

2. When ItemIndex > 0, you can't change Text, this will represent current list item text.

Edited August 22, 2006 by Lazycat

[Zedna]

Thanks, waiting.

@Zedna

Well, the only way I see:

1. When ItemIndex = 0, you can change Text, this will be added as first item to list and set to default.

2. When ItemIndex > 0, you can't change Text, this will represent current list item text.

In Autoit is not adequate to ItemIndex, so it is only in Koda to help setup property Text.

So my idea is to completely remove property ItemIndex (or Text?) in Koda.

But I don't know about relations in sources of Koda and used components,

so take it only as my idea from outside

Edited August 22, 2006 by Zedna

[Lazycat]

In Autoit is not adequate to ItemIndex, so it is only in Koda to help setup property Text.

Not exactly: ItemIndex help to set default item, but Text <> default item.

So my idea is to completely remove property ItemIndex (or Text?) in Koda.

But I don't know about relations in sources of Koda and used components,

so take it only as my idea from outside

Btw, in Delphi's combo Text property is independent from Items (result: text of control is Text property, items in dropdown list - Items), but in Autoit realization, text visible in control can be only one from list items. So when setting text in GUICtrlCreateCombo ( "text"...) - this text is always added in list. I'm not sure if this correct behaviour or not (I feel this wrong), but in this case Text property have no sense.

[parrotta]

Lazycat, et. al:

First of all, awesome application. Your efforts have already saved me quite a bit of development time with a client/server app I'm writing.

Secondly, ever since I downloaded 1.5.16 from your website this morning, I am presented with the following MsgBox message everytime I attempt to save one of my forms:

"Could not convert variant of type (String) into type (Double)"

I quickly scanned this thread and didn't see any mention of this. Any ideas?

Thanks,

Adam Parrott

[Zedna]

Secondly, ever since I downloaded 1.5.16 from your website this morning, I am presented with the following MsgBox message everytime I attempt to save one of my forms:

"Could not convert variant of type (String) into type (Double)"

Post here KXF file or say what controld you have on the form - for reproduce error.

And what OS do you have?

EDIT: And what nonstandard properties do you set up as values in controls?

Edited August 22, 2006 by Zedna

[parrotta]

Post here KXF file or say what controld you have on the form - for reproduce error.

That's the problem - it stops just short of actuaully saving the .kxf file once it gives me the message.

And what OS do you have?

Currently, I have only tried 1.5.16 on my development machine here, which is running XP Pro 2002 with SP1.

EDIT: And what nonstandard properties do you set up as values in controls?

Believe it or not, it will give me the same error no matter what I have on the form. IOW, if I restart Koda 1.5.16 by itself and attempt to save a blank form, it will give me the same error. Edited August 22, 2006 by parrotta

[Holger]

Here is the german translation so far (for version 1.5.1.16).

Maybe another one (german user) can take a second look over it.

So long...

Holger

lang_ger.xml

[Zedna]

Currently, I have only tried 1.5.16 on my development machine here, which is running XP Pro 2002 with SP1.

Believe it or not, it will give me the same error no matter what I have on the form. IOW, if I restart Koda 1.5.16 by itself and attempt to save a blank form, it will give me the same error.

Really I can confirm that problem also on my WIN98SE.

Open Koda (Beta 1.5.1.16) and Save empty form (the same also with simple one label) and the same error:

Could not convert variant of type (String) into type (Double)

It's strange because I worked with this version on some forms already without problems.

EDIT:

Now I know reason:

When is automatically created fd.xml there are boolean values:

<createbackup>False</createbackup>
        <keeplayout>True</keeplayout>

instead of correct ones:

<createbackup>0</createbackup>
        <keeplayout>1</keeplayout>

Edited August 22, 2006 by Zedna

[Lazycat]

Here is the german translation so far (for version 1.5.1.16).

Thanks, Holger!

Now I know reason:

When is automatically created fd.xml there are boolean values:

I'm suppose something like that, because form saving not do any string->double conversions... Thank you for findings!

[Groumphy]

Hello,

In the original template, there is some sentences in russian :

<form name="frmTabOrder">
        <caption>Ïîðÿäîê êîíòðîëîâ</caption>
        <btnOK property="Caption">OK</btnOK>
        <btnCancel property="Caption">Îòìåíà</btnCancel>
    </form>

With an automatic online translator, I've this result : "tabulation ordrer" and "Cancel".

Find the version beta translate in french (this is an test [alpha] traduction, for the moment. I'm waiting the comment and false traduction) in this topics :-)

A+

G.

<edit>23.09.2006 13:31 > updated translation

lang_frbe.xml

Edited August 23, 2006 by Groumphy

[Zedna]

In the original template, there is some sentences in russian :

<form name="frmTabOrder">
        <caption>Ïîðÿäîê êîíòðîëîâ</caption>
        <btnOK property="Caption">OK</btnOK>
        <btnCancel property="Caption">Îòìåíà</btnCancel>
    </form>

With an automatic online translator, I've this result : "tabulation ordrer" and "Cancel".

I reported here this bug yet.

Texts should be:

Tab Order Editor
Cancel

[Groumphy]

Nice :-)

I update the translation (I've write "Ordre des tabulation" and this is an editor...).

G.

[Lazycat]

<edit>23.09.2006 13:31 > updated translation

I can't check it, but it looks complete enough.

@Zedna

I'm leave combo in current state now. Maybe after release will make custom property editor for it to avoid all messes.

Here new version, only latest fixes and added ready translations.

http://www.autoitscript.com/fileman/users/lookfar/koda_2006.08.23.zip

[Zedna]

I have ideas for improvement:

1) Add keyboard shortcuts for some operations:

- Open (Ctrl+N or some Fx)

- Save (Ctrl+S or some Fx?)

- Options

- Update script (Ctrl+F9 or ??)

- Help F1

- ...

Maybe some of them could be also with modificators (Alt, Ctrl)

and these new and also existing shortcuts should be also in menu items

(now is missing for example existing Ctrl+C, Ctrl+V, Ctrl+A, Del)

2) As I wrote earlier: Allignment pallete

here is screenshot such pallete from PowerBuilder

[Lazycat]

I have ideas for improvement:

1) Add keyboard shortcuts for some operations:

- Open (Ctrl+N or some Fx)

- Save (Ctrl+S or some Fx?)

- Options

- Update script (Ctrl+F9 or ??)

- Help F1

- ...

Maybe some of them could be also with modificators (Alt, Ctrl)

and these new and also existing shortcuts should be also in menu items

(now is missing for example existing Ctrl+C, Ctrl+V, Ctrl+A, Del)

Well, it's possible to add them with some workaround. In menu they are only informative - main form don't have focus when you work with design form, so you can't call those shortcuts actually.

2) As I wrote earlier: Allignment pallete

here is screenshot such pallete from PowerBuilder

Maybe. I'll look PowerBuilder and how it work. But all after release

[Zedna]

Here new version, only latest fixes and added ready translations.

Fixed: virtual name of control in the TabOrder editor instead emptyness (thanks Zedna)

It's better but I meant something even more better

In Tab Order ListBox show also text of controls (from their Text or Caption properties)

at least at such controls without defined names.

Something like:

now:

1: <Label[1]>: TALabel
2: <AInput[1]>: TAInput

new:

1: <Label[1]>: TALabel (Caption of label1)
2: <AInput[1]>: TAInput (Text of input 1)

[Zedna]

Well, it's possible to add them with some workaround. In menu they are only informative - main form don't have focus when you work with design form, so you can't call those shortcuts actually.

But there are some shortcuts now already: F8 F9 F10,

so make another ones in the same style.

Maybe. I'll look PowerBuilder and how it work. But all after release

PowerBuilder is corporate developers IDE for applications www.sybase.com

I didn't expect such quickly implementatuon

If I can help you with more detailed description of functionality that palette, just tell me.

Here is textual listing of allignment commands for palette in my previous screenshot:

Align left edges to first selected

Align right edges to first selected

Align center horizontal to first selected

Align center vertical to first selected

Align top edges to first selected

Align bottom edges to first selected

Space evenly horizontally

Space evenly vertically

Make all widths same as first selected

Make all heighths same as first selected

Make all widths and heighths same as first selected