@Qimmer,
see http://www.winblitz3d.co.uk/forum/ might be an idea to post your working version. when WM_CLOSE is processed in the windows api winproc it auto calls defwindowproc(). to enable winblitz3d's include version to disable this would need to re-write the custom asm bytecode.
the .dll version that will be available soon does this along with losts more, to much to be listed here.
@Boiled Sweets
15 UK Pounds this includes full access to bug-fixes, updates. winblitz3d's .dll is currently very stable :) the user has full access to winapi gadgets on the runtimewindow or there own window. full control over all windows\gadgets winapi styles using standard constants.
when will it be available to buy? well im still waiting on the docs to be returned from one of winblitz3d's beta testers 'Mr P' and ive still to finish more example. although they are coming along.
kev
see http://www.winblitz3d.co.uk/forum/ might be an idea to post your working version. when WM_CLOSE is processed in the windows api winproc it auto calls defwindowproc(). to enable winblitz3d's include version to disable this would need to re-write the custom asm bytecode.
the .dll version that will be available soon does this along with losts more, to much to be listed here.
@Boiled Sweets
15 UK Pounds this includes full access to bug-fixes, updates. winblitz3d's .dll is currently very stable :) the user has full access to winapi gadgets on the runtimewindow or there own window. full control over all windows\gadgets winapi styles using standard constants.
when will it be available to buy? well im still waiting on the docs to be returned from one of winblitz3d's beta testers 'Mr P' and ive still to finish more example. although they are coming along.
kev