| Age | Commit message (Collapse) | Author |
|
This helps pick up any problems with the glpyh rendering.
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
This one picked up a lot of inconsistancy so the changes here are pretty
big.
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Currently wasp-os enables a narrow set of applications because we don't
want to consume RAM by importing the module and constructing the
application. We can improve on this situation by providing a small
(stateless) application that can be used to enable or diable applications.
This allows all the ROMed applications to be enabled using the GUI
without compromising on the ability to develop applications.
In fact this application significantlly reduces the RAM consumed in the
default case becasue the Self Test app does not need to maintain its
state.
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
We are able to add this to the self tests without having to create a
special page. Instead we can modify the existing notifications test
to utilize the spinner.
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Currently all lines are a single pixel wide. To draw wider lines we
must draw two parallel lines with a single pixel offset and this is
a *very* inefficient approach, espeically on ST7789 where we spend
longer setting the clipping window than we do drawing each pixel.
Fix this by constructing a line using a variable sized square rather than
a single pixel. This will "overdraw" (some pixels will be drawn more than
once) but since square blocks can be efficiently transferred to the
display the overdraw is acceptable.
Note: It is a difficult decision whether to maintain the convention that
color is the last argument or to keep compatibility with existing
line drawing tests. This patch opts for the former and fixes up
all uses within the existing codebase.
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
This is the API:
drawable.line(x1, y1, x2, y2, color)
The function has optimizations for the case of vertical or horizontal lines.
Signed-off-by: Kozova1 <mug66kk@gmail.com>
[daniel@redfelineninja.org.uk: Minor update to commit message]
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
This requires a modified version of Gadgetbridge and currently works by
implementing the BangleJS protocol.
In Gadgetbridge ensure "Sync time" is *not* set and choose "Don't pair"
when adding the PineTime device.
|
|
Measure the performance of the quarter screen fill, horizontal lines and
vertical lines.
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Currently the slider doesn't actually slide (because we process touch
events rather than swipe events) but we've called is a slider anyway.
|
|
|
|
|
|
If an application crashes let's report it on the device so it can be
distinguished from a hang (if nothing else it should mean we get better
bug reports).
|
|
From here we can also bring colour to the launcher!
|
|
|
|
It is not really the launcher itself that is immature. Rather that the
framework and UI concepts to move between applications isn't complete
yet.
|
|
As we enrich the navigation options we will increasinly need to visualize
between apps where up/down will switch us between rings and there
up/down is needed to scroll through content.
|
|
We will shortly be adding machinary to handle application errors more
gracefully. This is a useful way to force an application error!
|
|
Making callbacks optional reduces pointless boilerplate in applications.
|
|
Here the biggest changes are in the test application because we
refactor a number of the tests to make better use of the button.
Although applications may consume button events it does have a
default behavior which is to switch to the default application
(usually the clock).
|
|
After a bit of testing I have not yet come up with a fast, visually
acceptable horizontal animated effect. Instead we simply reply on
screen blanking during the redraw... meaning there is no need for an
effect hint.
|
|
As it turned out Direction was only a Direction because there were things
missing from the enumeration!
|
|
|
|
|
|
This is a big change that break compatiblity with existing applications
*and* with existing installed versions of main.py.
When upgrading it is import to update main.py:
./tools/wasptool --upload wasp/main.py
|
|
This is something of an experiment but now the app roll is traversed using
horizontal swipes and applications should primarily use vertical swipes
to navigate internally. This is mostly because if "feels" better but it
also leaves the vertical scrolling hardware available for use by the
app.
|
|
|
|
Moving it from applications into the watch is useful for two reasons.
Firstly it means applications don't need to know as much about the
display color depth and secondly it makes it easier to replace the
drawing routines with wasptool.
|
|
|
|
|
|
|
|
|