Why does this happen?   



when this is the code?

all the cool kids are doing it so why not?

A simple gui example to demonstrate a scheme for button handling and menu selection.
This makes use of a couple of the new dialog controls in version 3.4

Menu selections return input from the selection, there's a little but of button manipulation shown, you cna quit from a menu or the big red quit button. Menu2 uses the new dialog controls, the hello menu selection wlil have a different message if the user has enters a username.

This is fairly barebones and hopefully straightforward enough someone may find this useful.

A quick little routine to tell you if a string is a number, or not.

BTW: at the end of the song, or after you stop the song, you'll have the option to play the song again.  Choose "Y", and then you can alter the tempo of the song and the waveform applied to the sounds.

• View the source code
  
• Run the program
  

Hey if you like borderless windows but want a way to resize them forget about using $RESIZE. It has no border to grab on to. Oh, if you don't mind ugly, or want an all black window, you can add a WS_THICKBORDER element to your API call, which Steve discovered, but it's ugly. (It leaves a thin black row just below the top white border in any window that has a colored background.) Anyway, if you don't mind that, you can use it with QB64 $RESIZE. If you want an alternative to $RESIZE, try something like this...

Try a mouse drag at any side or any corner to enlarge or shrink the borderless window. Esc to quit.

Finally everything works properly. A system that can be easily extended from non-source code. I created a structure that allows us to parameterize everything with a simple notepad. Add new maps, terrain, and textures quickly.
I want to make a game that I haven't made before. I deleted the shooting part. There is already such a game. An adventure game with missions and characters would be nice. If you have any ideas, I'd love to read them. even if it seems funny at first. I'm interested in any ideas! moreover, if we could collectively build a game in some form, where more people could take part, that would be wonderful.
It can be tried for now. there is no task, but you can walk around the huge space. There is a lot of garbage among the files, that's why it was 240 Mb, so sorry!


download:
https://drive.google.com/file/d/1yWJ4S9h...sp=sharing

FYI

_printimage first code set throws a syntax error on line 24
_PRINTIMAGE - QB64 Phoenix Edition Wiki



Changed the offending line from:
_PUTIMAGE Page&, Prev&

To:
_PUTIMAGE (0, 0), Page&, Prev&

And all good!

Not sure what I really can do as a report printer to file. Does QB64 have any functions that deal with formatting text to file? I poked around the board and the wiki and haven't really found anything. Any thoughts or leads? Ideally, I would like to center lines on a page (without having to manually space things), maybe some font or styles. Do we have any support for RTF (or PDF, if I may be bold  ) in QB64 itself or a library that we can use?

Any help would be appreciative, other than report output. The student database is up and running. It is time to start thinking about the gradebook side as well!

Thanks y'a11!

Making my way through this game, thought I'd share what I have done so far.

For those not familiar, it's an old arcade game from 1981.   The idea is to fill in 75% of the screen to complete a level.   (So far no scores yet, and unlimited lives)

Still some things missing (like those sparks) and there are some bugs to sort out.   No sound either - not sure how I'll do that because the original game had bad sound effects.

One thing I'd like to do eventually is learn a flood fill algorithm.   I struggled with that and decided to just use paint for now.   Flood fill in this case was more complicated than I was expecting it to be.   But it'd be nice to do it like the original game does.