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.

Please elaborate on #2

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.

1. Yes, just adjust in index.html
2. 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:

Preview of vue.js version, list is working and switching also:

• Font manager could help, but why is current font needed elsewhere than painter? Who uses it and for which reason?
  • Are you sure that current font is not belonging to some class? Was under impression that it belonged to painter before.

Utils was used to move some general stuff, but we had no time to review the architecture again, as we were trying to fix some things after GSoC2020 and discovered problems. Feel free to propose or add improvements. We can discuss anytime.

After some investigation, it seems like the problem is caused by the stack, which corrupts the heap. Probably some bloated code, e.g. wrong pointer usage or (unintentional) duplication of objects by passing them directly and not referencing.

Small correction, not all major countries, e.g. Germany uses QWERTZ.

Great! Looks much better. Please create a PR for it.

@eppisai Just take the checkbox SVG with the check mark, open in Inkscape, save it under new name for empty one and remove the check mark, then the boxes would look the same.

Jaggy edges are gone, but the outlines are still different. See the chamfered corners, one has less chamfering than the other.

There seems to be a problem with icons, as the on/off states look different.

@eppisai Was trying to answer your questions on IRC, but you weren't online. There is little reason to place a cartesian plane in the painter, as the purposes are different, it's more or less about "single responsibility". It would be better to create a base class for the graph widgets, e.g. BaseGraph, and then derive different graphs from it.

Basic diagram for visualiser communication:

Click the thumbnails to see the animations:

Tried several Gerber viewers (gerbv, Kicad and some other tools), so the problem is varying from tool to tool a bit, probably related to the format 2 of the data. Will try to adjust the header of drill layer manually and check if it helps.

I'm watching you! ;) Lame observer pattern joke, i know.

Attempt 1 which was plain output of element order, like it was stored by EAGLE:

Great, it works!

It's really not a lot of code to do and would save only the framebuffer to file. Just a nice to have feature, like we did it for OC.

Tried and getting OpenGL 2.1 in the terminal output. @panintended Can you check it? No profile worked for me yet, but the order is certainly important.

Reference:

Great analysis, thanks. Would check it with the Ubuntu VM. Do you have a fork with a fix for testing?

Found the link which contains the code i've used for generation of linearization array: https://jared.geek.nz/2013/feb/linear-led-pwm

Fixed debug painter, now it is done through strategy pattern.

Automatic fallback through two phase init is probably fit for most machines:

Structure is added, next step is side bar implementation. Here the ButtonBar can be used, like the example which is already added, just in combination with the ImageButton.

We've discussed it and this is a workaround, but we need a proper fix, as i fear that future extensions will add more problems. Still debugging and thinking how to resolve.

Hardware looks fine, my output for Intel:

Can you post the output from 'glxinfo | grep OpenGL', please?

Interesting, cannot observe such behaviour on my machine. It has 2 GPUs, Intel and nVidia. Both work, for nVidia i start the app with 'prime-run'.

Please check latest commit in the repo, it has a debug overlay now, which currently is only implemented for DrawText() and DrawIcon():

No, add implementation, by porting from old firmware version and re-using the DrawIcon() code to reduce image size.
The base class needs some additional love to be able to set this buttons from the child class comfortably.