SneakyInput 0.3 is on it's way! « cocos2d for iPhone

cocos2d for iPhone » Programming » Programming - Everything else

SneakyInput 0.3 is on it's way!

(4 posts) (4 voices)

Started 1 year ago by sneakyness
Latest reply from Benihana

Tags:

sneakyness
Member

Hello everybody! It's been a while since you've heard the word on SneakyInput.

The word is: I'm kicking ass! :) I've received $105 in donations as of version 0.2. You might be wondering what all that money buys, the answer is: SneakyInput 0.3!

I'm planning the next version right now, here are the currently planned features:

Directional Analog Joysticks/Sliders - Joysticks that only work in two directions from the center in one line. This can be used with or without auto-center to make all sorts of controls, such as thruster, balance, or volume/fader controls.

Visual Input Diagnostics - Debugging tools, graphs that show data for the sneakyinput it's enabled for, bars for force, velocity indicators, rotation, angle, degrees, position, button state, slider position, etc. Also doubles as indicators for an interface, such as making a green light to show that something is enabled.

Event System/Callbacks - This one is a doozie, and I would appreciate a lot of user input.(pun intended) Basically you'll be able to set events for certain states, so like, a range of force in a certain direction, or the activation of a button. There will also be all the usual callbacks, such as input started/finished/is happening/etc.

Draggable Buttons - Pretty self explanatory

SneakyKnob/SneakySlider - A knob and a slider, with and without "clicks", and also toggleable auto-return and value-linking (moves to reflect change in value)

SneakyBlister - A controller that will generate SneakyButtons around an object, so that you are presented with options when you touch an object. Pretty handy stuff. I'm sure everybody will really appreciate/abuse this one ;)

Now, these are just the things I want to do. I'm pretty overambitious. We'll see how much of this really makes it into the next version. Do you have suggestions? Do you have something you really want? A good idea? Do you want to collaborate? Come to the GitHub! You can post your thoughts and ideas here as well, but the only way to make sure everybody working on the project will see what you said is to post them in Issues on the GitHub.

If you use SneakyInput, be sure to let us know, we really appreciate it! :)

Posted 1 year ago #
Corrupter
Member

go sneaky Nerd ;)

Posted 1 year ago #
JohnnyFlash
Member

Hey Sneakyness... what's the status of 0.3? Have you thought about adding a develop branch to your git repository?

Posted 1 year ago #
Benihana
Member
This seems to be the most recent official SneakyInput thread (even though 0.4 is in the git), so I'll post this here. I made two changes two SneakyInput that I thought I'd share, in case it helps someone for whom the changes would not be trivial or obvious.

Visibility/Disabling
I don't want my controls accessible while not visible, and I don't want to have to add/remove child whenever I disable them (you could also add some kind of disable code like CCMenus which would gray out buttons). I added a visible check to the active check done in ccTouchBegan as such:
```
if (active || ![self visible]) return NO;
```
and added an explicit visible setter for SneakyButtonSkinnedBase because SneakyButtons are not normally children of the base and thus don't receive their visibility automatically:
```
- (void) setVisible:(BOOL)v {
	if(button){
		[button setVisible:v];
	}
	[super setVisible:v];
}
```
This also fixes issues with buttons intercepting touches while they are not visible. A nearly identical change can be done to SneakyJoystick and its SkinnedBase, except that it does not do an active check:
```
if (![self visible]) return NO;
```
```
- (void) setVisible:(BOOL)v {
	if(joystick){
		[joystick setVisible:v];
	}
	[super setVisible:v];
}
```
KVO compliance
Sometimes you want to poll a button, and if the button is active, do something (over and over again). Other times, it's better to just watch a button and change something locally when the button changes states. Unfortunately, SneakyInput currently sets value directly, instead of its property. I made the following changes to implement automatic KVO support:

Change the value property to assign (instead of readonly):
```
@property (nonatomic, assign) BOOL value;
```
Change all instances of value in SneakyButton.m to self.value, except in the initializer (it might be safe to change that one as well, but my understanding is that it's bad design to use setters before the object is completely initialized).

You should now be able to access the @"value" key using KVO. You could make similar changes to SneakyJoystick, however I'm sticking with polling it, since it can often change at framerate and I'd rather control polling and apply the change directly (I poll it every 1/15 sec and apply thrust).
Posted 11 months ago #

RSS feed for this topic

Reply

You must log in to post.