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#202 - Overcoming MS's confusion in styles for forms

Attached to Project: Koda
Opened by Chris Haslam (c.haslam) - Monday, 18 April 2011, 07:24 GMT+3
Last edited by Admin (Lazycat) - Thursday, 05 May 2011, 13:06 GMT+3
Type Feature Request
Category Application
Status Assigned
Assigned To No-one
Operating System All
Severity Low
Priority Low
Reported Version Development
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


MS‘s mess (discussed previously) is driving me nuts!

So for Styles of TAForm I suggest that you add some pseudo-styles. Some I think of: Title bar, Close box, Minimize box, Normal frame, Dialog frame, perhaps Modal.

There are two ways you could add them:

  1. Put them in the Styles tab, at the top of the list, or
  1. Put a Clearer styles for Form checkbox in Options | Designer. When it is checked, have Koda replace all the WS styles which are equivalent to pseudo-styles.

You have more experience than I do with these bloody styles. Perhaps there is no way to get around MS‘s confusion!

There is another way: document the translation from pseudo-styles to WS_ constants in Controls | Form. For that I would need your help.

This task depends upon

Comment by Chris Haslam (c.haslam) - Monday, 18 April 2011, 07:28 GMT+3

The case that drove me nuts: a dialog box with a title bar and a close box, no other boxes, no sys menu.

Comment by Admin (Lazycat) - Monday, 18 April 2011, 14:36 GMT+3

Yeah, form styles :-) I'm still not sure that their logic implemented is correct...

The wholy idea of pseudostyles is ok, but possible ways of realization not yet. All style names an their values in the styles.xml, and with editing "TAForm" section you can have any style pairs you want. But logic of checkbox cross-switching is implemented internally for each control. So, probably simpler to implement some "Presets". When selecting this preset Koda will apply it's value to form and let to do remain work to internal logic.

Comment by Chris Haslam (c.haslam) - Tuesday, 19 April 2011, 06:36 GMT+3

Yes to Presets.

At the moment I am thinking that clicking on New Form might bring up a Presets dialog.

Perhaps they could be updated for an existing form by having the Presets dialog show from Tools | Presets... ?

Comment by Admin (Lazycat) - Tuesday, 19 April 2011, 11:19 GMT+3
Perhaps they could be updated for an existing form by having the Presets dialog show from Tools | Presets... ?

I though about presets somewhere in the object inspector. This way it's will be possible create not only form presets, but also other control-related presets. Maybe, even not only styles, but control properties too.

Comment by Chris Haslam (c.haslam) - Tuesday, 19 April 2011, 18:11 GMT+3

Object Inspector seems to me like a good place for Presets. Make Presets a tab?

Comment by Admin (Lazycat) - Wednesday, 20 April 2011, 18:28 GMT+3

This is open for ideas yet. I though about combo, but maybe some better design come in mind.

Comment by Chris Haslam (c.haslam) - Thursday, 21 April 2011, 05:45 GMT+3

I am thinking that Presets might be an expanding item in the Properties tab of Object Inspector. I don't see how a combo box would work, because a user may wish, e.g., Close box and Minimize.

One possible simplification: no caption, no boxes ⇒ no title. Am I correct?