- User Since
- Oct 15 2020, 8:10 AM (67 w, 1 d)
- Nickname on IRC
Aug 27 2021
Aug 26 2021
hi again, :)
hi, I had added documentation for flashing process..
Jul 27 2021
Jul 18 2021
Jun 12 2021
I had adjusted linker script in firmware to add second framebuffer, and have added second framebuffer in source code.
Jun 1 2021
May 27 2021
May 19 2021
Mar 25 2021
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 .
- 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.
Mar 22 2021
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.
Feb 8 2021
Jan 18 2021
Progress So far..
Jan 17 2021
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)
In the above the keyboard is not yet QWERTY,will be making it proper QWERTY
I'll be finished by tomorrow before the IRC meet I think, so will also update last week's proper progress!
Jan 5 2021
Jan 4 2021
How about now? @BAndiT1983 I have just removed the tick from "on" icon svg