(02-12-2026, 07:05 PM)bplus Wrote: @dbox once again QBJS does not like something that works perfectly in QB64...I can tell I've disappointed you @bplus, and I'm sorry.
QBJS has no screen 0. BTW _MouseX and _MouseY in screen 0 of QB64 does char cells not pixels, same with QBJS. Otherwise I dont know why the codes perfectly in QB64 but not QBJS????
...the point of all my labors today was todo mouse clicks!
The main issue was that the tight loop in the GetMove$ method was not giving enough time for UI events to be processed. This can be remedied by adding a _Limit before the end of the loop.
The _MouseX and _MouseY returning character coordinates instead of pixel coordinates is an oversight on my part. I tend to mostly work in graphics mode myself. I'll add a fix for that in the next release. In the meantime, it can be worked around by just dividing the mouse position by the font size.
Quote:BTW I had to Dim all my variables in the function GetMove$ to get it accepted by QBJS. I thought you fixed all that!I'm pretty sure this was because of Option Explicit. As you can see below the Dims are not necessary.
Here's version of your test program that might be a bit closer to what you were wanting:
(02-12-2026, 07:25 PM)TempodiBasic Wrote: Ok @DboxI will accept it.
it can be a interesting exercise doing a TUI for this engine, but you must accept that its max force is about 1000Elo (IMHO);


