GET parameter is id matching the JSON file
Tue, Oct 12
Mon, Oct 4
Unless there are actual usecases for a VPN something simpler like a pure terminal sharing solution seems better for support purposes to me.
Thu, Sep 30
Mon, Sep 27
Sun, Sep 26
Aug 27 2021
yes, please close this task.
yes, please close this task
Aug 26 2021
hi again, :)
hi, I had added documentation for flashing process..
Aug 23 2021
Aug 5 2021
Jul 29 2021
Jul 27 2021
Jul 26 2021
Jul 25 2021
Jul 20 2021
Jul 18 2021
Jun 20 2021
Great progress and discovery!
Looked at code, memory usage report and disassembly, seems like CentralDB and related classes are pretty heavy here and there, could also be the cause for the crashes on stack and heap collision.
Jun 12 2021
I had adjusted linker script in firmware to add second framebuffer, and have added second framebuffer in source code.
Please elaborate on #2
please create PR for code review.
I see there is a branch already, please look through it if anything is still to be cleaned up/improved, then please create a PR so code review and merge can follow.
Move this to separate branch if not done already, create PR.
adjust linker script to add second framebuffer, look at first framebuffer there as reference
add second frame buffer in source code
Give us an update about the codes current state & issues
Please clean up the keyboard code and create a PR for this branch, then code review will follow and ultimately end in a merge.
Jun 1 2021
May 31 2021
May 29 2021
May 28 2021
May 27 2021
@BAndiT1983 did it
May 26 2021
Do you work with a camera target object currently? If yes you could simply prevent that from going below 0
May 25 2021
We can use same JSON approach which was described for the camera position, as ID we can use the one we set in our parts JSON.
- Yes, just adjust in index.html
- Yes, favicon.ico is the one, just replace existing file
Rotation is restricted, but panning needs additional research.
Already implemented, it works when parts are switched, but needs a small fix when the page re-/loads
Maybe we can encode JSON with base64 in URL query params:
we went with option 3