Updating my Mouse/Keyboard/Buttons/Fields routine.

[Pete]

Added full text input and right click text input popup for cut/copy/paste, etc.

See post #1. https://qb64phoenix.com/forum/showthread...3#pid31503

[bplus]

I'm getting a bunch of errors? Are you using 4.1 too? starting at 547 invalid handle and goes down the line from there, same thing, invalid handle.

[Pete]

Some editing error occurred and dropped the 3-HTML buttons out of the attached file. I re-upped them in post #1.

You can also change the Demo variable. Demo = 0 allows you to write in your own configurations. Non-zero runs the full demo.

Pete

[bplus]

OK Lucy
   

   

I am not going for 3, though Tesla might disapprove

[Pete]

Wooohooo! Got the popup shadow effect worked out nicely.

Thanks Steve for cluing me in on _SAVEIMAGE work around.

Updated in post #1.

Pete

[Pete]

What? Almost 1,700 views of this thread? Pete's gonna be really pissed if AI chat bots are using this to build gui libraries for lazy ASCII coders... and so are the lazy ASCII coders!  

Funny AI story. I asked Alexa who the starting cast was for the TV series NCIS. It got the cast members right, but it stated the main character, played by Mark Harmon, was "Jethro Bodine." Well doggies!!!!!

Anyway, if any of you none bots out there are following this, please let me know if you find any bugs. I have just a few more variables to reassign/rename and then I'll split it up into a library and start trying it out on various projects before expanding it any further. Oh, and for the hell of it, I might just also make a hardware popup version, for comparison.

Pete

[Pete]

Added a hardware popup version to the 1st post.

Now I have to decide which one I want to further develop. It won't be both, because would be a PITA.

I'm leaning towards the more compact hardware popup. It's more straight forward, no messing with changing display order, etc.

My reservation of not wanting a hardware that must except text entries may be fading. I thought a couple of days ago I might just get around that problem by making the hardware input fields 'transparent' so it would once again be good ol' screen 0 input showing through. That thought reminded me of a time in the 5th grade when this overly pedantic kid got me inspired to hire him under contract to do practically nothing for a ton of perks in return. The rub was the contract was two sheets of paper, pressed tightly together, with signing boxes cut through the top sheet. He signed. I tore off the top page, crumbled it up, and showed him the page his signature ended up on. Hmmm... I wonder if he ever learned to code, since under signed contract, on the hidden page, he's my indentured servant until the year 2030, I should really give him a ring!

Pete