Re: Re: Keyboard problems in Logic
Re: Re: Keyboard problems in Logic
- Subject: Re: Re: Keyboard problems in Logic
- From: email@hidden
- Date: Fri, 12 Mar 2010 13:17:34 +0000
On Thu 11/03/10 6:41 PM , Howard Moon email@hidden sent:
Has anyone gotten any more info on this? Apparently, Logic 9 has broken what works fine in Logic 7 and 8. Now our software no longer traps key strokes (in our Carbon plug-in window.) All of the numeric keys (above the qwerty keys) now cause the screen set to change. I tried deleting the key bindings for the screen sets, but all that did was cause Logic to beep at me, telling me I'd pressed an invalid key!
Is there any way to route keystrokes to the plug-in in a Carbon (composited) window?
Thanks,
-Howard
On Aug 17, 2009, at 4:46 AM, john smith wrote:
So, still no word from Apple and/or Emagic on this... Can it really be true that the only way to solve is to use low-level code, which I cannot even debug (since it will disable keyboard if I enter a breakpoint in the code)?
(And yes, it has to be a Carbon window :-))
Thanks for the reply. It seems that this API could solve the problem, although I was hoping it didn't have to be this low-level. Simply put, the more low-level, the greater is the chance that something goes wrong.
>
> I don't know anything of plug-ins programming, yet as both a Logic
> user and mac os x programmer i'll give you my two cents advice.
> Maybe you could give a look at the Quartz Event Taps, that are damn
> handy when trying to grab events from the keyboard mouse and others.
> In your case a passive listening tap would do the trick, and install/
> remove it when your in your so called "edit mode".
>
> I've used these taps and find them far more convenient than carbon
> event handlers, not to mention that they're not relying on the now
> aged (and supposed to disappear) carbon, carbon event handlers have a
> status that's too uncertain to me.
>
> Quote from the Quart Event Services documentation : "Introduced in Mac
> OS X version 10.4, event taps provide functionality similar to the
> Win32 functions SetWinEventHook when used to establish an out-of-
> context event hook, and SendInput. "
>
> >
> > I'm trying to solve a problem we have with a plug-in in Logic.
> >> >
> > Now, the problem is that Logic seems to get the "first run" on the
> > keyboard events. For instance, if 1 is pressed we get the keyboard
> > input, and all is well. If 0 is pressed, we never get the event
> > (Logic seems to use this as a shortcut).
> >
> > So, as said, it seems to me like Logic first decides whether it
> > wants the event or not. Which is, obviously, reversed to how we
> > would like it.
> >
For any user input, I've started using Modal windows for registration and preset names etc.
I've had these keyboard issues with Logic 8, as well as some other hosts. As for trapping controls for GUI navagation, I gave up on that for plug-ins a long while back.
Cheers,
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden