Scol

arkeon wrote:

This is not a bug, you can call that a behavior that do not feet your needs :)

Can you post a simple code that produce the behavior ?

bug, behavior, perhaps 'issue' would be the best word (in English), although I think that it gives the user a bad impression to start up an application (including os3d) and see that the loading screen hangs.

it doens't deter me from using os3d, but perhaps may deter others. they will see the grey window and think that something isn't quite right. that's just my opinion.

in os3dload.pkg,

fun main()=
//create a window in this function, then pass the window as an argument to fun loadOS3D
//as the .pkg dependencies are loaded in loadOS3D, the window will hang

in os3dplayer.pkg:

fun initOs3dPlayer(file, projname, pw ,ph, fullscreen)=
let _GETscreenSize -> [ssw ssh] in
let _CRwindow _channel nil ((ssw/2)-200) ((ssh/2)-75) 400 150 WN_NOBORDER|WN_NOCAPTION|WN_TOPMOST "Initializing Window" -> window in

//insert rest of code from this function in os3dplayer.pkg here
//i have found it impossible to create a compbitmap in such a window, i.e. it doesn't render at all during 3d initialization. the most i can do is render comptext in an objectcontainer.
the window will gray out and hang

i hope that helps, I'll email you the complete source if this doesn't explain things.

hebdemnobad wrote:

arkeon wrote:

This is not a bug, you can call that a behavior that do not feet your needs :)

Can you post a simple code that produce the behavior ?

bug, behavior, perhaps 'issue' would be the best word (in English), although I think that it would give the user a better impression if the starting screen(s) don't hang at startup.

it doens't deter me from using os3d, but perhaps may deter others. they will see the grey window and think that something isn't quite right. that's just my opinion.

in os3dload.pkg,

fun main()=
//create a window in this function, then pass the window as an argument to fun loadOS3D
//as the .pkg dependencies are loaded in loadOS3D, the window will hang

in os3dplayer.pkg:

fun initOs3dPlayer(file, projname, pw ,ph, fullscreen)=
let _GETscreenSize -> [ssw ssh] in
let _CRwindow _channel nil ((ssw/2)-200) ((ssh/2)-75) 400 150 WN_NOBORDER|WN_NOCAPTION|WN_TOPMOST "Initializing Window" -> window in

//insert rest of code from this function in os3dplayer.pkg here
//i have found it impossible to create a compbitmap in such a window, i.e. it doesn't render at all during 3d initialization. the most i can do is render comptext in an objectcontainer.
the window will gray out and hang

i hope that helps, I'll email you the complete source if this doesn't explain things.

Allow multithreading to allow vm to display 2d content in one thread while it is busy initializing so3 engine in another thread.

Allow multithreading to allow vm to display 2d content in one thread while it is busy initializing so3 engine in another thread would be the more informed way of describing adding this feature, feel free to close this request down and I will post another one with a more technical and accurate description.