QB64.org Forum
Active Forums => QB64 Discussion => Topic started by: Cobalt on November 27, 2019, 11:03:07 am
-
have a program up,(the program I am using has no subs or functions yet)
using the mouse, to 'scroll' means to move the mouse along the menu bar.
click on "Options"
scroll over the menu bar to "View"
click on "line numbers"
scroll back to "options"
click "display"
pops up the SUBs listing not the Display menu.
may be other ways to do it, but it does it every time for me following that order.
Ver 1.3 [stable] 96937f0
-
Hehe, that’s hilarious. I’ll check it out, thanks for reporting! 😂
-
I tried it, it works right for me.
-
I tried it, it works right for me.
what I'm getting.
-
Works fine for me too, but using the latest development build. Actually, the development build just before the latest, but with Steve's updated qb64.bas installed, and qb64 recompiled. I tried several times to see if it misbehaves, but it did not.
-
Works fine for me too, but using the latest development build. Actually, the development build just before the latest, but with Steve's updated qb64.bas installed, and qb64 recompiled. I tried several times to see if it misbehaves, but it did not.
Then you basically have the latest development build. Only other thing I pushed was a change to libqb so _PUTIMAGE will work with the SOURCE and DEST being the same. No need to toss an error there.
-
I reproduced the issue on my machine, I’ll fix it soon. Again, thanks for the report.
-
Yes, I was able to see what Cobalt was talking about, kind of complex but I can guess what is going wrong.
vers 1.3 stable
I can't imagine Steve fixing this glitch in dev version without mentioning it. ;)
-
I got it on QB64x64 Version 1.3 Revision [Stable] from git 96937f0
Fine!
-
These are the exact steps I used, to see if the problem exists in the latest development build.
1. I selected a program I had written, which contains no subroutines.
2. Using the mousepad, in my case, on this one PC, scrolled along the menu bar, starting with "options."
3. click on "Options."
4. Then, scrolled over the menu bar to "View," where line numbers had not previously been selected.
5. Then select "line numbers."
6. Then scroll back to "options."
7. Click "display."
What I reliably get is indeed, the options for display settings, not the F2 list of subs (which don't exist in this program, as they did not exist in the original statement of the bug).
Is the difference that I'm using a mousepad rather than an actual mouse, or are these steps not otherwise identical to the original description, or is it that the latest development build does not exhibit this bug?
-
It seems to me that
first we choose "Option"
then we choose "View" by scrolling mouse on the menu
then we choose "File Number" by click on it otherwise we got no glitch!
then we scroll to "Option" without enlight the "Subs" voice menu
now clicking on Display we get the result of SUBs screen display.
Some news:
1.
you can get this also with no program loaded into IDE
2.
if you try you can get the same glitch scrolling on "Search" and click on "Find..."
moreover if you are able to click on "Change..." you can get this!
[ This attachment cannot be displayed inline in 'Print Page' view ]
3.
But as Bert22306 says
you must be fast or direct to click on the voice of menu without highlighting the other voices near.
I can imagine that the index of command of menu are waiting a selection after click on Line Numer but scrolling back with no selection we leave void the variable of menuselected... void = 0 so in a system with base index 0 and no reset of menu voice during scrolling after click on "Display..." or on "Search..." the IDE executes the first command of "View..." menu indeed "SUBs...F2"
Thanks
-
Hot mess, hot mess. I’ll get into it it all, guys.
Now, if you all could stop procrastinating and playing with our menu bar, that’d be great. 🤣
-
sorry Fellippe, did not mean to start something.
-
As long as we’re all nit-picking over quirks in the IDE, can you take a moment to look at the coloring routines?
PRINT 1.18E+1000
This prints RED, then WHITE, then WHITE to the + sign, with the 1000 being RED... As you type code, and the error checker does its thing each keypress, that number flickers over and over, uncertain what the heck to color itself. It’s distracting as can be, drawing eyes towards it, making the user (me, at least) get lost with what they were doing and causing extra typos in the code.
If we can’t have it auto-color itself properly, can we get an option to disable custom colors completely for numbers? Or is there some simple trick I’ve overlooked to choose a character color which won’t flicker? (Perhaps set the color white, as that’s what it seems to try and revert back to? I’ll have to try that later..)
Just thought I’d mention it, since you’re going to be digging around in the IDE soon, anyway. ;)
-
Yeah, the issue here is that figuring out it's a number in scientific notation is a pain. What you see flickering is the syntax highlighter believing it found a number, then doubting itself and thinking it's an expression, then back and again. I'll try to figure it out this time.
You can always bypass number highlighting though:
[ This attachment cannot be displayed inline in 'Print Page' view ]
Just make the number color the same as the normal text color.
-
Sorry for more feedback!
Stop in this moment. :-)