• Status Assigned
  • Percent Complete
  • Task Type Bug Report
  • Category Application
  • Assigned To
  • Operating System All
  • Severity Low
  • Priority Defer
  • Reported Version Development
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Koda
Opened by Chris Haslam - 02.01.2011
Last edited by Admin - 02.01.2011

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

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.

Chris Haslam commented on 02.01.2011 03:21
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.

Admin commented on 02.01.2011 12:42

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.

Chris Haslam commented on 14.05.2011 03:18
Chris Haslam commented on 14.05.2011 11:55

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.

Chris Haslam commented on 30.06.2011 14:42

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.


Available keyboard shortcuts


Task Details

Task Editing