 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : Testing for VGA/HDMI/LCD etc. recommended approach
| Author | Message | ||||
| matherp Guru  Joined: 11/12/2012 Location: United KingdomPosts: 12066 |
Please could I make a request in your own interests. Lots of programs you are writing can run on both LCD and VGA/HDMI variants. Using mm.device$ for this is becoming increasingly difficult as there are so many. Unless anyone can point out a reason why this is a bad idea please can I suggest using if instr(mm.info(lcdpanel),"MODE") then VGA/HDMI else LCD/NONE This is, or will be in all my current MMBasic variants. Only if you then need to drill down further or you have platform specific variants should it be necessary to go beyond this. For HDMI/VGA variants it, obviously, returns the current display mode MODE1, MODE2, .... For LCD variants it returns the name of the display as in option list or NONE if there is no display configured |
||||
Volhout Guru Joined: 05/03/2018 Location: NetherlandsPosts: 6198 |
I think that is a good idea. In the past I have focussed on VGA + keyboard, versus GameMite, since most programs need Some kind of user input, and the keys on GameMite where defined. But now there is much more variety. In new programs, or new Ports, I will use this method, but as mentioned above, part of the reason for using platform, is the input method. Volhout P.s. Despite this good suggestion, it may be a good idea to limit the number of HW variants. PC3 is a good move in that direction. Edited 2026-10-25 02:45 by Volhout PicomiteVGA PETSCII ROBOTS |
||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2026 |
