Hi, I'm trying the demo to see if my Knobster could get benefit of AAO functions. It seems that I can't manage long / short click from Knobster push button. Is it something that is on your todo list, or a limitation of the Web bridge or Knobster API? Long / short click handling is a major enhancement for me, so useful in Airbus series to simulate Push/Pull on the FCU.

Thanks

34 minutes ago, roland_lfor said:

Is it something that is on your todo list, or a limitation of the Web bridge or Knobster API?

The limitation is that I don't have a Knobster... the bridge has been developed "blind" for a friend. 

The bridge is only transmitting the actual input events from the Knobster API. You would configure short and long clicks in AAO itself.

Looking at the code right now. I'm not 100% sure, but it looks like the Bridge doesn't send the BUTTON_RELEASED event.
I've changed that, but I have no way of testing it - it may interfere with existing configurations (though I don't see how).

https://www.dropbox.com/scl/fi/8ht8oh11x6w5991l25qs0/KnobsterToLorbyAaoBridge_v1_00_b08.zip?rlkey=0w1y757vhld4ymqea13k89c31&dl=0

Unfortunately the new exe process starts and closes, before showing its UI. Strangely in process explorer I see 2 of them before they close.

6 minutes ago, roland_lfor said:

Unfortunately the new exe process starts and closes, before showing its UI. Strangely in process explorer I see 2 of them before they close.

Try this download:

https://www.dropbox.com/scl/fi/8ht8oh11x6w5991l25qs0/KnobsterToLorbyAaoBridge_v1_00_b08.zip?rlkey=0w1y757vhld4ymqea13k89c31&dl=0

If that doesn't work, I'm out of ideas at the moment, sorry.

Edited December 14, 20241 yr by Lorby_SI

New exe is running, thanks. However it does not seem to send 'key up' event. I tried w/wo the option "Force <key up> event" and I don't see a different behavior.

A difference between the 2 versions:

With original bridge (1.0.7), 2 events are captured from Knobster push button: CHN: 0 EVT: 1 CLICK and CHN: 0 EVT: 1 TURN_RIGHT (on second time push during configuration). Only the second one was usable for binding.

With new bridge (1.0.8) I see only the first one: CHN: 0 EVT: 1 CLICK.

Tell me how I can help to debug furthermore.

 

I've build the KnobsterExample from Github which has another version of libknobster.dll.

Press and release events are correctly detected :

 

Edited December 15, 20241 yr by roland_lfor

57 minutes ago, roland_lfor said:

Press and release events are correctly detected :

Yes, they are detected in the Bridge too (presumably, since I can't test that myself).

Internally, the input is then mapped to a fake MIDI event, to make use of the existing AAO logic. That is probably where the Release gets lost somehow. 

Btw. the assignment process uses a different logic from the actual operation. I would expect CLICK to be the correct assignment. If you push the button again, the Add/Change Button dialog will probably interpret that as an Axis movement, so make sure to save the assignment when it says "CLICK". 

Edited December 15, 20241 yr by Lorby_SI

58 minutes ago, roland_lfor said:

Press and release events are correctly detected :

I've been running some tests now. At the moment, short/long click distinction is not possible. This is not an easy fix either, there are challenges to be solved both in the Bridge and in AAO itself. Handling key down and up separately certainly makes sense, but it will affect the other Bridge programs too - this will require a significant effort.

This is not something that can be done on short notice. It will be included in the next version of AAO, but the release of that version is not even planned at the moment.

Long story short, the way that the bridge is working at the moment, it doesn't fulfill you requirements - sorry.

 

I have to say I'm a little bit lost, as per your manual chapter 20.3, bval=0 is for release event and bval=127 for pressed. As I understand it, it's supported.

If I send http request from my browser, in AAO I have the "TURN_LEFT" key for bval=127 and "TURN_RIGHT" for bval=0.

1 hour ago, roland_lfor said:

I have to say I'm a little bit lost, as per your manual chapter 20.3, bval=0 is for release event and bval=127 for pressed. As I understand it, it's supported.

If I send http request from my browser, in AAO I have the "TURN_LEFT" key for bval=127 and "TURN_RIGHT" for bval=0.

As I wrote above, I am aware of this problem, but I can't do anything about it on short notice. This requires changes in AAO itself. Call it a bug - it just never came up, apparently nobody tried to use the API in this particular way. StreamDeck etc. aren't using this Button logic at all, they go through the direct variables, events and RPN code options of the API.

Edited December 15, 20241 yr by Lorby_SI

I spend several hours on it and I have found a (dirty?) working solution. Based on the Github example I've added the HTTP GET calls in it to build my own bridge and experiment.

Finally, I handle in this bridge the long / short click as follow:

• On pressed event I don't send anything to AAO

On release event:

• if time since pressed is < 400ms I send the pressed event to AAO
• otherwise I send released event

 

On AAO side, when I configure the Knobster push button, I can now see 3 different commands captured:

1. first push => 'CLICK'
2. second push => 'TURN RIGHT'
3. long push => 'TURN LEFT'

If I want the short click binding I use 'TURN RIGHT', for the long click I choose 'TURN LEFT'