Air Manager / Knobster / Custom Instrument

[zenom]

I really liked KnobXP but wanted something I could push the buttons on in Air Manager. I created a knob that has the same sort of commands. Minor CW, Minor CCW, Major CW, Major CCW and then I also have a button press command.

All the knobs work, but the button press on the minor button does not work from the knobster. It works if I disable the knobster and use the mouse, but it does not work when highlighted and I click minor knob with the callback set.

Code: Select all

dial_minor = dial_add("alt_knob.png", 30, 42, 90, 90, 1, minor_callback, knob_pressed_callback)

function knob_pressed_callback()
    xpl_command(user_prop_get(minor_pressed_cmd))
end

What am I missing for the knobster to do the knob_pressed_callback?

[Ralph]

That's not how the dial works for button presses. What you're using is a dial pressed and released callback, that's not meant to act as a button. You have to add a button on top of the dial.

[Keith Baxter]

That's not how the dial works for button presses. What you're using is a dial pressed and released callback, that's not meant to act as a button. You have to add a button on top of the dial.

@Ralph

Suggestion...

The API does little to elaborate on this function. Something to look at and enhance for users.

I am referring to the "Example" section of the API...

What exactly does....

dial_id = dial_add(image, x, y, width, height, acceleration, direction_callback, pressed_callback, released_callback)

Do ???

http://siminnovations.com/wiki/index.php?title=Dial_add

Keith

EDIT: A example relating to Knobster characteristics, i think would be a useful indication in all features.

[zenom]

Is this just for knobster? Because if I do touch, it works fine, but with the knobster it doesn't. Which is confusing.

[Ralph]

No like I said, this is not for the Knobster. This is only for mouse and touch. It is the callback for press and release of the dial. The Knobster has no way of knowing if your fingers are on the dial. Sounds pretty obvious to me But I'll add a description to the wiki.

[Sling]

A dial is a rotary control so by definition any callbacks used with it are related to its use and nothing to do with buttons. I agree with Ralph I think this should be obvious. As stated several times on this forum previously the knobster functionality is implicit to the way the base instrument is coded. Meaning if you co-locate a button with 2 rotaries (dial etc) then you get the 3 independent functions that a knobster provides. If you omit one of the 3 then that functionality will be missing from the knobster also. The knobster does not add instrument functionality, it just mimics the soft controls into hardware.

[jph]

Agreed, an overreaching desire to 'make things more user friendly (from one persons perspective!) ' most often leads to more confusion.

[Keith Baxter]

Hi,

For me, and obviously the OP and possibly many more users, there is a lack of explanation on how the {"pressed_callback" and "released_callback"} argument/callback works. Sorry @Sling I disagree with it being obvious, for me at least.

Basically what I am saying is that the API/WIKI is a little light with how these arguments/callbacks work. And. If they work with Knobster.

I wonder why the pressed arguments were implemented in the first place? Helping me to understand these functions would be awesome.

Yes guys, stacking dials and buttons in Z order is probably the better option and best understood. I use that method and it works perfectly.


Keith

[Sling]

Keith,

Obvious in the sense that you need some understanding of what a callback is, what a dial is and how the API functions apply these. If you dumb it down so much you will end up with stuff like you see in product instructions to protect against stupidity. Think about in the context of dial what a pressed callback would do. The wiki currently says ‘This function will be called when the dial is being pressed.’ A Dial is a rotary device and has no button so the pressed in this context I interpret as the press of the mouse or your finger in the case of touch. Release by its name implies it gets called when you let go of the mouse click or lift your finger. Because they are useful in some instances but not absolutely needed in all cases for a dial they are optional arguments.

As I explained before to make the soft controls for everything on a knobster to control, one needs to add 2 dials and a button all co-located. In the OP’s case he omitted the button which is why the knobster only saw the 2 dials. When not using knobster it appeared as though a soft button was there because the pressed or release callback was used. Remembering that when the dial is first clicked/touched the pressed callback gets called. Knobster by its nature of being physical hardware cannot action the pressed or release callback for the rotary dial. It makes absolute sense and is just a case of understanding. I suppose more could be written on the wiki but as I implied I think it’s implicit with the names used and how the other API functions also use these names.

[Keith Baxter]

Keith,

Obvious in the sense that you need some understanding of what a callback is, what a dial is and how the API functions apply these. If you dumb it down so much you will end up with stuff like you see in product instructions to protect against stupidity. Think about in the context of dial what a pressed callback would do. The wiki currently says ‘This function will be called when the dial is being pressed.’ A Dial is a rotary device and has no button so the pressed in this context I interpret as the press of the mouse or your finger in the case of touch. Release by its name implies it gets called when you let go of the mouse click or lift your finger. Because they are useful in some instances but not absolutely needed in all cases for a dial they are optional arguments.

As I explained before to make the soft controls for everything on a knobster to control, one needs to add 2 dials and a button all co-located. In the OP’s case he omitted the button which is why the knobster only saw the 2 dials. When not using knobster it appeared as though a soft button was there because the pressed or release callback was used. Remembering that when the dial is first clicked/touched the pressed callback gets called. Knobster by its nature of being physical hardware cannot action the pressed or release callback for the rotary dial. It makes absolute sense and is just a case of understanding. I suppose more could be written on the wiki but as I implied I think it’s implicit with the names used and how the other API functions also use these names.

Yes Tony

All this is crystal clear in the API? Sorry for my sarcasm but I have a different view.

My comments were/are not intended to swing handbags, but assist others that are not so learned.

Keith