Most recent activity
-
I don't understand what Auto-open Unread Msg does. After testing with it on and off, I don't notice anything, very confusing.
Anyone feel the same way?
-
I always assumed that "double touch" was tapping twice in quick succession
Yes it is tapping fast in quick succession.
I am just stating that I also need multi touch, does bangle support that? is the controller capable of multi touch ?
But since double touch is simply 2 touch in quick succession and we have double tap implemented already, I feel like a in-built double touch based on similar concept could be nice for us.
-
Is it possible to get the double touch signal working from the
typeon.("touch") ? I can't seem to get it working.I see on search others with same touch controller also have issues with the double touch.
0xBI want to find as many unique ways of input as possible so as to prevent using button, I don't like pressing the button that much.
So i need mb multi-touch (2 fingers at once?). long press and double touch.
-
I think it would be nice to have an app on the app loader which allows paste code into it, and it packages it into an app with meta etc, so like a quick app wizard.
In case you want to create an app that does incredibly little, but still want it to function as an 'app', so other apps see it as an app.
Does this already exist? couldn't find it. I would use such an app often.
So, it uploads the code you paste in there, on to your Bangle an an app, not as a file. Its incredibly simple but very useful in my opinion.
It could also have an option to upload it as a boot app too, for people who are not familiar with concept of .boot.js files loading in every app.
Guess i am super lazy, and don't enjoy writing much meta data, I prefer default options and want a fast auto-app wizard type thing.
-
https://github.com/espruino/Espruino/commit/5be8869ae36b7d9fe955e1b1071b9f8a58a038cf
v21.124
This is the culprit, but I have no idea why, it doesn't seem like it should be the culprit. -
I can confirm it my tests:
Testing latest firmware: 2v22 17:26:55 - synced. 19:48:30 5 seconds drift. 5 seconds over 2 hour 22 mins =================================== 2v21 19:53:50 - synced. 23:24 In sync 0.5 seconds
Actually, I test it with it off, and it seem like it auto open the unread message? So it does opposite of what it says?
Well what i describe as auto open above, is the red cross and green tick screen. Mb that isn't auto open?
Auto open is when it goes into the messages app list?
In which case there seems to be some conflict of interest with this setting. Since even if you disable 'auto open of messages list', the swipe left right thing still fires. Guess i'm missing the point of it
Is is that somehow being 'inside the messages app directly' is sometimes more useful than the swipe screen(red cross, green tick)
Also the other setting named : "Disable auto open". Which is named suspicously similarly to the feature above. Completely disables the swipe screen AND the opening of the messages app. But its named the same, so it is not consistent.
EDIT: Unread Timer is also badly named. This timer is related to the swipe screen timeout.
I feel like such an important feature of the device, which is message parsing, should not be confusing to the user at all.
I found some documentation on how it works under https://banglejs.com/apps/?id=messagegui&readme .
But it would be nice if it didnt' require looking things up and was self explanatory.
So I would like "Improved naming of menu items in settings" , OR "a tooltip feature accessible directly in the settings menu to explain each setting". Could this tooltip possibly display after long press of said item?
I think the messagegui (messages ui app) , should have a nickname that is used in the setting menu, such nickname could be :
message swiper. Then any interaction with it would be understood. Whenmessages appis used it would not meanmessage swiper. Another candidate for naming could bemessage handler.