Sorry if this is stating the obvious, but did you also set your
initialFirstResponder correctly? If your user's first action isn't a
mouse click, the focus might not be on the QCView, and any keystroke
might go to some other control.
On 14 Apr 2008, at 09:21, vade wrote:
I noticed this too.
I had to manage this myself, as the checkbox did not seem to work.
(qcView is the IBOutlet for the QCView in the main app controller)
call this on awakeFromNib or -applicationDidFinishLaunching or
somesuch:
[qcView setEventForwardingMask :NSAnyEventMask];
I did not mark it as a bug as the app I was fiddling with at the
time was majorly under construction, but this fixed it. Should work
- good luck.
On Apr 14, 2008, at 3:44 AM, Chris Wood wrote:
Is there a bug with 'forward all events' when using a QC patch in
interface builder?
I'm making a photoshop-like paint tool with QC, which works fine in
QC itself. When I add the QC View into an application window, I can
see the brush outline following the mouse within the app suggesting
that mouse x+y work fine, but the mouse buttons and key presses
aren't recognised. The 'forward all events' option seems to be the
solution according to the documentation + tutorial, but it doesn't
have any effect.
Am I doing it wrong, or is there a problem with it? If there is,
what's the best way to work around it?
Thanks,
Chris Wood
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
