Richard,
For one thing, I have four Macs on my desks and no room for PCs; another, it
would be a sacrilege to have a real PC on sacred Mac grounds! (smile) My
friends could then say - "he, too, finally succumbed to the M$ voodoo magic".
Incidentally, I thought it was interesting to note that In
Joe Lewis Wilkins wrote:
I guess I need to burn a CD and test this on somebody's real PC. Thanks for the
confirmation Jacqui.
Good for now, but I can't recommend having a PC on hand strongly enough.
PCs are cheap, and second-hand ones more so. You can probably pick up a
decent second-hand
I guess I need to burn a CD and test this on somebody's real PC. Thanks for the
confirmation Jacqui.
Joe Lewis Wilkins
Architect & Director of Product Development for GSI
On Jan 5, 2011, at 10:15 AM, J. Landman Gay wrote:
> On 1/5/11 12:00 PM, Joe Lewis Wilkins wrote:
>> Actually, I was not aw
On 1/5/11 12:00 PM, Joe Lewis Wilkins wrote:
Actually, I was not aware of this. Not sure that I even understand
what you are saying. Are you saying that I don't even have to have a
handler for the Control Keys; that LC will automatically provide
functioning of the CommandKeys as if they are Cont
Actually, I was not aware of this. Not sure that I even understand what you are
saying. Are you saying that I don't even have to have a handler for the Control
Keys; that LC will automatically provide functioning of the CommandKeys as if
they are ControlKeys when creating the Windows version? I
On 1/5/11 11:00 AM, Joe Lewis Wilkins wrote:
I have yet to resolve this issue. Strangely enough, if I allow the
OSX version to "see" the controlKeyDown handler, they work the same
as the commandKeyDown handler - both being in the stacks' scripts.
You know that LC maps the control key on Windows
Thanks Richard. I hadn't thought of that angle. I'll check it out.
Joe Lewis Wilkins
Architect & Director of Product Development for GSI
On Jan 5, 2011, at 9:14 AM, Richard Gaskin wrote:
> Joe Lewis Wilkins wrote:
>
> > I have yet to resolve this issue. Strangely enough, if I allow the
> > OS
Joe Lewis Wilkins wrote:
> I have yet to resolve this issue. Strangely enough, if I allow the
> OSX version to "see" the controlKeyDown handler, they work the same
> as the commandKeyDown handler - both being in the stacks' scripts.
> The only area of suspicion would likely be that I'm running Wi
I have yet to resolve this issue. Strangely enough, if I allow the OSX version
to "see" the controlKeyDown handler, they work the same as the commandKeyDown
handler - both being in the stacks' scripts. The only area of suspicion would
likely be that I'm running WindowsXP under VM Fusion on my Ma
