Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

msgtwscr: Temporarily activate scroll on twist function when a new message triggers the message app. #3714

Draft
wants to merge 135 commits into
base: master
Choose a base branch
from

Conversation

thyttan
Copy link
Collaborator

@thyttan thyttan commented Jan 11, 2025

Can be installed from my app loader: https://thyttan.github.io/BangleApps/?id=msgtwscr

Temporarily activate scroll on twist function when a new message triggers the message app.
yogsoy and others added 30 commits February 15, 2025 03:21
sets width to 0 and checks inside the draw function rather than
leaving them undefined
Fixes a bug in the dot coloring and adds more screenshots
I didn't realize it would choke on further dots in the versioning.
…e to gb instead of play; allow widget clicks
Discovered that, in the events synchronized from Gadgetbridge, all-day events
have timestamps that disregard local timezones.  Specifically, all-day events
always start at midnight UTC, which caused calendar to display them starting at
a different time depending on time zone offset (e.g. for my offset of -5, I see
all-day events start at 19:00 the day before).  Borrowed logic from the agenda
app to correct this.  This logic shifts an all-day event's start time to start
at midnight in the current time zone.

Also specify all-day events as type "o" (other) so the full day is highlighted
and the start time is not displayed.

Note that this does nothing to handle all-day events that span more than one
day (only the first day is highlighted in the calendar).  Also note that I'm
not sure how this will handle time zone changes, like shifting to/from daylight
savings time.
Commented out the utility functions and variables used to make documentation. Seems like there should be a better approach, maybe an extra dev.js?
Maybe implement this in a separate app instead.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.