Follow-up Comment #2, bug #21478 (project gnustep):
I would like to help out on this problem, but will need some more information
on the internal working of Gorm.
First I would expect that there could be two possible sources for this
problem. One would be just a redraw issue, trickered by Gorm missing some of
the draw method calls from gui. In this case the changes to the draw mechanism
in NSView would be the reason. I noticed that Gorm overrides some internal
NSView methods in GormViewEditor (no idea, if this class is really relevant
here). There displayIfNeededInRectIgnoringOpacity: and
displayRectIgnoringOpacity: are defined. Now the correct call to override
would be displayRectIgnoringOpacity:inContext: and it would be even better not
to work on that level, but to do what ever is needed for the view in
drawRect:. This would also be save against futher changes of the internal
drawing code, which is to be expected as soon as we start to optimize NSView.
The other potential cause I see is event processing. Here I am really lost,
as I don't have a glue where to look in Gorm. Just the same class
GormViewEditor has a very strange set of event method overrides.
So please give me a hint and I join in to chase this bug.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?21478>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
