Wouldn't it be more sensable to have a separate link for Beta software bugs?
Perhaps a bug reporting tool built right into the product that would include
informations derived from the specific PC environment, plus the code where
the error was encountered, plus any user comments. A checklist of boxes to
help classify what part of the product seemed to be involved with the problem, such as the Debugger, Editor, Compiler, Help file, provided examples, syntax checking, computational error, all that stuff. Knowing
which version is involved is important for duplicating the error, and a built-in
bug reporter would be able to include that information automatically.
It would also help to keep a list accessable of known bugs, so that people
can either avoid reporting the same problem over and over, or use the list
to retest problems to see if they are still present in a new version.
Just my thought, anyway. I found a problem trying to compile and run Module.pb in the examples, because windows complained that it could not
find the MIDAS1,dll anywhere in the path. Using search, I found PureBasic
version 4 came with Midas11.lib, but I can't find a way to set it so that the
IDE or program will search alternate paths for it. there is a place under
Compilers/Compiler Options for setting something in the Library Subsystem, but entering a path to d:\PureBasic4\PureLibraries\Windows did not do anything to help.
Adding yet another path to my existing path is not a good option. First, my existing path is incredibly long, because I have a lot of stuff installed
on my PC. Second, I am maintaining version 3.93 and 4 Beta separately,
and adding to the existing path would favor one over the other, which could have some downsides to it.
I went back to look at my download of 3.93, and comparing the two, it
looks like a lot of functionality still has to migrate into version 4's IDE.
Just my take on it so far.
Just My Opinion, but ...
Just My Opinion, but ...
has-been wanna-be (You may not agree with what I say, but it will make you think).
