• And you're definitely on 2v13 firmware?

    Yes on 2v13.13

    as long as you do use as much of the full height of the display as you can it was ok?

    The problems with w,q,y,z are all after I descovered that using the full screen was the best strategy.

    For instance if you record your 'q' and replace it in the keyboard code and it works better, maybe >contribute it back?

    Took me a while to figure out how to do that but the comment in lib.js helped.

    /* To make your own strokes, type:
    
    Bangle.on('stroke',print)
    
    on the left of the IDE, then do a stroke and copy out the Uint8Array line
    */
    exports.getStrokes = function(cb) {
    
    

    So I did successfully manage to record a few of my q's. I was attempting to use the old PalmOs Q as much as possible. But I found just looking at the code that is printed that there can be a lot variable between one stroke and another.

    I tried the code and it did improve this and I got q's reliably BUT the printed graphic was not a good exmaple of what I feel I am tracing out, so I have not committed as think overall it makes things worse.


    1 Attachment

    • download (1).png
About

Avatar for HughB @HughB started