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.


FS#153 - TAInput with TAUpdown always sets initial value to UpDown|Min

Attached to Project: Koda
Opened by Chris Haslam (c.haslam) - Sunday, 02 January 2011, 07:31 GMT+3
Last edited by Admin (Lazycat) - Monday, 17 January 2011, 17:54 GMT+3
Type Bug Report
Category Application
Status Postponed
Assigned To No-one
Operating System Windows 2000
Severity Low
Priority Normal
Reported Version Development
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


I set the Min to 1 and the Max to 9 in Updown. I could not then change the Text in Input to 3. I should be able to do this.

This task depends upon

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

This is not a bug. When Updown attached to input control, it's text become controlled by updown (system behaviour). To have default text, set "Position" property of UpDown control.

Maybe this need a little better documentation.

Comment by Chris Haslam (c.haslam) - Monday, 03 January 2011, 07:37 GMT+3

"Position" is unclear to me. How about "Value"? This is what MS calls it for VB. (I do see that MS calls it nPos for C++).

Comment by Admin (Lazycat) - Monday, 03 January 2011, 12:58 GMT+3

Position is Delphi's property for updown. Changing it required adding another property with handler and possibly breaking compatibiity. It's worth?

Comment by Chris Haslam (c.haslam) - Tuesday, 04 January 2011, 00:17 GMT+3

I think that is worth changing Position to Value. Compatibility with what? I would never guess that Position means initial value.

Comment by Admin (Lazycat) - Tuesday, 04 January 2011, 17:49 GMT+3

Compatibility with older forms. It's quite simple to add new property, but not removing/renaming already exisiting.

Microsoft control, btw, used "POS" term, which is "position" shortening...

Comment by Chris Haslam (c.haslam) - Tuesday, 04 January 2011, 18:54 GMT+3

Position is also a property of Form, but there it has a completely different meaning. To me, this is an inconsistency.

You could use Value for Position in the Object Inspector, and retain Position in the .kxf file.

So you have a choice:

  • Be inconsistent in the UI, or
  • Be inconsistent between the UI and the .kxf file.

You can't win completely!