Just need to finish updating HitTest and touch methods for expanded items and ContextMenu is done. Not really sure what to do w/ it design wise beyond the normal.
Personally, I don’t think the PC form factor menus work very well for touch and they look rather antiquated. I’m going for more of a smartphone feel. Could you add an option for the pop-up menus to be full screen and slide left/right as you go into submenus? I’m basically using the AppBar for this now but if I needed more than one-level menus this would be insufficient.
@ Skewworks - I got the Pacman working. Something causes it to hang up every once in a while that must be due to a Tinkr thread because it didn’t do that before. Not a problem though for demos since I’ll only play a few seconds. I had to modify the Pacman game quite a bit to allow it to offset drawing from (0,0) so that it would center in the CP7 screen. This made me think that it would be really nice if Tinkr included a Canvas control that could act as a Bitmap drawing surface and whatever was drawing on that surface would see top left as (0,0). I’m adding some graphs on top of Tinkr next and they could benefit from this also.
If possible, could you shoot me a new build tomorrow as soon as possible? I want to shoot a video and get a blog post out tomorrow night and would like to incorporate some of your latest changes. How do you create your CP7 screenshots? They don’t appear to be photos.
@ ianlee74 - it’s funny you should mention that since I spent yesterday updating the Picturebox for that purpose
My screen captures are done on an emulator. NETMF comes with a bunch of samples including an emulator which I modified to be the right size and changed it to have 3 buttons like the CP7 screen.
[quote=“Skewworks”]
@ ianlee74 - it’s funny you should mention that since I spent yesterday updating the Picturebox for that purpose :)[/quote]
Awesome!
Textboxes and VirtualKeys are about to become a whole lot faster!
Calculating the caret position inside multiline text is a pain in the butt w/ NETMF. But my new code makes giant headway. Instead of getting a fix on the caret every single time you type a character it is now done as follows:
Determine start/end characters for every line at startup
Grab initial caret position
Update X by added width every time a single character is entered and simply wrap to next line reset when X exceeds width
Update on .Text set.
Seems simple enough, but it saves a lot of cycles when typing.
Test Results:
Finds caret in–
First run: 31ms
After: 11ms