on screen key test

Limelight/Input/CustomOSC/OnScreenButtonState.h

@@ -15,13 +15,16 @@ NS_ASSUME_NONNULL_BEGIN
  We are able to associate this 'OnScreenButtonState' object and its corresponding CALayer onscreen controller button by setting their 'name' properties equal; in our particular case we give them descriptive names such as 'aButton', 'upButton', 'leftStick', etc. By keeping references to the 19 on screen controller buttons (CALayers) in an array, and creating 19 'OnScreenButtonState' objects with names corresponding to these 19 CALayers and keeping them in an array, we can iterate through both arrays to find OSC buttons (CALayers) with the same name as one of the 'OnScreenButtonStateObjects' and then set the CALayer on screen control button's 'position' and 'hidden' property according to the value of the 'OnScreenButtonState' objects 'position' and 'isHidden' properties.
  Naturally we would like the user to be able to save their controller layout configurations so that they can load them between app launches, so we adopt encoding/decoding related protocols so we encode these 'OnScreenButtonState' objects and save them to NSUserDefaults
  */
+
+// OS Button state info obj to be modified
 @interface OnScreenButtonState : NSObject  <NSCoding, NSSecureCoding>
 
 @property NSString *name;
 @property CGPoint position;
 @property BOOL isHidden;
+@property (nonatomic, assign) BOOL isKeyboardButton;
 
-- (id) initWithButtonName:(NSString*)name isHidden:(BOOL)isHidden andPosition:(CGPoint)position;
+- (id) initWithButtonName:(NSString*)name isKeyboardButton:(BOOL)isKeyboardButton isHidden:(BOOL)isHidden andPosition:(CGPoint)position;
 
 + (BOOL) supportsSecureCoding;
 - (void) encodeWithCoder:(NSCoder*)encoder;