Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
DAY 021: LOCATE
#3
"Try doing that with LOCATE," said a mini-mod of the oldest forum. Now I'm trying to think about why he said it...

OK I'm giving the game away. I shared a game program that I wrote on QuickBASIC, kept it at the "tiny" 320x200 but it was mostly text mode anyway. The time hasn't arrived yet where I tell you what was my username in Galleon's forum and other things about it.

Hmmm did some of you look for "Discussion" posts in the large number of pages of the old QB64 Wiki? Some of it was entertaining, very surprising coming in one half from somebody who later became very important...

Umm, erm, ahh... the third parameter of "LOCATE" is more useful now in Freebasic than in QB64, because the other programming system takes up the terminal that an user program is run in, assuming it's not a "GUI" program. Not like QB64 "SCREEN 0" nor like "$CONSOLE:ONLY" mode. A few people would request the fourth and fifth parameters honored only to keep freaking out at the moving hamburger...

(12-02-2022, 05:41 AM)SMcNeill Wrote: And that's basically the difference in LOCATE with a graphical environment, verses a SCREEN 0 environment.  In SCREEN 0, one doesn't have to worry about how locate acts with variable width fonts, as they're simply not allowed in screen 0 to begin with.

It's only in graphic modes, and with non-monospaced fonts, that one has to remember that LOCATE works by ROW, PIXEL.  In all other cases, it work via ROW, COLUMN.
Arrow Maybe I should spend far more time reading the wise people than babbling.
Reply


Messages In This Thread
DAY 021: LOCATE - by Pete - 12-02-2022, 04:50 AM
RE: DAY 021: LOCATE - by SMcNeill - 12-02-2022, 05:41 AM
RE: DAY 021: LOCATE - by mnrvovrfc - 12-02-2022, 08:27 AM



Users browsing this thread: 2 Guest(s)