(04-17-2023, 10:08 AM)mnrvovrfc Wrote:(04-17-2023, 01:50 AM)TerryRitchie Wrote: Let's hope that never gets incorporated into QB64. I can't stand them in text messages. In my code? No thank you.
This was said decisively enough for me.
BTW I caught someone else in another forum using your signature.
(04-17-2023, 03:45 AM)CharlieJV Wrote: That's a disappointing reply considering my intent/hope.
Don't look at things at a negative aspect. QB64(PE) doesn't have certain abilities that BASIC Anywhere Machine and QBJS have, as you and dbox keep demonstrating. An user could choose one or the other depending on his/her needs.
I admit, syntax coloring was something I would have still resisted today, although it could be helpful. It's because almost all editors that do it could go overboard with someone else's settings. One would then have to make adjustments to configuration when he/she would rather write source code! When I first saw syntax coloring in Turbo C++ way back in the day, I felt my copy of Turbo Pascal v6 was rather old. My copy was actually only a couple of years off. But it's because I barely made any use of it and it was my fault.
Another thing about editors these days is that dumbass highlight of the "current" line the edit cursor is on. That drives me nuts! At least the QB64 IDE has an option to disable it, but with editors like Kate it's not that easy, must take the trouble with configuration to set it the same as the general background color. (facepalm)
The only thing BASIC Anywhere Machine in any of this: it allows me to try things out and see how it helps me.
I was hoping this thread would not be about QB64pe or BASIC Anywhere Machine, but would be about discussing things that can be done in general to accommodate folk with disabilities.
Do I ever regret thinking folk here might have some useful insights or any curiosity about it. EFF it.