I was chasing down a bug for a few days, when I came across this little gem. I rewrote some code a few times to figure this one out.
It took me a little time to see it, but everything made sense afterwards.
In case you can't see the image, I will explain.
I am comparing two calendar day numbers, 1 through 365/6. If today's date is similar or greater than the listed date, specific code was to fire to shift data in arrays. I noticed that when I selected <= or >= in the drop down of integer comparison block, it would insert the opposite of what I selected. (The image is worth a thousand words. The image shows that >= was previously selected, but the context menu shows that <= is actively operational)
After I fixed this by selecting the opposite of what I needed the program worked as it should.
I don't think I have any funny setup. I basically use AI2 out of the box.
It's the first time I have ever noticed this, and any other time, the code worked, proving that this one time is an anomaly. I will keep my eye on it. I am not concerned.
I extracted a new block, and it does the same thing.
And in a different project altogether...
Curiously, enabling OpenDyslexic...
Evidently, logic follows the chosen equation rather than what is displayed.
Do you have any local browser styles or plugins that manipulate the style settings? If it draws correctly with the open dyslexic font turned on but not without, then it might be that something is overriding our default font and causing the issue.
I double checked the code and we are definitely using the right Unicode characters for ≤ and ≥, so it's not clear why it would be drawing one direction in one context but not another.
Android 11, I believe on a Acer chromebook. chrome OS Version 123.0.6312.112 (Official Build) (64-bit)
Using the default Chomebook font, NOT customized.
And therein lies the issue. I did not enter a >= in the code, I entered <=.
As the picture shows, it renders >=. If you run the program with numbers according to the text box names (low.number , high.number), the result is opposite from what the button says, no?
No, there aren't any wonky settings. This thing with the <= & >= reversing is the only thing that happens.
I can live with it, but need to double check it all the time, or just shift the sentinel up or down one and use < or > instead.
Looking at your posting of the code, the comparison has corrected itself. On my screen it shows >=, but in actuality calculates <=.
Thus, running the program on my chrome book, if I enter 10 in the first box, 100 in the second box, and click on the button, the result will be "true", where according to the text, it should be "false"
