DC_XbpBrowse:MoveColumn

[Tom]

Hi, Roger.

The method MoveColumn of DC_XbpBrowse works excellent - until Visual Styles and a theme like Aero (Win 7/Vista) is used. In that case, the column headers are painted wrong (upper image: before, lower image: after move):

BTW, the sample "Move Column" in XDemo/sample set 5 still uses an old function. This should use the method "MoveColumn" of DC_XbpBrowse.

[rdonnay]

Tom -

Can you help me out by giving me a sample program?

Roger

[Tom]

Hi, Roger.

Just run your "Move column"-sample with usevisualstyle := .T. on a Vista- or 7-machine with Aero-theme or similar.

[Tom]

Hi, Roger.

Did you find the time to check the sample?

A similar problem comes up if browse columns are hidden/shown using the HIDE clause (with visual styles). Seems that the header and footer presentation gets lost on this way. The leftmost columns in this dialog were hidden and shown again shortly afterwards. Heading and footer are repainted incorrectly.

[rdonnay]

Tom -

I have been overworked lately.
Hope to get settled down soon.
Today, I am trying to catch up on BB postings.

Roger

[Tom]

Hi, Roger.

It seems that AddColumn() and InsColumn() lose some column properties. I found out that I have to reassign "usevisualstyle" to a column header (dataarea seems to work) and the "drawmode" (if ownerdrawing is used with the browse). I believe this is not your mistake, but something inside Xbase++. If I remove a column created with DCBROWSE and add it again afterwards, it's still a DC_XbpColumn object.

"usevisualstyle" was set for the entire browse, the DrawMode was only set for several columns (dataareas).

[rdonnay]

Tom -

Are you saying that you have found a workaround or do you still need help from me?

Roger

[Tom]

Hi, Roger.

If "usevisualstyle" is used and a theme is active, columns (column headers) added or moved lose these informations. In addition, the DrawMode of the dataareas gets lost. These iVars have to be set manually after a column is moved or added again. I do this as a workaround. This is not very satisfying, but it works.

[rdonnay]

If you show me your workaround, I will add it to eXpress++ build 255.