Koda

Welcome to Koda bug tracker!

At the moment you can post bugreports or suggestions anonymously. But registered users have some benefits: attaching files, commenting, voting, tracking tasks e.t.c.

Due some asshole started spamming tracker, now (at least for some time) it’s not allowed to create anonymous tasks. Sorry for unconvenience.

In edit fields you can use DokuWiki syntax for formatting.

Tasklist

FS#152 - TAUpdown: Appearance in Preview is inconsistent with appearance in AutoIt

Attached to Project: Koda
Opened by Chris Haslam (c.haslam) - Sunday, 02 January 2011, 05:52 GMT+3
Last edited by Admin (Lazycat) - Sunday, 02 January 2011, 15:44 GMT+3
Type Bug Report
Category Application
Status Assigned
Assigned To Admin (Lazycat)
Operating System All
Severity Low
Priority Low
Reported Version Development
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

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.

This task depends upon

Comment by Chris Haslam (c.haslam) - Sunday, 02 January 2011, 06:21 GMT+3
This is not the way AutoIt behaves. 

Correction: AutoIt does behave this way.

An example:

In Koda, an Input with a wide UpDown. Input is 153 wide, UpDown is 100 wide. Total: 253

AutoIt code shows width=253 for Input (and of course, none for UpDown)

AutoIt Reveal shows 238 for Input and 17 for Updown, for 255 total.

Comment by Admin (Lazycat) - Sunday, 02 January 2011, 15:42 GMT+3

Yes, updown in Koda appear differently, as separate control, since we need to have ability set it's own styles.

This can be finetuned though. I'll add it in todo with low priority.

Comment by Chris Haslam (c.haslam) - Saturday, 14 May 2011, 07:18 GMT+3
Comment by Chris Haslam (c.haslam) - Saturday, 14 May 2011, 15:55 GMT+3

Because AutoIt restricts UpDown to being a buddy control, I am thinking that to Koda it should not be a stand-alone control. Perhaps a TAInputUpDown should be a TAInputBox+TAUpDown. But perhaps it is too late to make this change.

Comment by Chris Haslam (c.haslam) - Thursday, 30 June 2011, 18:42 GMT+3

An idea: When a Updown is first created, its width and height should be what they may be at run time. When run, the height of the UpDown = height of Input box. So base the height of an UpDown (until it is attached) on the Form font size.

A "reasonable" Input box is 17 high with the default font size (8.5 points). So the height of an unattached UpDown should be twice the Form's font size.

Testing shows that the width is always approximately 15. So an unattached UpDown should 15 wide.

UpDown properties should never show width and height.

These rules would not apply if AutoIt ever allows an UpDown to exist without being attached.

Loading...