No workaround yet, other than using setCurrentSelection, which is not
too bad. However, I still am facing the problem of getting to convert
a point from the PDFSelection boundary to the right format used to
popup the menu.
Alex
On 31-okt-2007, at 14:55, Adam R. Maxwell wrote:
Hi Alex,
On Oct 31, 2007, at 3:51 AM, Alexander Griekspoor wrote:
Is it me or does it no longer work to subclass mouse events in
PDFView? mouseDown is called correctly in my subclass, but after
that I never receive mouseDragged and the mouseUp events. This
poses serious problems for what worked fine under Tiger (showing a
menu upon mouseUp). Is there a workaround or someway to know when
the user stopped selecting?
It's not just you. We have the same problem in an app that relies
heavily on PDFView. If you find a workaround, I'd like to hear it;
I got too frustrated with Xcode's glacial editing speed to work on
it any further. I suspect we'll move everything into mouseDown:,
since that's what Apple seems to require.
--
Adam
*********************************************************
** Alexander Griekspoor PhD **
*********************************************************
EMBL Outstation - Hinxton,
European Bioinformatics Institute,
Rebholz Textmining group
Claiming that the Macintosh is inferior to Windows
because most people use Windows, is like saying
that all other restaurants serve food that is
inferior to McDonalds
