QBJS v0.9.0 - Release

[dbox]

Keep in mind, Timer by itself is going to have issues.  If you're looking for better precision, use Timer(0.001).

Ah yes, good tip.

[bplus]

Maybe that Timer point would fix my issue on my system, I will check.

[SMcNeill]

Maybe that Timer point would fix my issue on my system, I will check.

If it's an issue with timing and _DELAY, I wouldn't think so.  I didn't actually change the delay any in the code before.  All Timer(0.001) does is try and return a more accurate version of the time for you to store in your variable; it's not changing that _DELAY difference at all.

[bplus]

@Smcneill No a Timer was being used in place of a Delay so as not to interrupt the smoothness of execution in the Play Demo of PLAY. You can see where the issue comes up in that thread.
Reply #9 https://qb64phoenix.com/forum/showthread...7#pid31387
It's the old clearing of a mousebutton down problem without missing the next.

Honestly I am not getting it, but dbox says its better that way. It's dbox way. It works.

I know Steve has a way, Pete has a way, Old Moses has a way, even bplus has a way but he can never remember it when writing code on the fly. Delay .25 works well enough for him.

[Pete]

@bplus Pete's way is being expanded. https://qb64phoenix.com/forum/showthread.php?tid=3402

I'm switching the keyboard portion over to _keyhit.

I love how you defend how the _delay part works for you. Now do this. Step 1, get married. Step 2, open an office and write software to run it. Step 3) have your wife use your software to run your office.

Oh, there's more...

Step 4) Hire a really hot divorce lawyer. Step 5) Divorce your current wife. Step 6) Marry your attorney to get your money back.

@SpriggsySpriggs knows I'm 7/8ths kidding. The other part is all about the Benjamins. 

Okay, fine. I really am kidding about the divorce part. What really happened is my wife would come up with what I later realized were great suggestions for the programs, and I would finally implement them upon reentry. No Steve, I'm talking about blowing up into outer space, not what you're thinking about! I mean I'd hear her describe, in about 10 words or less, what she wanted the program to do, and then I had to explain to her that would take a week or more to code and dammit, I already had a tee time on the books! Anyway, truth be told, I'd rather cut off both arms than leave my wife, of course if she left me after that move, I'd be really screwed. No Steve... because I wouldn't be able to type code anymore. Geeze!!!! @SMcNeill

Pete

[bplus]

LOL that Pete!

I sorta had that experience without the wife. I made up some data base code and data entery forms for business I was working at. Their 386(? was it) was jammed packed with a data base whose record structure wasted tons of room. I want to brag about more of this but long story short the secretary who had to use the thing for tons and tons of inventory slips had several good suggestions on how to improve data entry form. Very Positive experience nothing to get divorced about.

Now what does all this have to do with QBJS? you may ask.

Well we all wished back then we had something that did not have to have Windows and definitely did not have overly priced IBM consultants to tell you how to run your business on their overly priced IBM sysytem. Its enough to make you learn coding for yourself.

QBJS is the answer to those wishes.

[dbox]

Maintenance release 0.9.1 is now live with the following fixes:

• PLAY was not correctly extending the note duration when "." was encountered. (#126)
  
• Updated _FileExists to correctly return status of files from relative URLs. (#118)
  
• Updated _LoadFont to correctly load font resources from relative URLs. (#118)
  
• Updated Str$ to correctly include a space before a positive number. (#123)
  

Thanks to everyone who reported bugs.  In particular, @bplus and @a740g, this release should fix the issues you reported for Str$ formatting and PLAY, respectively.