QB64 info (please complete the following information):
First, make sure you've tried to replicate the problem in the latest development build.
: [Yes, the issue is in the latest dev build. / No, the issue was fixed. Yay!]
If the suspected bug is also present in the latest dev build, please report what you get in the Help->About dialog: [e.g. Version 1.5 dev build from git a6101af]
Report the OS you're using: [e.g. Windows 10 Build 2H2D]
REPLY Not applicable
Describe the bug
A clear and concise description of what the bug is.
However, your team does not use the domain QB64.ORG
You're using QB64.COM
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
REPLY 1. Read the original template. Error is clearly obvious.
A clear and concise description of what you expected to happen.
REPLY This template should use QB64.COM, not .ORG.
Paul
"The lessons of history teach us - if they teach us anything - that no one learns the lessons that history teaches us."
Paul Robinson xdpascal@xdpascal.com
"Unlike Alanis Morisette, I do know what Irony is."
QB64 info (please complete the following information):
Help->Aboutdialog: [e.g.Version 1.5 dev build from git a6101af]REPLY Not applicable Describe the bug A clear and concise description of what the bug is.
This template advises people reporting bugs to use the template at Get it from https://www.qb64.org/portal/development-build/
However, your team does not use the domain QB64.ORG You're using QB64.COM
To Reproduce Steps to reproduce the behavior:
REPLY 1. Read the original template. Error is clearly obvious. A clear and concise description of what you expected to happen. REPLY This template should use QB64.COM, not .ORG.
Paul "The lessons of history teach us - if they teach us anything - that no one learns the lessons that history teaches us."
Paul Robinson xdpascal@xdpascal.com "Unlike Alanis Morisette, I do know what Irony is."