On Mar 4, 2014, at 16:16:53, Kyle Sluder wrote:
> That doesn't seem right… if I press a dead key (like Option-e), then the
> next unmodified space should insert an acute accent in whatever field
> editor is first responder. If your code is triggered solely by virtual
> key code, the user will be
On Tue, Mar 4, 2014, at 12:18 PM, Mills, Steve wrote:
> On Mar 4, 2014, at 13:51:31, Eric Schlegel wrote:
>
> > A little architectural background first: normally, when a keyboard event
> > first arrives in the HIToolbox event queue from the window server, the
> > initial contents are just as yo
Hello all,
I have a test case where I would like to launch a UI. I have a NIB with a
window that I load through code in the test case. Here goes the code :
- (void)testExample
{
NSArray* topLevelWidgets = nil;
NSBundle* theBundle = [NSBundle bundleForClass:[self class]];
[NSAppl
On Mar 4, 2014, at 13:51:31, Eric Schlegel wrote:
> A little architectural background first: normally, when a keyboard event
> first arrives in the HIToolbox event queue from the window server, the
> initial contents are just as you saw - a keycode and key modifiers, but no
> unicode values. T
On Mar 4, 2014, at 11:28 AM, Mills, Steve wrote:
> On Mar 4, 2014, at 13:03:34, Mills, Steve wrote:
>
>> I'm seeing something really odd. We get the NSEvent for the current keyDown
>> when the user types an unmodified space. From that we get the eventRef to
>> pass to some legacy code. Somet
On Mar 4, 2014, at 13:03:34, Mills, Steve wrote:
> I'm seeing something really odd. We get the NSEvent for the current keyDown
> when the user types an unmodified space. From that we get the eventRef to
> pass to some legacy code. Sometimes that EventRef will contain the correct
> space charac
I'm seeing something really odd. We get the NSEvent for the current keyDown
when the user types an unmodified space. From that we get the eventRef to pass
to some legacy code. Sometimes that EventRef will contain the correct space
character (32) in kEventParamKeyMacCharCodes and the correct spac
On 4 Mar 2014, at 9:20 pm, William Squires wrote:
> Question: Do I have to list the @property line in CSquare.h in order for
> users of CSquare to be able to access the "area" property? Or is it
> sufficient that (because I'm overriding it, and it has the same method
> signature - i.e. select
Let's say I have a simple class, CParallelogram
"CParallelogram.h"
//
// CParallelogram.h
//
#import
@interface CParallelogram : NSObject
@property (nonatomic) CGFloat width;
@property (nonatomic) CGFloat height;
@property (nonatomic, readonly) CGFloat interiorAngle;
@property (nonatomic, read
