Steve,

I just performed a scan of all the properties in Kixforms that are not already 100% dotnet compatible. I also left out all the properties that do not have an equivilent in dotnet. The list below are the properties that would be immediately impacted if I realigned them to dotnet (and the designer) ... not quite as big as i thought. Most of them are relatively new.

What I would like to start is a dialog about whether we should make the switch now (during the beta of 2.3.0) or talk about other alternatives. Its always been my goal to make kixforms as dotnet compatible as possible, so this is just the next step. If anyone has any thoughts on this, would love to hear.

There would probably be some other behavioral changes as well, maybe some color differences or some border differences, think those changes can be done gradually over time. I just want to focus in on these in particular because of the CHM file ...

Anchor Property

Current:

0. None
1. Left
2. Top
4. Right
8. Bottom

Proposed:

0. None
1. Top
2. Bottom
4. Left
8. Right

Alignment Property (TabControl)

Current:

2. Top
8. Bottom

Proposed:

0. Top
1. Bottom
2. Left
3. Right

CheckAlign Property

Current:

4. MiddleLeft
6. MiddleRight

Proposed:

16. MiddleLeft
64. MiddleRight

FlatStyle Property

Current:

0. Normal
1. Flat
2. Popup

Proposed:

0. Flat
1. Popup
2. Normal