Koda ver 1.5 uploaded

[AutoChris]

I am running Koda 1.5.1.3. In the Win32 tab, the buttons are not linked properly with the functions. The first button is inactive, and the second button is linked the the function of the first button. The third is linked to the second, etc.

1. Pressing the slider button does nothing.

2. Pressing the progress button creates a slider.

3. Pressing the date picker creates a progress bar.

etc.

Great program, by the way.

edit: typo

Edited April 14, 2006 by SerialKiller

[Lazycat]

When starting ->Error Invalid arguments ?? -> craches

Strange. Do you tried to kill fd.xml? I can imagine only problems related with it...

It must be exact same also with case sensitivity!

And extension of file must be kxf (and not KXF or kxF, ...)

Don't know exactly, but this is should not be that way!

I am running Koda 1.5.1.3. In the Win32 tab, the buttons are not linked properly with the functions.

Crap... :"> I'm sorry, this was fixed already by lookfar, but I'm accidentally missed this fix... Will be fixed in next beta.

BTW, I'm still interesing in some opinions about event naming...

[Zedna]

Don't know exactly, but this is should not be that way!

Try to rename Form1.kxf to Form1.kxF and then run it via doubleclick,you hit this error:

Form1.kxF is not a valid component name.

It's the same on WIN98 and WINXP.

I'm using version 1.5.1 of Koda

Edited April 14, 2006 by Zedna

[Lazycat]

Try to rename Form1.kxf to Form1.kxF and then run it via doubleclick,you hit this error:

Found bug, this because extension trim function was case-sensitive...

Though can't confirm that it also applies to filename.

[Lazycat]

New beta is out http://www.autoitscript.com/fileman/users/lookfar/koda_2006.04.17.zip. In this beta is mainly interface (aka usability ) fixes and changes, related to form handling, opening, saving, closing etc. Full changelog look http://www.autoitscript.com/fileman/users/lookfar/history.txt.

[Zedna]

New beta is out http://www.autoitscript.com/fileman/users/lookfar/koda_2006.04.17.zip. In this beta is mainly interface (aka usability ) fixes and changes, related to form handling, opening, saving, closing etc. Full changelog look http://www.autoitscript.com/fileman/users/lookfar/history.txt.

I'm using version 1.5.1 (and not beta versions) because I'm working on several (GUI) projects which I don't want broke, but I test every beta you give up

Problems in this version:

- in GUIOnEvent mode there is missing in generated code:

Opt("GUIOnEventMode", 1)

GUISetOnEvent($GUI_EVENT_CLOSE, "OnClose")
Func OnClose()
  Exit
EndFunc

--> when you create new GUI with OnEvent mode and run generated code "as is" it can't be closed!

--> this code should be in GUIOnEvent header/footer as I say below in Ideas

Ideas:

- GUIOnEventMode should be dependent on each KXF form (inside it) and not as global for all forms

as global option it must be only for newly created forms

- header and footer should be twice (in Options as two TabItems) for GUIMessage mode and GUIOnEvent mode

- Event Editor can only set None/Notify, so I can't define event code directly inside Koda

- doubleclick on buttons (and maybe other controls) should open Event editor

Keep on this good work ...

[Zedna]

Another little cosmetic idea:

Maybe you should change your Koda version strategy

In these last betas there are lot of new big functionality,

so version like 1.5.2 or 1.6.0 or 2.0 would be better (than 1.5.1.3)

Edited April 17, 2006 by Zedna

[Lazycat]

I'm using version 1.5.1 (and not beta versions) because I'm working on several (GUI) projects which I don't want broke, but I test every beta you give up

Cleverly. Moreover, now was a big changes done, so it probably buggy.

- in GUIOnEvent mode there is missing in generated code:

Opt("GUIOnEventMode", 1)

GUISetOnEvent($GUI_EVENT_CLOSE, "OnClose")
Func OnClose()
  Exit
EndFunc

--> when you create new GUI with OnEvent mode and run generated code "as is" it can't be closed!

--> this code should be in GUIOnEvent header/footer as I say below in Ideas

Yes, indeed, this is by design atm How you think, this function should be hardcoded or better to add onClose event for form?

But "GUIOnEventMode" I definitely forgot... This is will be generated automatically.

- GUIOnEventMode should be dependent on each KXF form (inside it) and not as global for all forms

as global option it must be only for newly created forms

This was planned as just codegen option. So you can in anytime generate one or other style code. But this can be memorized, need to think.

- header and footer should be twice (in Options as two TabItems) for GUIMessage mode and GUIOnEvent mode

Now most code will be generated dynamically. I don't know, footer and header is even need now?

- Event Editor can only set None/Notify, so I can't define event code directly inside Koda

Sorry, forgot to say about it: go to options -> designer -> Other options -> Advanced Event Editor

- doubleclick on buttons (and maybe other controls) should open Event editor

Hm... why event editor, and not, say, items editor?

[Zedna]

Yes, indeed, this is by design atm How you think, this function should be hardcoded or better to add onClose event for form?

Always I'm not sure about variant one or two I make an Option to leave decision on user

Here I think onClose event looks pretty, it can be done this way also for GUIMessage (Case $GUI_EVENT_CLOSE).

This was planned as just codegen option. So you can in anytime generate one or other style code. But this can be memorized, need to think.

If it will be a codegen option, there should be predefined value from KXF (where it will be stored)

Now most code will be generated dynamically. I don't know, footer and header is even need now?

I don't know about this dynamic code, so header/footer is by me still important.

Users like me who don't use dynamic features need header/footer

Sorry, forgot to say about it: go to options -> designer -> Other options -> Advanced Event Editor

It still don't let me edit code for event mapped to this control (maybe there should be used Scite editor for this editing invoked directly from Koda by doubleclick)

Hm... why event editor, and not, say, items editor?

In all other Development applications like Delphi/VCC/VB/PowerBuilder/...

on doubleclick there is opened event editor for this control.

Properties like item editor are accessible from object inspector which is easily visible.

Edited April 17, 2006 by Zedna

[Lazycat]

Always I'm not sure about variant one or two I make an Option to leave decision on user

Here I think onClose event looks pretty, it can be done this way also for GUIMessage (Case $GUI_EVENT_CLOSE).

Yes, this is exactly as planned. Form will have all available events (onClose, onMinimize etc). No problem also make onClose enabled by default.

I don't know about this dynamic code, so header/footer is by me still important.

Users like me who don't use dynamic features need header/footer

Well, this need to be consider.

It still don't let me edit code for event mapped to this control (maybe there should be used Scite editor for this editing invoked directly from Koda by doubleclick)

Hm... You mean integrated code editor for events? Don't know, don't know... This is should not be hard to add, but you think this will be useful? No way to use Scite or something like as editor atm, and I'm pretty doubt that you can use it in future, if some interactive editing will be available.

on doubleclick there is opened event editor for this control.

Default event. Well, this is also need consideration.

In these last betas there are lot of new big functionality,

so version like 1.5.2 or 1.6.0 or 2.0 would be better (than 1.5.1.3)

We decide it when lookfar will be accessibe (he is busy now).

[Lazycat]

New beta uploaded http://www.autoitscript.com/fileman/users/lookfar/koda_2006.04.27.zip. The main new thing here - menu designer (finally!). Implemented 3 controls: Main Menu, Context Menu and Tray Menu.

Some notes for those, who never worked with IDE like Delphi. When you place menu control onto designer form, creating actual menu and "virtual" control, that serve as interface between you and menu. This looks like small "button" that have some properties in the inspector - usually Items for access to menu items and some other. You see this button only on design form, it's not generate any code.

Any menu should be "attached" to some contol or form. Look for properties "Menu", "ContextMenu" and "TrayMenu" in the inspector. It's dropdown list contain all controls of appropriate type that was placed on form, so you can select one. Each menu can be attached only to one control! If you select menu that already attached, it's will be reattached to new control.

Not attached menus not generate any code. This mean, for example, that you can have more then one main menu on form, and switch between them. Look MenuDemo.kxf in forms subfolder for examples.

Another big thing (though mainly internal) with this beta - new xml save/load routines, now based on the general xml parcer. This should be more reliable and give less errors. But because this critical update, it's need to be tested - especially for compatibility with old forms and saving/loading non-latin strings. So if someone have many complex forms and can test it - this will be appreciated. Test version with new routines enabled can be downloaded http://www.autoitscript.com/fileman/users/lookfar/koda_test.zip.

[Gene]

New beta uploaded http://www.autoitscript.com/fileman/users/lookfar/koda_2006.04.27.zip. The main new thing here - menu designer (finally!). Implemented 3 controls: Main Menu, Context Menu and Tray Menu.

Some notes for those, who never worked with IDE like Delphi. When you place menu control onto designer form, creating actual menu and "virtual" control, that serve as interface between you and menu. This looks like small "button" that have some properties in the inspector - usually Items for access to menu items and some other. You see this button only on design form, it's not generate any code.

Any menu should be "attached" to some contol or form. Look for properties "Menu", "ContextMenu" and "TrayMenu" in the inspector. It's dropdown list contain all controls of appropriate type that was placed on form, so you can select one. Each menu can be attached only to one control! If you select menu that already attached, it's will be reattached to new control.

Not attached menus not generate any code. This mean, for example, that you can have more then one main menu on form, and switch between them. Look MenuDemo.kxf in forms subfolder for examples.

Another big thing (though mainly internal) with this beta - new xml save/load routines, now based on the general xml parcer. This should be more reliable and give less errors. But because this critical update, it's need to be tested - especially for compatibility with old forms and saving/loading non-latin strings. So if someone have many complex forms and can test it - this will be appreciated. Test version with new routines enabled can be downloaded http://www.autoitscript.com/fileman/users/lookfar/koda_test.zip.

GREAT!!!

I installed it, opened it, left clicked on the plus symbol next to the menu item in the Object Inspector and got the following error.

I'm running Win2K sp4 MSIE 6.x sp1 256MbRAM

Gene

EDIT: I got the same or similar error again. This time I clicked on the main Menu icon in the tool bar. Dropped a small menu Icon and dashed square on the form. I moved it to the upper left. Next dbl-clicked it, the menu designer opened, I right clicked it and choose insert on the Popup menu. At that point the erreor message poped up.

See msg here =>

Edited April 27, 2006 by Gene

[Zedna]

For now:

Bugs:

1) When I place two tray menus at form (it's incorrect, I know) and doubleclick at first and in menu editor hit Ins - Acces violation.

2) When I place two main menus at form (it's incorrect, I know) then after adding items to both of them there are strange thing in Koda: disabled all Koda menus (one menu designer was at backgound, under form) and in generated code is only last main menu

3) in mainmenu/popupmenu - after doubleclick in menu editor is not working Ins key - it's because focu isn't on empty menu item, I must first click on it to be working Ins key and Insert item popup menu there

4) After F10 is SCITE hidden behind OnTop Koda window

5) in Options/CodeGen/Header is #include <GUIConstants.au3 there is missing >

Ideas:

6) TabOrder Editor (like in Delphi) - dialog with listview with control names and their taborders and possibilty to move them up/down

7) in Koda main menu item Options move to menu Tools so there will be:

Generate Code F9
 Run Form F10
 ---
 Options

Stay tuned I will test more but later

[Lazycat]

Wow, I'm just impressed: last two days I'm not got AV's, and here few at once

I installed it, opened it, left clicked on the plus symbol next to the menu item in the Object Inspector and got the following error.

EDIT: I got the same or similar error again. This time I clicked on the main Menu icon in the tool bar. Dropped a small menu Icon and dashed square on the form. I moved it to the upper left. Next dbl-clicked it, the menu designer opened, I right clicked it and choose insert on the Popup menu. At that point the erreor message poped up.

Hm, can't represent it, nor in XP nor in W2kSP4. Can you explain what the "dashed square" is?

And for first image: I'm curious, how you got situaltion, when field don't have an object, but have plus sign? Of course, you can remove object ident, but until you press enter, it still assigned, after pressing enter plus sign is gone...

1) When I place two tray menus at form (it's incorrect, I know) and doubleclick at first and in menu editor hit Ins - Acces violation.

This is correct (two menus, not AV of course). I tried to represent this error and can not do it exactly: do you sure that it "Access violation"? Maybe "Invalid typecast"? I'm got only this error sometimes.

2) When I place two main menus at form (it's incorrect, I know) then after adding items to both of them there are strange thing in Koda: disabled all Koda menus (one menu designer was at backgound, under form) and in generated code is only last main menu

This is semi-correct behaviour: what is right, instead other editors menu designer can't be modal (or you can't use property inspector), but using other functions while menu editing can cause hardly predictable results, so atm whole koda is dim while menu editing. What is wrong, that you can open second menu editor, or at least fact that it hide behind the form.

3) in mainmenu/popupmenu - after doubleclick in menu editor is not working Ins key - it's because focu isn't on empty menu item, I must first click on it to be working Ins key and Insert item popup menu there

Yes, that is... Probably part of other error also caused by that fact. Need to fix.

4) After F10 is SCITE hidden behind OnTop Koda window

Yes, not only Scite and this is not good behaviour, but I'm not familiar with this part of code, so atm I'm add this to buglist.

5) in Options/CodeGen/Header is #include <GUIConstants.au3 there is missing >

Still missing... Fixed (this saved in config, so it's matter when recreating config only).

Ideas:

6) TabOrder Editor (like in Delphi) - dialog with listview with control names and their taborders and possibilty to move them up/down

Yeah, I'm just started to work on it yesterday.

7) in Koda main menu item Options move to menu Tools so there will be:

We will think. This can be moved, if no other options will be under Options menu. Edited April 28, 2006 by Lazycat

[Zedna]

1) When I place two tray menus at form (it's incorrect, I know) and doubleclick at first and in menu editor hit Ins - Acces violation.

This is correct (two menus, not AV of course). I tried to represent this error and can not do it exactly: do you sure that it "Access violation"? Maybe "Invalid typecast"? I'm got only this error sometimes.

I tested it on WIN98 SE and it was really AV.

But now I tested same sequence also on WINXP and it's OK.

So bug only on WIN98 SE...

[Gene]

Wow, I'm just impressed: last two days I'm not got AV's, and here few at once

Hm, can't represent it, nor in XP nor in W2kSP4. Can you explain what the "dashed square" is?

And for first image: I'm curious, how you got situaltion, when field don't have an object, but have plus sign?

I opened Koda, noticed the plus sign next to Menu and clicked on it to see what it would expand to...

Of course, you can remove object ident, but until you press enter, it still assigned, after pressing enter plus sign is gone...

Look at the upper left corner of the form in this graphic.

The dashed line is the object outline with window sizing handles, but when I was writing it it came out as dashed line. Sorry.

Gene

Edited April 28, 2006 by Gene

[Lazycat]

New beta uploded http://www.autoitscript.com/fileman/users/lookfar/koda_2006.04.29.zip. Don't sure if changes in menu builder solved problems, but have a try... Also visual TabEditor was added.

Probably, I'll pause adding new features now and start fix existing

I tested it on WIN98 SE and it was really AV.

But now I tested same sequence also on WINXP and it's OK.

So bug only on WIN98 SE...

Sadly, I can't test it under W9x now... Try new beta, maybe changes fix it.

I opened Koda, noticed the plus sign next to Menu and clicked on it to see what it would expand to...

Just opened and it's was there? No thoughts yet... Can't represent this behaviour...

[Zedna]

New beta uploded http://www.autoitscript.com/fileman/users/lookfar/koda_2006.04.29.zip. Don't sure if changes in menu builder solved problems, but have a try... Also visual TabEditor was added.

Probably, I'll pause adding new features now and start fix existing

Sadly, I can't test it under W9x now... Try new beta, maybe changes fix it.

Just opened and it's was there? No thoughts yet... Can't represent this behaviour...

Step order leading to bug (AV - acces violation) on WIN98 (version from 27.4.):

- place two main menus on new form

- on first main menu icon doubleclick to open menu designer

- in menu designer click to empty menu

- press Ins key insert one menu item

- close menu designer

- on second main menu icon doubleclick to open menu designer

- (in menu designer DON'T click to empty menu)

- press Ins key insert one menu item

--> now appears on WIN98 acces violation error, on WINXP Invalid class typecast error

In new version from 29.4. this kind of error don't occurs on WIN98, so this problem has been solved.

New visual TabOrder editor is really GREAT and can be added to menu "View/TabOrder editor" with some hotkey.

And small question from me: Is planned new version of Koda to be bundled with new release version of AutoIt which is planned to release in May?

[Lazycat]

Step order leading to bug (AV - acces violation) on WIN98 (version from 27.4.):

--> now appears on WIN98 acces violation error, on WINXP Invalid class typecast error

In new version from 29.4. this kind of error don't occurs on WIN98, so this problem has been solved.

Glad to hear that. So this was the same bug, just appears differently on different OS.

New visual TabOrder editor is really GREAT and can be added to menu "View/TabOrder editor" with some hotkey.

Ok, but I think Edit menu will be more suitable place, because you edit TabOrder... View menu operates with windows that can be constantly visible or not.

And small question from me: Is planned new version of Koda to be bundled with new release version of AutoIt which is planned to release in May?

Hm, this question is beyond my area. Though, this is already in the Scite installation, do you think it need to be included in the release? Among other things it will greatly increase distributive size (Koda itself, languages, templates etc etc - it's about 600 kb zipped size).

[Zedna]

Ok, but I think Edit menu will be more suitable place, because you edit TabOrder... View menu operates with windows that can be constantly visible or not.

I think in Object inspector you are also editing and it's in View and not Edit.

I understand your idea of View only for long time like Object inspector.

Please look into Delphi (I haven't it instaled now) where in menu is TabOrder editor. I think in Koda it should be in the same place as in Delphi when Koda is "clone" of Delphi

Hm, this question is beyond my area. Though, this is already in the Scite installation, do you think it need to be included in the release? Among other things it will greatly increase distributive size (Koda itself, languages, templates etc etc - it's about 600 kb zipped size).

From me it was only QUESTION. I think you developers of Koda could ask developers of AutoIt if such bundling of Koda and AutoIt (with Scite) instalers is planned for next release or not...