Re: NSCursor mismatched push and pop
El mar, 08-10-2013 a las 00:36 -0600, Germán Arias escribió:
> El lun, 07-10-2013 a las 16:06 -0600, Germán Arias escribió:
> > mouseMoved, has a the delta:
> >
> > deltaX = 430.00, deltaY = 82.00
> >
> > This assumes the cursor is entering, and set the I-beam again.
> >
>
> I added some NSLog messages to see what is happening here. Are these:
>
> _lastPoint after resert cursor rects {x = 454; y = 62}
> _lastPoint used in _checkCursorRectangles {x = 33; y = 468}
> _lastPoint in MouseMoved {x = 453; y = 62}
>
> First message is the value of _lastPoint after call the method
> -resetCursorRectangles after close the "open" panel. Second message show
> the value of _lastPoint used at _checkCursorRectangles:, when mouse
> moves. And the last message is the value that MouseMoved set to
> _lastPoint after check all rectangles.
>
> The coordinates {x = 33; y = 468}, are where I clicked over the toolbar
> item. How is this possible? There isn't any piece of code that restores
> a previous value of mouse location to _lastPoint. So, what is happening
> here?
>
> Germán.
>
I found the problem. The NSToolBarItem send a NSLeftMouseDown event. But
this is processed after close the "Open" panel, and after the window has
reset its cursor rectangles.
Germán.
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: NSCursor mismatched push and pop
El lun, 07-10-2013 a las 16:06 -0600, Germán Arias escribió:
> mouseMoved, has a the delta:
>
> deltaX = 430.00, deltaY = 82.00
>
> This assumes the cursor is entering, and set the I-beam again.
>
I added some NSLog messages to see what is happening here. Are these:
_lastPoint after resert cursor rects {x = 454; y = 62}
_lastPoint used in _checkCursorRectangles {x = 33; y = 468}
_lastPoint in MouseMoved {x = 453; y = 62}
First message is the value of _lastPoint after call the method
-resetCursorRectangles after close the "open" panel. Second message show
the value of _lastPoint used at _checkCursorRectangles:, when mouse
moves. And the last message is the value that MouseMoved set to
_lastPoint after check all rectangles.
The coordinates {x = 33; y = 468}, are where I clicked over the toolbar
item. How is this possible? There isn't any piece of code that restores
a previous value of mouse location to _lastPoint. So, what is happening
here?
Germán.
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: NSCursor mismatched push and pop
I'm wrong, the AppKitDefined event is for the panel, not for the window. Germán. El lun, 07-10-2013 a las 16:06 -0600, Germán Arias escribió: > > Well, after close the open panel, the NSCursorUpdate event is processed > correctly, with the point: > > x = 430.00, y = 81.00 > > Then one event AppKitDefined (subtype GSAppKitWindowLeave) set the last > point to: > > x = -1.00, y = -1.00. > > With this the next event, mouseMoved, has a the delta: > > deltaX = 430.00, deltaY = 82.00 > > This assumes the cursor is entering, and set the I-beam again. > > The GSAppKitWindowLeave is a event that should be processed before > launch the "Open" panel, but is processed later, after close it. I'm not > sure how solve this. > > Thanks for this log David. > > Germán. > > > > ___ > Gnustep-dev mailing list > Gnustep-dev@gnu.org > https://lists.gnu.org/mailman/listinfo/gnustep-dev ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
themes: highlighted cell text colors
Hi, I'm working on the Nesedah theme: http://jesseross.com/clients/gnustep/ui/concepts/23/camaelon_nesedah.png One thing that is giving me trouble is getting selected cells in NSTableView and NSBrowser to have a highlighted text color. For tables, I've found the relevant place in GSThemeDrawing.m; it's -drawTableViewRow:clipRect:inView:, and I have access to the NSCell and know whether the table cell should be selected. My problem is, I don't know how I should I set up the cell. Simply calling -setHighlighted: YES doesn't cause a NSTextFieldCell to draw differently than normal. I could explicitly set the text color to a highlighted text color in -drawTableViewRow:clipRect:inView:, but this would break cells that have custom text colors already set, which seems like a bad thing. I'd appreciate any hints! Thanks, Eric ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: NSCursor mismatched push and pop
El dom, 06-10-2013 a las 21:31 +0100, David Chisnall escribió: > Ah, sorry, it seems my -base was quite a way out of date. > > I've put the log here: > > http://theravensnest.org/NSCursor.3.log > > David > Well, after close the open panel, the NSCursorUpdate event is processed correctly, with the point: x = 430.00, y = 81.00 Then one event AppKitDefined (subtype GSAppKitWindowLeave) set the last point to: x = -1.00, y = -1.00. With this the next event, mouseMoved, has a the delta: deltaX = 430.00, deltaY = 82.00 This assumes the cursor is entering, and set the I-beam again. The GSAppKitWindowLeave is a event that should be processed before launch the "Open" panel, but is processed later, after close it. I'm not sure how solve this. Thanks for this log David. Germán. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: problems debugging with clang 3.2, gdb 7.6, libobjc2 SVN, and Ubuntu 13.10
On Mon, Oct 7, 2013 at 12:41 AM, David Chisnall wrote: > Yes, the debugger needs to know how to look up the ivar offsets and currently > gdb doesn't know how to do that. I'll hopefully add support for our ABI to > LLDB soon, now that the Linux / FreeBSD ports are in an approximately useable > state. > > If you want to inspect ivars in the debugger currently, you should use the > runtime's introspection functions rather than ->. FWIW, for gdb as well as the above, the most recent round of modern GNU runtime changes which neutered the Object class, have stopped gdb's objective-c testsuite from compiling. The gdb testsuite probably needs to include its own root class now since there is apparently no method to allocate an Object. This would be needed to test the above changes or could be done separately without the above changes. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: problems debugging with clang 3.2, gdb 7.6, libobjc2 SVN, and Ubuntu 13.10
On 7 Oct 2013, at 02:30, Eric Wasylishen wrote: > Thanks for the pointers… > > I reconfigured make without enabling the nonfragile ABI (just used "CC=clang > ./configure --enable-debug-by-default"), rebuilt everything, and now stepping > into Objective-C methods works with gdb, as does ivar printing. > > So do gdb and lldb need some changes to support the nonfragile ABI? If that's > the case, maybe we should display a warning when configuring make with > --enable-nonfragile-abi, so people know that debugging will be broken. Yes, the debugger needs to know how to look up the ivar offsets and currently gdb doesn't know how to do that. I'll hopefully add support for our ABI to LLDB soon, now that the Linux / FreeBSD ports are in an approximately useable state. If you want to inspect ivars in the debugger currently, you should use the runtime's introspection functions rather than ->. David ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
