This problem existed in beta 6 also.
Also when running 3d examples with debug on I get:
the debugged executable quit unexpectedly
seems to relate to invalid memory access error
ide then locks completely
I have also had:
an error has been detected in the IDE!
Error: Segmentation Violation
File: ......tabbargadget.pbi
Line: 1518
and when trying to run example materialtransparent.pb
without debug and fullscreen i get:
The program 'purebasic_compilation0.out' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 19 error_code 2 request_code 1 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Windows 32 bit betas seem almost perfect but still hitting issues in the 32 bit linux
keep up the hard work!
