bastard wrote:Hi,as I'm not sure which firmware I want to use or modify I've done a comparison between them. I hope I got all features. If not, please give me some input - I'll put it in asap.
jsgf wrote:And you scooped me on drift correction! I only *just* committed that, and haven't announced it at all yet!
jsgf wrote:One thing I'd mention - and admittedly because I'm biased from having spent some time implementing it - is display transitions. Aside from looking pretty, I find they do actually help give a cue as to what just happened when you pressed the button without having to read the display... And if the shape of '9' is worth mentioning, then this is
bastard wrote:I agree, but do not fully understand. So I make you a "notes" field. What would you have to be in there? Please give me your words.
DigiSage wrote:I have no trouble building / flashing my firmware with the MacOS X avr packages.
jone wrote:Adding "--param inline-call-cost=2" to the compiler options reduces the size of DigiSage firmware
jone wrote:Adding "--param inline-call-cost=2" to the compiler options reduces the size of DigiSage firmware as follows --
Hope this helps someone out.
Eggplant! wrote:I'm not sure if the board software allows this, but I'd prefer an HTML table over an embedded image if possible. That way you can add things like links to the forum topics or web sites, be able to copy/paste information, etc.
Users browsing this forum: No registered users and 2 guests