Have Swipe L/R/U/D and Drag L/R/U/D (+/- inversion )have some consensus among users/programmers?

hi,

i used the "swipe back to clock" app which is good,
on ANY app a left swipe will return to the clock,
from the clock i use "pattern launcher" to get to "folder launcher" or apps.
And get back to the clock again using it.

however,
in sci calcultor,
this got 3 panel for keyboard,
it used a left swipe/right swipe to choose keyboard, and leaving swipe U/D to be non-functional

1. thus i think if i have time later, i'll try modify the "swipe back to clock" to use swipe U/D 1st,
   then ADD this function to the app, with the ability to use the apps' list (always on, always off, white list, black list) etc. This approach i think is easier to me.
   
   

then I used music control,
it use Lt swipe for prev song, Rt swipe for next song, Up swipe for vol up, Dn swipe for vol dn,
which completely beat me.

1. I'll suggest let's reserve swipe (swipe is easier to program than drag, in bangle i think) for APP management more,
   and drag for things within the app. e.g. for this music control app, a Dn swipe to close it/back to clock (as in windows 10), while the drag L/R/U/D for prev, next, vol up, vol dn etc.
   
   

later i read the posts and found that some people have different meaning on up swipe, which is other people's dn swipe (inversion). would be good to consider that too.

thanks.

ps: I found this have a higher priority than the screen lock issue, so i'll work on this first.

there is also an app called "swipe back" but it let users choose number of handlers/drag which i dont understand how to.

not bad if later L/R/U/D swipe can provide close/back (indeep is a "goto" to launcher/clock), OR 1 step back

I assume left swipe : begin from "outside of Lt side of LCD" to "middle of LCD"
(or this is swipe "to right")

drag right: begin anywhere (x, y) inside LCD to "any point on Rt hand side of this (x,y) i.e. (x+dx,y)

a diagram with these actions in the API manual will be good, thx

I have no idea what you want, but in SciCalc down swipe starts the calculation.

...which just gave me the idea to bind up swipe in scicalc to undo. Might do that later.

it just made "swipe back to clock" un-usable then.

i knew that drag is harder to PROGRAMME than swipe in bangle..

so my suggestion is:

sci cal or other applictions

drag Lt/Rt for keyboard
drag up for undo?
drag dn for do calculation

then leave
down swipe for closing app/return to clock/launcher
rt swipe for 1 step backward

otherwise it 's just chaos

Adjacent to this previous conversation:
https://forum.espruino.com/conversations/388188/

Also this github issue:
https://github.com/espruino/BangleApps/issues/3048

there is also an app called "swipe back" but it let users choose number of handlers/drag which i dont understand how to.

Is it still unclear how to do this after you've read it's readme text? I can give you some tip if you elaborate on your problem and maybe the readme should be made more instructive?

I assume left swipe : begin from "outside of Left side of LCD" to "middle of LCD" (or this is swipe "to right")

Swiping from left towards the right is a right swipe.

then leave down swipe for closing app/return to clock/launcher

I'm not sure I've ever seen a device where down swipe went back?

I'm afraid this is just one of those things - different people have different ideas of how to interact, and they tend to implement this in their apps differently. We try to be open to all kinds of new apps, and don't want to impose 'UI Guidelines' that make it even more difficult for new contributors.

I don't think it makes sense to telling other app users to totally change their app because 'I installed app X and now doesn't work quite right in this case'.

For global functionality, there is Bangle.setUI. For instance we have back field, which is implemented with the button (and top left icon) normally, but if someone overrides Bangle.setUI it can be implemented with a swipe in every app instead... But not all apps do this and there are far more complex interactions which it'd be hard to handle in setUI.

yeah i did read that.

1. Gordon should take the previlege to define it clearly and write into the API reference, esp with photo/chart

2. I found the swipe in bangle is easier to program than "drag" (drag is not discussed in that previous thread). so I agree that hard to force other programmer to re-write their code to use drag.

3. however, apps like a simple sci cal could easily use up 4 swipes. My thinking now is please at least leave 1 swipe for call up the "swipe back to clock", and now i would like to

A. let "swipe back to clock" select using left swipe or R, U, D

B. borrow the secondary menu from "quick launch", so that after the 1st swipe, it pop up a menu and let you choose (back to clock, 1 step back or else). in this way, only ONE swipe is occupied by the "swipe back to clock", and the app developers still have 3 swipe and 4 drag for function.

I appreciate!
if you use it, what is the numer of handle/drag you choose?

as an end user, i only want to know this, thanks

thx for reply,
i figure out how to do so now,
as in my #9 post,
"swipe back to clock" may only need 1 swipe then will popup a menu for choices,
this may balance it.
thx

I'm not sure I've ever seen a device where down swipe went back?

win10 apps close by swiping from top to bottom, i mean .

for android, press "HOME" until the app manager appear,
then each bottom to top swipe will kill that app. something like these.

The number for me will not necessarily be the same as for you.

1. Have the Bangle show your clock face app.
   
2. Be connected to the Web IDE.
   
3. Enter Bangle["#onswipe"] and later Bangle["#ondrag"] into the Web IDE left hand field (console/terminal). Look at what you get back. Then use this from backswipes readme to determine the numbers you want:
   
   

They return undefined if no handler is active, a function if one is active, or a list of functions if multiple are active.

Use the numbers you determined for the settings for "Standard # of handlers".

hi, thx

for my bangle:

Bangle["#onswipe"]
=[
function (lr,) { ... },
function (,dir) { ... }
]
Bangle["#ondrag"]
=function (position) { ... }

so i chose noswipe to be 2, ondrag to be 1.

yet i have to say not every swipe will trigger it.
in comparision, "swipe back to clock" is more reliable on this.
may be if possible, the action part of "back swipe" should be moved to be triggered by "swipe back to clcok".

btw, seems swipe up to down is easily mixed up as drag up to down by the "desktop launcher".

thanks