Using SCI_MARGINSETSTYLE doesn't trigger a redraw ... why not?

36 views
Skip to first unread message

John Vella

unread,
Jun 15, 2012, 6:06:32 PM6/15/12
to scintilla...@googlegroups.com
I noticed there's no notification of any kind sent to the parent(via NotifyParent) following a change in just a margin's style. I've got an RTEXT margin that I already have text in, but when I try to add some style data without modifying the text, there's no redraw triggered. This doesn't seem right as either a change in the text or the style data should require a redraw.

Am I missing something here or do I need to be responsible for scheduling a redraw manually?

Thanks,
-john

Neil Hodgson

unread,
Jun 15, 2012, 8:25:43 PM6/15/12
to scintilla...@googlegroups.com
John Vella:

I noticed there's no notification of any kind sent to the parent(via NotifyParent) following a change in just a margin's style. I've got an RTEXT margin that I already have text in, but when I try to add some style data without modifying the text, there's no redraw triggered. This doesn't seem right as either a change in the text or the style data should require a redraw.

   OK, that's a bug. Committed a fix as changeset 4187.


   Neil

John Vella

unread,
Jun 15, 2012, 9:17:07 PM6/15/12
to scintilla...@googlegroups.com
Do you happen to know which release this fix will appear in? I need to add a workaround into my code and I wanted to add a comment about when the workaround is no longer needed.

-John

--
You received this message because you are subscribed to the Google Groups "scintilla-interest" group.
To post to this group, send email to scintilla...@googlegroups.com.
To unsubscribe from this group, send email to scintilla-inter...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/scintilla-interest?hl=en.

Neil Hodgson

unread,
Jun 15, 2012, 9:31:27 PM6/15/12
to scintilla...@googlegroups.com
John Vella:

> Do you happen to know which release this fix will appear in? I need to add a workaround into my code and I wanted to add a comment about when the workaround is no longer needed.

The next release may be called 3.2.1. If a major change is added, it could be called 3.3.0 or even 4.0.0.

Neil

Reply all
Reply to author
Forward
0 new messages