Besides BMAX wont work anymore for me since the lastest update, bugger it Dont just work at all, so I had to regress to what is the older (but perfect version) of BMAX, some of the changes to BMAX now crash my computer, even intermittantly without any messages etc.
It looks like I might have to move on relucantly at some point.
PS. How come B3D's IDE highlights syntax almost immediately, but BMAX nearly overloads/locks my powerful PC notebook when I open large BMAX source code?
B3D's IDE is dodgy AS with no undo I could lose a chunk of source code by accidently bumping the mouse pad on my notebook with my thumb, and that just about kills it for me anyway, several years later its unusal to find that the same issue still exists, as I wouldnt let that go on in my free programs, even NotePad has undo.
Is anyone else having problems with BMAX 1.24 ,im getting many issues that never existed in the last release? like problems in the audio sound driver, standard open file dialog has moved hard left/top (Ouch) ,Intermittantly ungracefully exiting my app without any warning or messages, FLIP (to update a canvas) crashes my apP AFTER "endgraphics" etc..etc... or is it just me?
Remembering that Bug spotting is very easy but skilled bug repairing takes a skilled programmer.
It looks like I might have to move on relucantly at some point.
PS. How come B3D's IDE highlights syntax almost immediately, but BMAX nearly overloads/locks my powerful PC notebook when I open large BMAX source code?
B3D's IDE is dodgy AS with no undo I could lose a chunk of source code by accidently bumping the mouse pad on my notebook with my thumb, and that just about kills it for me anyway, several years later its unusal to find that the same issue still exists, as I wouldnt let that go on in my free programs, even NotePad has undo.
Is anyone else having problems with BMAX 1.24 ,im getting many issues that never existed in the last release? like problems in the audio sound driver, standard open file dialog has moved hard left/top (Ouch) ,Intermittantly ungracefully exiting my app without any warning or messages, FLIP (to update a canvas) crashes my apP AFTER "endgraphics" etc..etc... or is it just me?
Remembering that Bug spotting is very easy but skilled bug repairing takes a skilled programmer.