https://staging.qb64phoenix.com/showthre...66#pid9266

This thread exists because I didn't want to reply to that post, and I selfishly didn't want to post on the dedicated thread about the subject.

Good job with this project, surprised that it's as deep as it is in such a short time. Normally I don't like stunts done by clunky web browsers but this interested me. I visited the page on Github to learn about support for QB64(PE) keywords. These are just my observations.

• "COMMAND$" - not even a special "global" dialog to put in its value? Some programs depend on this, including all-uppercase return value, and it might be difficult to change away from it. Might not have to worry a lot about "COMMAND$(1)" or alike. OTOH Linux is very lame about this sometimes, limiting terminal command line to a maximum of 255 characters.
  
• "IF... THEN" - clarify that it has to be "IF (condition) THEN GOTO (linenum/label)", or "GOTO" cannot be used at all? (OK discovered below "GOTO" and labels aren't even supported.) Does this mean only block "IF" could work? No problem for me but some old programs would need extensive revision then, you know how much colons were loved back then...
  
• "LOCATE" - does this mean changing the cursor shape? Because this is a bit sad this day and age. I mean in graphics mode "druw yer own kersair for krissakes"...
  
• "OPEN FOR RANDOM AS" - this should be easy to implement one way. "TYPE... END TYPE" is supported, am I correct? It must have to do with a security issue. Entire files could be "dowloaded" which isn't as useful to me and I could never get to grips with Internet functionality in QB64PE.
  
• "SELECT CASE" - what is "EVERYCASE"? Do you mean "CASE ELSE"? Must be Visual Basic tendency.
  
• "TIMER" - a few QB64 programs will be broken because of this. So this might mean the QB64-only edition of "ON TIMER" isn't supported neither.
  
• "_MOUSEINPUT" - LOL so this is like being on a Macintosh.
  
• "_OS$" - I think this should work like in normal QB64, some programs depend on this information and don't use the preprocessor.
  

Perhaps not the greatest of keywords to start with, but that's the nature of randomness.  It is what it is, so with no further ado, here's _GREEN32 explained and showcased.

What is _GREEN32?  It's a simple command that takes a color value and returns the green component back to you from it.

When would you use it?  Basically when you have a color (perhaps taken from one of the color names), and you need to know what the green value is in it.

Example:

From the topic here -- Code fix (qb64phoenix.com) -- I was surprised to see both Dimster and OldMoses were both unaware of the INPUT$ function.  It's one of those commands that's been in the language since the beginning of time (back when cavemen used LET and such), so I just assumed everyone was familiar with it by now.  

Fool me once, as they say!

So the question then becomes, "What other keywords are folks missing out on?  And how can we help draw attention to those keywords, to make the user base aware of them?"

My solution??

Keyword of the Day!!  

Every day I'll run the little code below and TRY to write up an explanation and a few simple samples of whatever keyword the list gives me.  If it's a keyword that's already been covered, then YAYYYY -- I get a day off!!  For those that know the keyword, I encourage you to add any explanation and examples that you can with it, to showcase WHY one would use it and WHEN they would use it.  On any day which I might miss due to illness, life, or whatnot, I encourage any other user to feel free to run the code below and put up a sample for a Keyword of the Day!

Let's see how many days in a row we can go without missing one!

Hello
Please modify the code.
Normal inputs are: zero (inclusive) to 6
How to convert the code so that the option without entering digits after pressing the Enter key, T # takes the value 7.
Thank You

PRINT "Enter a digit"
K$ = "": F$ = ""
WHILE LEN(K$) < 1 AND F$ <> CHR$(13)
    F$ = ""
    WHILE F$ = "": F$ = INKEY$: _LIMIT 30: WEND
    IF F$ = CHR$(27) THEN 15
    IF F$ = CHR$(32) THEN 20
    IF F$ <> CHR$(13) THEN K$ = K$ + F$
WEND
T# = VAL(K$): PRINT T#

Looks like you're not sleeping well...

Hi,

I'm (not really) Mike Lindell.

Are you up all night posting on the Phoenix Forums and no matter what you do, you can't stop finding more and more threads to read and respond to? Well have I got a solution for you. Just visit myQB64 Official dot com, register, sign in, and in no time at all your head will smash straight into the keyboard and you'll be fast asleep. My patented lack of content (opposite of fill) will cause your thoughts to vanish and I personally guarantee you'll awaken 8 hours later, completely refreshed and ready to start your day. Just remember to log out immediately to prevent going into a coma.

QB64 dot com. Officially your best night's sleep ever!

Quick Question.

At present is there any version of QB64 that can possibly run on an ARM processor (on some OS)?

Enjoy this tiny little SCREEN 0 MOD Player that I've written entirely in QB64.

Thank you to @vince for your awesome FFT routines. You can find the good stuff here https://staging.qb64phoenix.com/showthre...05#pid2005

a740g/QB64-MOD-Player: A ProTracker (and compatible) MOD player & library written in QB64-PE (github.com)

https://github.com/a740g/QB64-MOD-Player...s/main.zip

Update:

• Add MTM (MultiTracker) format support
  
• Can play MODs and MTMs directly from https://modarchive.org/ (many thanks to @DSMan195276 for HTTP support and documentation)
  

I'm damn sure you guys have explained this once before so if anyone could point me to the thread I'd appreciate it. Can't seem to come up with the one I kind of remember that addressed this, it could be on the other site. Anyway here's the simply code

Dim a As Double
Dim b As Single
a = .12345678
Print a
b = Abs(a * 10000000)
Print a; b


So my search is to find out what happened to the 7 in the difference between variable a and variable b

Note: Windows only app. (Saving you time reading if you only have Linux or Mac.)

For fun, I thought I'd start putting together an app that let's us paste text in a small persistent QB64 window. We can then click on line of text in the window, and insert it into another document, including a QB64 IDE window. So basically I'm making a multi-use clipboard app.

For now, it's bar bones, not goof proofed, but this is why I love this section of the boards where we can share stuff in the making. This is enough for now to demonstrate the basic mechanics. A lot more needs to be added to make it really worth using.

One challenge was a difference between apps like Notepad and QB64. _SCREENPRINT can be used for non-QB64 apps, but copying to highlighted text in the QB64 IDE results in the text being replaced with a "c" and paste has similar problems. I had to use a hack to get around this and used SENDEKY Windows API sub to open the QB64 Edit Menu and select "C" or "P" to get the operations to work properly. Not all that happy with it, but at least it works, and it is nice to include the IDE in the Sam-Clip app.

So how to separate the QB64 from other apps like Notepad? Hold Ctrl  when highlighting or pasting to an app like Notepad and simple use the mouse without any key held to copy or paste in a QB64 IDE.

So to test it, try this....

1) Open Notepad and type some crap like, "Steve is brilliant." (We can so edit that later.)

2) Run Sam-Clip

3) Hold the Ctrl key and use your mouse to highlight part of the text like, "brilliant" When you release the left mouse button what you highlighted will be pasted into the Sam-Clip window.

3) Now press Enter a couple of times on notepad.

4) Next go to Sam-Clip and click on "brilliant" The text will be highlighted.

5) Go back to Notepad, hold down the Ctrl key, and left click where you want the text inserted. The word "brilliant" will be pasted into Notepad.

You can add more stuff to Sam-Clip, but for now it can't handle more than the window height. You can't same your additions yet, either.

You can bulk copy multiple lines of text to Sam-Clip, and bulk paste. .

Edit: Added Sam.clip.dat and Sam-clip.tmp database to save clipped selections.
Added ability to click where in the list to add a clipped line.

Edit: Added the ability to copy a bunch of text and keep it on Sam-Clip as a custom named [Header]. You right mouse hold on the [Header] and it will show you the contents.
Added the ability to click to highlight a [Header] and click the document. The contents of the [Header] will be paste into the document.
Added a bypass. If you hold Alt with a Sam-Clip entry highlighted, you can move about your doc and your Sam-Clip window will be grey and disengaged until you release the Alt key.

Started playing with a smooth drawing routine and a screen fading method.  Curious as to what could become of using this method.  

- Dav