Create a reference to the directory containing the programs you want to run. Since the programs aren't in the default search path – which is the current directory and its ancestors all the way to HOME – you'll have to create a PATH list in HOME. It looks like the Linux version may benefit from this type of surgery as well. In addition, I uploaded Plus42 test builds here. The improved display update code for Windows will be in Free42 3.0.12 and Plus42 1.0.1. I made this change in Free42 and verified that, instead of being 2x slower than 3.0.10, it is now 5x faster, despite still using GDI+. Which is what the Android, iOS, and MacOS versions do as well. This is really inefficient, because the human eye can't keep up with that kind of frame rate anyway, and it makes more sense to put a limit on the number of repaint operations per second, and allow program execution to hog the CPU the rest of the time. There is actually a deeper issue with Free42 and Plus42 for Windows: they paint the display immediately, whenever the core updates it. And the GDI+ bitmap render apparently takes twice as long. This is because of how the display is drawn on the screen: 3.0.10 did this using GDI, BitBlt() to be precise, but 3.0.11 uses GDI+, in order to support non-integral display scales. It was pointed out to me that Free42 3.0.11 for Windows is a lot slower than 3.0.10 when running display-intensive programs. (Which is another feature that has turned out to be a lot easier on iOS than Android, but I digress.) So, no, not related to proper alpha keyboards. I got it to work in the iOS version, but in the Android version, it was a disaster. And in Free42 for Android and iOS, I tried to implement n-key rollover for the touchscreen. Early keyboards sometimes had only 2-key rollover, or no rollover at all. The n in n-key rollover means that the keyboard will allow pressing arbitrarily many keys without dropping keystrokes. Without this, you start to get dropped or out-of-order key events when users are typing quickly. As in: press A, press B, release A, release B: in that sequence of key events, you want both A and B to be recognized as typed characters, even though B was pressed before A was released. Rollover refers to the behavior of electronic keyboards that allow multiple keys to be down at the same time. (05-02-2022 09:49 AM)jonmoore Wrote: But what's n-key typing? Is this similar to my request for a proper alpha keyboard? In a nutshell, the UI structure in my apps is not the way iOS apps are really supposed to be structured (Free42 is my first iOS app, I didn't know any better.), and while I have been able to get away with that on the various iPhones and iPod touches, it starts to cause real problems when trying to support the iPad properly. I think I'll get those features essentially for free when I turn on iPad targeting in the Xcode project settings, but there are some issues having to do with the Free42/Plus42 views are managed. What the iOS version does with sliding sideways is not the same thing as Slide Over on the iPad, I think, and there's also Split View. Thanks for highlighting this as I probably would have missed it. Here's a version in Swift that has a +/- button and also a Clear and Done button for the numeric keyboard.(05-02-2022 09:49 AM)jonmoore Wrote: Slide-over views are a classic iOS UX pattern and perfect for the print view on Plus42.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |