Aug 23 2021
Jul 29 2021
Jul 27 2021
Jul 26 2021
Jul 25 2021
Jul 20 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 1 2021
May 28 2021
May 27 2021
May 19 2021
Apr 25 2021
Apr 24 2021
Mar 29 2021
Mar 28 2021
Hello, I've started working on this.
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 .
I see there might be some confusion about the SetFont() usage. The purpose is not to allow a user to select the general size of fonts used in the remote (like operating systems let you set larger fonts that are easier to read for all software). The purpose is to allow drawing headers in a larger font than normal menu text for example.
- 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() .
- 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.
@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 23 2021
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.
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.
Well then, great :)
My question about namespace utils still remains though, is the plan to move all the utility functions into it,
or is there some rationale behind whether a function ends up there or in the global one?
Hi Markus :). I have already completed this task.
Hello, I started looking into this.
Due to my lack of familiarity with the codebase, I have a few questions:
Mar 21 2021
Mar 20 2021
I created a pull request for this: https://github.com/apertus-open-source-cinema/AXIOM-Remote/pull/32