@Wave,
I found the 'duplicate file loading' bug. It happens when an application throws an exception, and this exception is located inside an imported or included bmx file, wich its relative path contains a ..\ starting.
As instance:
import "../anotherfile.bmx"
could cause a duplicate file loading in BLIde, if the application crashes inside this file.
This bug will be fixed on a next release (I hope next week).
I'm also thinking the way to let users load single bmx files (not application oriented, just files)... I think it's a very good suggestion.
I found the 'duplicate file loading' bug. It happens when an application throws an exception, and this exception is located inside an imported or included bmx file, wich its relative path contains a ..\ starting.
As instance:
import "../anotherfile.bmx"
could cause a duplicate file loading in BLIde, if the application crashes inside this file.
This bug will be fixed on a next release (I hope next week).
I'm also thinking the way to let users load single bmx files (not application oriented, just files)... I think it's a very good suggestion.