Latest update kills Entry Mode Switcher
|
05-01-2016, 04:08 PM
(This post was last modified: 05-01-2016 04:10 PM by Tim Wessman.)
Post: #8
|
|||
|
|||
RE: Latest update kills Entry Mode Switcher
(04-26-2016 02:53 AM)jgreenb2 Wrote: Any insight into why the text no longer appears? The text no longer appears because there was never any code to ensure that the text ever would be visible. When you draw to the screen, you need to either do some sort of wait, or use the FREEZE command to avoid the next screen draw. I believe that when the inner display loop was cleaned up and improved it was now fast enough that your text basically "disappeared" due to having the next screen draw happen. Adding FREEZE will make the text stay until you do something else. WAIT can be any value - not just integers. WAIT(.3) would be completely valid. Since TEXTOUT now returns the last X position "drawn" on the text, you could possibly get unexpected behavior due to evaluating that number as a "key". So now you probably want to return a specific number such as -1 (otherwise you may get an unexpected key executed). Code: // Cycles over entry mode options. TW Although I work for HP, the views and opinions I post here are my own. |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
Latest update kills Entry Mode Switcher - jgreenb2 - 04-26-2016, 02:53 AM
RE: Latest update kills Entry Mode Switcher - StephenG1CMZ - 04-26-2016, 06:23 AM
RE: Latest update kills Entry Mode Switcher - jgreenb2 - 04-30-2016, 12:13 AM
RE: Latest update kills Entry Mode Switcher - Terje Vallestad - 04-30-2016, 10:53 AM
RE: Latest update kills Entry Mode Switcher - DrD - 04-30-2016, 09:56 AM
RE: Latest update kills Entry Mode Switcher - jgreenb2 - 05-01-2016, 02:45 AM
RE: Latest update kills Entry Mode Switcher - DrD - 05-01-2016, 10:38 AM
RE: Latest update kills Entry Mode Switcher - Tim Wessman - 05-01-2016 04:08 PM
RE: Latest update kills Entry Mode Switcher - jgreenb2 - 05-01-2016, 06:15 PM
|
User(s) browsing this thread: 1 Guest(s)