VKB-SIM

My Goal: Mini stick returns BOTH axis and button presses, and the mini stick press is just an ordinary button (not toggle or shift).
Basically I want the mini stick to behave in both modes at the same time and let me use the press as button instead of toggle.

I think the way to achieve this is:
1) Disable the 'ustick' toggle button, set to normal button
2) Configure axes 5,6 as 2 buttons each via the axis2button dialog
EDIT: I now see I can configure the existing POV behavior directly without axis2buttons, however I'd still like to know what is wrong with my attempt below for further customization.

However no success for axis to button. I have been reading the njoy manual and searching the web and forums.

I've tried these two things with some results. Almost every other combination produces no result at all.
1. 'Range' Num: 0-4 produces a single held button press at the maximum limit only. Close, but where's the other side?
2. 'Edges2' Num: 2 produces a instant momentary button press when moving in either direction. Close, but I want it held while in range.

Stick: Kosmosima on NXT

Similar posts:
How to add 2 Buttons to 1 axis via Zones?
viewtopic.php?f=28&t=4598

EDIT: I've actually just realized I can achieve the result I want by 'POVs' tab, setting Active to 'Always'.
I'd still like to know how to configure custom buttons via range though.

"the mini stick press is just an ordinary button"

I'm only focusing on this part as I solved this by changing to "Tempo B" and checking the 'start in HAT mode' or whatever. Pressing down normally presses a button that is specified, holding switches between HAT and analog functions.

Edit: Under POVs you could switch "Active" from on/off to always maybe and that would hit all points combined with the above?

Thanks for replying Lobstar. I did try the Temp setting. That allows long press so it could also be used as button, but I wanted to completely remove the switching mode. I ended up doing your second suggestion which was to set both modes as always active. That meets all my needs, but I still would like to know why the axis2button config didn't behave as expected and documented.