OK, that's a little tricky. it's not just ANY loop, if you have an inkey$ loop, I have to put it there. Had it in the main loop and it did nothing.

THIS I know. I need a function/sub to run if they click the "x" (and not a "Q"uit option )

However, it will NOT run a sub or function if a user clicks the "x" on the terminal window. the terminal window will just stop.

For example clicking the red "x" in firefox, it will run some cleanup and delete cookies etc...

a qb64 window will just exit/end

edit: I know the title is confusing but there was not a better way to write that
I need the "exit/end" to RUN a sub/function

No, I have not released the source code for this yet (still messy) I started to work off the older source, however, there were so many changes I wanted to make, I threw it in the proverbial trashcan and (once again) started from scratch.

TL-V is my fav. Everything works as I wanted. Search by name, next/prev page works on larger collections, uses an external ini file that is much more organized (need dos commands that work internal of QB64 instead of shell - just askin :-P), much cleaner execution. and several other improvements over the older one.
Hats off to SPRIGGYSPRIG for his clever string.split and SMcNiel for his best solution to an "IsNum()"  function

If I get enough requests, I'll put the source up as is. (its messy, almost done cleaning it). Currently MUCH MUCH smaller at 450+ lines of code, and some external files as well.

edit: forgot to add a download :-)

mediafire

https://www.mediafire.com/folder/26w77pfe4s4lr/releases

So if I do

c:\> dir /b /a-d "drive:\path\to\roms\snes\" *.iso,*.bin
it says:
the system cannoot find the file specified, and then lists ALL the files in the folder.

However, If I do this in the same drive, no errors, and it lists the two extensions requested.

Unless I forgot how my dos stuff works LOL - VERY possible.

wish list, get dir$ working so it can do this :-)

(or does it)

so working on my emu launcher. and found an interesting quirk (wont call it a bug)

dir /b /a-d drive:\path\to\folder\ *.bin,*.iso

The above works perfect from the command prompt as intended. Just the bin and iso files show
howeeevvver


gives me ALL the files in the folder. which is what I don't want. Is this a goofy characteristic with QB64?

Name is a keyword in QB64 like Print. Add or subtract a letter or more for variable name.

O ya,, knew that. I tried _name but that didnt work either. so using nname, but I saw in @Cobalt had a good idea, and used "nam" not bad. will prob switch to that

thanks @Cobalt

thanks for the replies

You are correct, it is good practice to init all vars, arrays, and udt, however, is a special case for me.
I was so fascinated by the "ON TIMER(x)" feature.
I am in the process of converting a clicker JS game to QB64, and have almost 500 lines of UDT. 

Here is what I was able to convert so far - goes pretty smooth. May not be the correct way. but it works



And I believe @Cobalt is correct - UDT fixed strings usually hold junk
Also, anyone have an idea how to use "name" in a UDT that doesnt produce an error?

when initializing an array and type vars - do they start with empty strings or integers ?



I'm tinkering with a program but have tons of arrays and type vars, and just realized that I may have to do the famous loop to zero stuff out.
Do I still need to do that?

example

do these start off as zero for the var1 and empty string for the var2?