Julian:
More information, in src/mac/carbon/toplevel.cpp there is a routine
SetupMouseEvent
which is suppose to set the appropriate events. It is never called with
a Carbon Event related to mouse up. I get Carbon events for mouse moves
and I get Carbon events for mouse downs. If I change the mouse down
logic to call an wx UP event instead of a wx DOWN event my test program
responds as expected.
Forgive my flow of conscientiousness, this is my first Mac program. It
will take a bit to become tolerably fluent in Mac speak.
Ralph Pass
Julian Smart wrote:
>
> Hi,
>
> I don't know why this is; perhaps you can put a breakpoint in the Mac
> code that processes button up events: see src/mac/carbon/toplevel.cpp.
> However some implementations have trouble with intercepting events for
> (and drawing on) frames, so usually having at least one window in the
> frame client area is recommended. If things still didn't work properly
> with that window, then I'd be concerned.
>
> Regards,
>
>; Julian
>
> Ralph Pass wrote:
> > Julian:
> >
>; > Attached is a tar file with an example. If you click in the window
> > there should be a wxMessageBox announcing a button down in a general
> > mouse event (always shows), a wxMessageBox announcing a button up in a
> > general mouse event (does not show), and a wxMessageBox announcing a
> > wxFrame LeftUp event (does not show). If you take out the button down
>; > logic, then no wxMessageBoxes ever appear. It works as expected under
> > windows. (you need to comment out the Button Down wxMessageBox to see
> > the other boxes in Windows. I do the same thing on the Mac)
>; >
>; >
>; > Puzzled,
> > Ralph Pass
>; >
>; >
>; >
>; > Julian Smart wrote:
> >
>; >> Hi Ralph,
> >>
> >> Sorry, I deduced wrongly that you were trying to intercept a button-up
> >> from a wxButton control.
> >>
> >> Ralph Pass wrote:
> >>
> >>> Julian:
> >>>
> >>> Perhaps I am missing something here, like the definition of a
> >>>
> >> predefined
> >>
> >>> control.
> >>>
> >>> Is a wxFrame a predefined control? a wxBitmap?
> >>>
> >>>
> >> A wxBitmap is not a control, and wxFrame wasn't a control in the
> sense I
> >> was meaning - something that presents a higher-level command event to
> >> the application.
> >>
> >>> What I have is a bitmap that I am presenting. It is tied to the real
>; >>> world and my program knows this connection. When I click on a point I
> >>> want to have the program present information derived from tying the
> >>> mouse click point to the real world, and then getting the information
> >>> for that real world point.
> >>>
> >>>
> >> I can't think why there should be a problem getting a mouse up event if
> >> you've defined a handler for it and an event table entry... but then
>; >> it's hard to say without seeing code.
> >>
> >> Regards,
> >>
> >> Julian
> >>
> >>
> >>
> >
>; >
>; >
>; > Yahoo! Groups Links
> >
>; >
>; >
>; >
>;
> --
> Julian Smart, Anthemion Software Ltd.
>; 28/5 Gillespie Crescent, Edinburgh, Midlothian, EH10 4HU
> www.anthemion.co.uk | +44 (0)131 229 5306
>; Tools for writers: www.writerscafe.co.uk
> wxWidgets RAD: www.anthemion.co.uk/dialogblocks
>
>
.
