thankyou :)

hi again, :)

hi, I had added documentation for flashing process..

I had adjusted linker script in firmware to add second framebuffer, and have added second framebuffer in source code.

Sorry, my English is rather bad, I was saying that for FontManager object, not SetFont() method. But as I have realized and after discussion I am sure, this feature was and is something, that is not needed, in axiom remote. But rest of the points still stand for FontManager .

1. current font, and current font height, changes according to SetFont(). In painter we need current font height, while drawing text on screen, only. But the thing is, If we look at Numeric Value Screen , Image Button, Push Button, Toggle Button, Parameter List Screen, they also require the current font's height, and when whenever we set/change the font, the current font and hence current font height changes. So, I thought the sole purpose of current font and and its dimension (height) is not just drawing text on screen, but also in calculation of other objects of firmware, infact current font and its dimension(s) is more needed outside painter, same as GetTextWidth() .

@sebastian , @BAndiT1983 I am really sorry, I called this task complete (i thought it was), I have not been confident enought to raise proper pull request, that I should have done way earlier, and I would be been having this discussion earlier, instead of jumping to another task. Please help me devise the right approach in this regard.

In T1216#17827, @sebastian wrote:

In T1216#17821, @eppisai wrote:

Hi Markus :). I have already completed this task.

@eppisai if you work on this please claim the task.
Have you commited a PR already?

I get your point, my P.R for task wasn't made,so saying task was complete would be wrong on my part. sorry.

No, I wanted to check on real board before PR,so was waiting. Had completed it last month. Will create P.R for this and Keyboard today.

Hi Markus :). I have already completed this task.

Progress So far..

hmm...I can use the knob to select the alphabets(pressing the knob) since it is being used to navigate(trial basis), and keep the enter button reserved for when the user had finished typing.

Hello!! This was till 11 January 2020, after taking your and everyone's suggestion, I am incorporating them into the keyboard. I have made quite some changes since then, like changing the underlying algo to an optimized one(using an array of char and not drawing each button individually, which bAndiT1983 had suggested), added knob control, and a few more still doing...(side buttons and up and down navigation and other things)

few points,

In T1193#17441, @BAndiT1983 wrote:

@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.

How about now? @BAndiT1983 I have just removed the tick from "on" icon svg

In T734#17428, @BAndiT1983 wrote:

@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.