Thank you, Jeff. When I see things like /= for not equal, I can imagine the person who thought that up never had to diagnose someone's 10-year-old, undocumented code. It's real easy to make a typo with just /=; while .NE. is more deliberate and "reads" easier. Sure, one can play games with "How few statements/characters can be used to get this done?" but in real life, it's more often, "How fast can you find this error?" And we don't have to live in 32K partitions anymore. Not say'n we should go back to COBOL, but clarity does count.
Just for your tech notebook - and I know it will be fixed on the next release - that transparent window had a few side effects. It must have had some "In Front" attribute because if it covered part of another app's window - like a web page - the buttons under the transparency were shielded from picking up a mouse click.
The unaware user would think their browser was malfunctioning or their mouse needed new batteries. Yes, you can see the faint border of that transparent window - if you have the right colors on your background graphic.
Thank you for checking it out and jumping on a fix. There is no slow-down because of it.
I am using Modern Fortran by Clerman and Spector and Modern Fortran Explained by Metcalf, Reid, and Cohen for syntax examples. Not the best - Clerman's doesn't even have the word "Operator" in the index - but I'm pushing my way through.