Menu

#155 Obsolete properties HighlightBackgroundColor and HighlightForegroundColor still default in designer

C#_v2.9
closed
obsolete (1)
1
2016-05-05
2015-12-04
bkraul
No

The properties HighlightForegroundColor and HighlightBackgroundColor have become obsolete in lieu of the new properties SelectedForeColor and SelectedBackColor. However, the VisualStudio designer is still picking the old properties as the defaults when designing a form with an ObjectListView control, causing obsolete property warnings. Even after changing the properties to the new properties, eventually the designer reverts to the old properties, and the warnings are shown again.

Suggest that the attribute [DesignerSerializationVisibility(DesignerSerializationVisibility.Hidden)] be used for those obsolete properties.

1 Attachments

Discussion

  • bkraul

    bkraul - 2015-12-07

    Phillip, thanks for your reply. However, unless I am missing something, I don't see how the link for the fix you describe in your message relates to this particular issue, which I believe you perhaps meant for someone else?

     
  • Phillip Piper

    Phillip Piper - 2015-12-08

    I'm pretty sure that's the right thread. I tried to link to the last message in thread, but it seems SourceForge doesn't allow that.

    The fix is in the last message in the thread.

     
  • Stefan Lampert

    Stefan Lampert - 2016-04-21

    Hi, is this issue going to be resolved in the near future?

     
  • bkraul

    bkraul - 2016-04-21

    Phllip, I kinda forgot about this thread. I still don't think the fix you are linking to relates to this particular issue. This is about properties that have been obsoleted, where a simple component model attribute could resolve. That is what I did in my fork. I merely would like to see this implemented in upstream.

    The link for your fix refers to a completely unrelated issue dealling with NullRefs when editing a cell.

     
  • Phillip Piper

    Phillip Piper - 2016-05-05
    • status: open --> closed
     
  • Phillip Piper

    Phillip Piper - 2016-05-05

    This was fixed in v2.9.1

     
  • bkraul

    bkraul - 2016-05-05

    Phillip,

    You da man! Thank you for your efforts. Your product is like no other.

     

Log in to post a comment.