Jump to content

GUI Designer: Koda 1.7.3.0


Lazycat
 Share

Recommended Posts

for a updown control the property 'Max' will not be saved in the kxf-file

Please check this again :P

Checked. Do you sure it not save at all? It save for me, except value 100 (this wrongly inherited from default, should be 0).

Very nice job ! For french translation, what 're the new menu ? Is all translated ?

I think this is ok... But not shure...

It looks complete except "Options" menu item (but maybe this ok too).
Link to comment
Share on other sites

Funkeh ^^, Just wondering, is there/will there, be a way, to generate the form by inserting the au3 code? For example, load the form from the code, instead of the file the form saves as? Because, I always forget to save my forms. Gets annoying when I need to edit them, and have to make them all over again xP

# MY LOVE FOR YOU... IS LIKE A TRUCK- #
Link to comment
Share on other sites

Yes, I think I will ask about.

Funkeh ^^, Just wondering, is there/will there, be a way, to generate the form by inserting the au3 code? For example, load the form from the code, instead of the file the form saves as? Because, I always forget to save my forms. Gets annoying when I need to edit them, and have to make them all over again xP

This function is WIP, but slowly. Now it's realized as standalone app, and it is early alpha.

http://www.autoitscript.com/fileman/users/Lazycat/Au3toKoda.zip

Link to comment
Share on other sites

Checked. Do you sure it not save at all? It save for me, except value 100 (this wrongly inherited from default, should be 0).

Hallo Lazycat

yes, it's true, i have tested UpDown-Control with Min = 1 and Max = 100 (because i need this values)

With this values the property MAX is not saved (MIN is saved correctly)

If i set MAX to 0, so it is 0 (range 0 to 1 is to small for me)

Is there a simple way to set the needed range 1 to 100 ?

Is it possible to save the property MAX all the time (including 100) ?

Apart from that you have done a really good job !!

Thanks

Link to comment
Share on other sites

yes, it's true, i have tested UpDown-Control with Min = 1 and Max = 100 (because i need this values)

With this values the property MAX is not saved (MIN is saved correctly)

If i set MAX to 0, so it is 0 (range 0 to 1 is to small for me)

Is there a simple way to set the needed range 1 to 100 ?

Is it possible to save the property MAX all the time (including 100) ?

Apart from that you have done a really good job !!

Thanks

Fixed this: now default values are both 0 - in this case code not generated. If they are different, code will be generated.
Link to comment
Share on other sites

Yes, I think I will ask about.

This function is WIP, but slowly. Now it's realized as standalone app, and it is early alpha.

http://www.autoitscript.com/fileman/users/Lazycat/Au3toKoda.zip

Very nice, Thanks :P
# MY LOVE FOR YOU... IS LIKE A TRUCK- #
Link to comment
Share on other sites

This function is WIP, but slowly. Now it's realized as standalone app, and it is early alpha.

http://www.autoitscript.com/fileman/users/Lazycat/Au3toKoda.zip

Here is VERY trivial GUI script which couldn't be converted --> List index out of bounds (-1)

#include <GuiConstants.au3>
#include <GuiListView.au3>

$gui_main = GuiCreate("Test", 500, 330)
$listview = GuiCtrlCreateListView("Col1|Col2", 0, 0, 500, 285,$LVS_REPORT) 

$add = GUICtrlCreateButton ("Add",10,300,70,20)
$change = GUICtrlCreateButton ("Change",100,300,70,20)
$delete = GUICtrlCreateButton ("Delete",190,300,70,20)

GuiSetState(@SW_SHOW, $gui_main)

While 1
    $msg = GuiGetMsg()
    Select
        Case $msg = $GUI_EVENT_CLOSE
            ExitLoop
    EndSelect
WEnd

Exit
oÝ÷ Ù8^±©­ë.جj[(Â+a¶¬P´Ñ4HTjëh×6GuiCreate("Test", 500, 330)
GuiSetState(@SW_SHOW)

While 1
sleep(100)
WEnd

Here are other my discovered bugs

but this one is really most significant.

Edited by Zedna
Link to comment
Share on other sites

Checked. Do you sure it not save at all? It save for me, except value 100 (this wrongly inherited from default, should be 0).

It looks complete except "Options" menu item (but maybe this ok too).

No it's OK too.

Can you upgrade the level translation to v1.0.0.beta with your next 'small' release ?

Thanks,

G.

----------------------GroumphyMore information about me [Fr]

Link to comment
Share on other sites

Can you upgrade the level translation to v1.0.0.beta with your next 'small' release ?

I'm make this just 1.6.0.0 - don't think translations need additional numbering. Once you done it, version will just follow Koda version number.

Also, bugfix version is out - mainly because nasty bug with saving. If this version ok, this will be postrelease.

http://www.autoitscript.com/fileman/users/lookfar/Koda_20060911.zip

Link to comment
Share on other sites

Also, bugfix version is out - mainly because nasty bug with saving. If this version ok, this will be postrelease.

http://www.autoitscript.com/fileman/users/lookfar/Koda_20060911.zip

Looks good to me.

I know that all bugs are not fixed but this one I discovered earlier and is leading to AV is not corrected

and can can be simply simulated (so not such xomplicated):

my post about it - number 6)

Link to comment
Share on other sites

Really sorry LazyCat :) but I found another AV.

When you close designed form while you have open Column editor (for listview)

then after some clicking on it AV occurs.

So maybe this dialog should be modal as all other similar dialogs are ...

EDIT: It can't be modal due to using another dialog: Object Inspector

Edited by Zedna
Link to comment
Share on other sites

just wanted to say i love Koda and use it all the time

and also love Au3toKoda, i've already used it 3 times today to make changes to a gui i thought was finished so i never saved it :)

I love Au3ToKoda too :P

@Lazycat: about Au3ToKoda

I think this importing program needn't handle all complicated situations,

it will be enaugh if it loads successfully 1 GUI from clean GUI script.

This Au3 script can be cleaned by hand before importing

because it's not so complicated for human brain (of skilled AutoIt scripters :D )

to cut off all non GUI stuff and leave only main GUI code for import (from Au3 to Koda Kxf).

It's good also for modify some old projects created without Koda and not only for not saved ones :D

Link to comment
Share on other sites

I know that all bugs are not fixed but this one I discovered earlier and is leading to AV is not corrected

and can can be simply simulated (so not such xomplicated):

Yeah, I tried to fix it before, but can't represent - because I tried delete it only via menu. This bug appear only when deleting with hotkey. Fixed.

When you close designed form while you have open Column editor (for listview)

then after some clicking on it AV occurs.

So maybe this dialog should be modal as all other similar dialogs are ...

EDIT: It can't be modal due to using another dialog: Object Inspector

Yes, this can't be modal, but all other windows can be disabled, like with MenuBuilder now. But for now I made quick fix, because collection editor still need some changes anyway.

I think this importing program needn't handle all complicated situations,

it will be enaugh if it loads successfully 1 GUI from clean GUI script.

This Au3 script can be cleaned by hand before importing

because it's not so complicated for human brain (of skilled AutoIt scripters )

to cut off all non GUI stuff and leave only main GUI code for import (from Au3 to Koda Kxf).

Indeed, this will not support all possible combinations - to do so, need to write fully functional parser like in Autoit, but this beyond this functon goal. But I want this function at least correct handle forms, created by Koda.
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...