As discussed before, the reason is that -drawRect of XGDragView
calls -drawInteriorWithFrame: of the NSImage cell with a wrong argument.
This patch fixes this in simplistic manner.
Wim Oudshoorn
2003-02-17 Willem Rein Oudshoorn <[EMAIL PROTECTED]>
* Source/x11/XGDragView.m ([XGDragView -drawRect:]): use [self frame] instead
of
`rect'. Fixes #101846.
([XGDragView -_handleDrag:]): Fixed typo in comment
([XGDragView -_handleEventDuringDragging:theEvent]): Removed old comment
--- ../../core/back/Source/x11/XGDragView.m Sun Feb 16 09:20:01 2003
+++ ./Source/x11/XGDragView.m Mon Feb 17 20:51:13 2003
@@ -199,7 +199,7 @@
- (void) drawRect: (NSRect)rect
{
- [dragCell drawWithFrame: rect inView: self];
+ [dragCell drawWithFrame: [self frame] inView: self];
}
@@ -427,7 +427,7 @@
return (operationMask != oldOperationMask);
}
-/*
+/**
_setCursor examines the state of the dragging and update
the cursor accordingly. It will not save the current cursor,
if you want to keep the original you have to save it yourself.
@@ -613,7 +613,7 @@
[self _updateAndMoveImageToCorrectPosition];
[NSEvent startPeriodicEventsAfterDelay: 0.02 withPeriod: 0.03];
- // --- Loop that handles all events durring drag operation -----------
+ // --- Loop that handles all events during drag operation -----------
while ([theEvent type] != NSLeftMouseUp)
{
[self _handleEventDuringDragging: theEvent];
@@ -787,10 +787,6 @@
}
break;
case NSPeriodic:
- /*
- * targetWindow check is needed because otherwise events only
- * arrive after an initial mouse move.
- */
if (newPosition.x != dragPosition.x || newPosition.y != dragPosition.y)
{
[self _updateAndMoveImageToCorrectPosition];
_______________________________________________
Bug-gnustep mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gnustep
