Jump to content

Koda ver 1.5 uploaded


lookfar
 Share

Recommended Posts

  • Replies 297
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Ouch :P

1) Translation issues (lang_eng.xml):

All fixed.

2) history.txt consistency stucture

instead of: Beta 2006-08-18

should be: Beta 1.5.1.15 (2006-08-18)

Good idea. One problem, I'm not remember when which version was. Though, last ones and future are ok.

3) create 2 forms

...

- press Reset --> AV error, see screenshot ...

Bad thing, fixed. Now form list will always have selected form.

4) Bad refreshing of overlaped controls when moving:

Yes, long time issue... I'm done some workaround, this is not perfect, but better then before.

5) when change tab order of controls their order maybe should be changed also in object treeview,

but this one I'm not sure

Maybe, don't sure too. Problem is that controls in tree show in order as they are created in form. To do that to reflect taborder, full rewriting of treeview fill procedure will required.

And what about release version? Last one was in February it's too long - almost like AutoIt :-)

I think now it's time for release because it can be bundled with new Scite4Autoit (with new release 3.2 of

Autoit).

Lol, when I saw today how many new bugs found, I'm not pretty sure about that :nuke:

No prob with new features, they are not added now, but need to fix at least visible bugs.

Link to comment
Share on other sites

Another issues:

1) menu designer:

This is codegen issue... will fix it.

2) Progress (and Slider)

Fixed. Also changed slider default max value to 100 as in autoit.

3) Edit & UpDown

Not good... need to think how to avoid that.

4) Code window (F9)

Yeah, forget them when changed control to RichEdit...

5) Picture editor

Oh my... wonder, when it get OnTop property? :P Fixed...

6) Image and Icon control

They have, picture 100x100 and icon 32x32... Never had that prob.

7) List index out of bounds (0) in Object treeview

Fixed.

8) Idea: disabled controls also in desing time?

Will see, maybe after release :nuke:
Link to comment
Share on other sites

Something wrong with big replies count in one post...

1) Property Enabled has no effect at Form

Hm, when @SW_DISABLE was added?..

2) Property Icon at Form - when I select one icon there is still (None) in Object Inspector

I saw that issue, but forget... Will look...

3) Label has Property Color which is in fact Background color

4) Label has not Property Background Color (AutoIt support it)

Yes, here some inconsistence: for all controls except progress BG color is set by "Color" property. Text color is set by "Color" subproperty for "Font" property. This is logical, though not familiar.

Of course, this can be changed (fro example Color and BkColor), but this require big changes.

I think it could be as comment (first char ; ) to avoid strange syntax highlighting in Scite

Why not? But I think I better make this, to avoid additional lines:

#Region ### START Koda GUI section ### Form=c:\path\form.kxf

#EndRegion ### END Koda GUI section

Yet I'd like to use it also for hints. For the moment, despite the %var% option, it is generating "%var%" instead of $var.

Would it be possible to implement this option for Hints too ?

Easy, just forget about hints... Done.

Another litle thing, when adding a picture, in the generation code the path is generated fully. It would be interesting to get in the generated code a relative path.

Yes, some resources management is definitely need. This is in the todo, but only after release.
Link to comment
Share on other sites

Now I tested it on WIN98SE and also on WINXP:

On WINXP it's OK as you said.

But on WIN98SE Image and Icon control has initial Width and Height = 0

Errm, don't tested it on the 9x systems... I can't test it myself now, uploaded test version with fix - this may help or maybe not...

http://www.autoitscript.com/fileman/users/lookfar/FD.exe

Link to comment
Share on other sites

QUOTE(Zedna @ Aug 18 2006, 06:43 PM)

2) history.txt consistency stucture

instead of: Beta 2006-08-18

should be: Beta 1.5.1.15 (2006-08-18)

Good idea. One problem, I'm not remember when which version was. Though, last ones and future are ok.

Here is complete history version/date (I have all versions on my HDD :P ):

Beta 1.5.1.15 (2006-08-18)

Beta 1.5.1.14 (2006-08-16)

Beta 1.5.1.13 (2006-08-14)

Beta 1.5.1.12 (2006-08-11)

Beta 1.5.1.11 (2006-08-10)

Beta 1.5.1.10 (2006-08-07)

Beta 1.5.1.9 (2006-08-05)

Beta 1.5.1.8 (2006-07-29)

Beta 1.5.1.7 (2006-07-23)

Beta 1.5.1.6 (2006-05-11) - not (2006-05-12)

Beta 1.5.1.5 (2006-05-05)

Beta 1.5.1.4 (2006-04-29) - same version as (2006-04-27)

Beta 1.5.1.4 (2006-04-27)

Beta 1.5.1.3 (2006-04-17) - same version as (2006-04-11)

Beta 1.5.1.3 (2006-04-11)

Beta 1.5.1.2 (2006-04-03)

Release 1.5.1 (2006-02-25) - not version 1.5.0 and not (2006-02-20)

Edited by Zedna
Link to comment
Share on other sites

Here is complete history version/date (I have all versions on my HDD :P ):

Wow!

Think I'm have them all too, but some time ago I'm not renamed each release code to something sensible (ashamed...), and now recall what release was folder Koda11 or Koda111, or this was not release at all is practically impossible :nuke:

Yes. This version is OK on WIN98SE.

Fine.
Link to comment
Share on other sites

Wow!

Think I'm have them all too, but some time ago I'm not renamed each release code to something sensible (ashamed...), and now recall what release was folder Koda11 or Koda111, or this was not release at all is practically impossible :P

I you wish you can have it all:

I uploaded all versions of Koda (zipped into one file) on free server www.yousendit.com

Link is here and will expire in 7 days. File has 9.8 MB

Link to comment
Share on other sites

Current beta with all fixes from last few posts :nuke:

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

If translators want to see their languages in upcoming release, this is the best time to update it! :P Old ones can't be used, because while development was changed more then half of sentences and id's.

8) Idea: disabled controls also in desing time?

I'm recall some tests, most likely this can't be done, because designer can't work with disabled controls. Only way - custom painting control state, but this is too complicated way...

Link to comment
Share on other sites

Current beta with all fixes from last few posts :P

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

One little thing:

Contextmenu - when I create context menu on the form and don't assign it to any control

then is not generated code for it.

I'm not sure if this is correct or no.

My idea is to use such action for dynamically assigned context menus,

so I prepare all of them in design time and at run time reassign them as desired.

I didn't need this yet but it's teoretically possible.

What do you think about this Lazycat?

EDIT:

Now I noticed: In AutoIt is in GUICtrlCreateContextMenu as parameter control

$Button1context = GUICtrlCreateContextMenu($Button1)

so my idea about reassign context menus is not possible.

Forget about this.

Edited by Zedna
Link to comment
Share on other sites

ComboBox: value of property Text should be in generated code:

Of course... Fixed.

Tab Order Editor in version 1.5.1.16 has mismatched chars in English (Title and Cancel)

Fixed.

1) after click on OK is hidden also form in designer

Ohh... this bug appear after refresh fix was applied :P

2) There should be added also Text (or Caption) of controls and not only Name and Type

for situation when I have Labels (or cther controls) with empty names (for not generating variable for them)

Yeah, indeed. The same "virtual" name as in tree and combo. Done.
Link to comment
Share on other sites

ComboBox: value of property Text should be in generated code:

GUICtrlCreateCombo("text", ...)oÝ÷ Øl¥u·¢ºÞrÙrjëh×6GUICtrlCreateCombo("", 128, 64, 129, 21)
GUICtrlSetData(-1, "Items") ; a|b|c
GUICtrlSetData(-1, "Text") ; boÝ÷ Ù·jëwâ®Ë^Å©©æ«z)Ý®]£  í뽩nzÆÚmÆÄÿlKÞ·­µêⱫ­¢+ÙU%
Ñɱ
ÉÑ
½µ¼ ÅÕ½ÐìÅÕ½Ðì°ÄÈà°ØаÄÈä°ÈĤ)U%
ÑɱMÑÑ ´Ä°ÅÕ½Ðí%ѵÌÅÕ½Ðì°ÅÕ½ÐíQáÐÅÕ½Ðì¤ìññì
Edited by Zedna
Link to comment
Share on other sites

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.

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