@John, I can't reproduce it and never seen it happen before. But can imagine what could produce it; probably needs a flushevents() somewhere?!... Can you reproduce this quite consistently??
@ Bram,
Re: tightloop: I know what you mean, but you can't (and I would advice 'never') 'slow down' a WB3D program by introducing a delay, because there will be a very possible chance that you will start to MISS EVENTS from your main gui loop! Which could be extremely anoying to the user ie. having to press something more than once before it responds!
But what I could do perhaps is create like a 'pause mode' sort of button! so you can test your own app in the background.
Re: the CTRL button to scale. That's another tricky thing with WB3D because you can ONLY capture keyboard events when you activate the blitz runtime window ie. when it has focus! Hence the reason you current 'MUST' click on the background (=blitz runtimewindow) before you can use the cursor keys to move/scale a gadget! Kev did start on a global key event or 'hotkey' function but I don't believe that made it to the final release...
Re: the pull down menu not functioning correctly: Yes you're right. I don't know why it doesn't repaint in the editor, I'll look into it.
The menu options not being exported isn't a bug - but more a case of 'the total absence of code' :)) Sorry, guess I never came around to that. You'll have to do that manually for now :/ But I'll try and cough up a little update over the weekend pending hangovers...
cheers,
danny
@ Bram,
Re: tightloop: I know what you mean, but you can't (and I would advice 'never') 'slow down' a WB3D program by introducing a delay, because there will be a very possible chance that you will start to MISS EVENTS from your main gui loop! Which could be extremely anoying to the user ie. having to press something more than once before it responds!
But what I could do perhaps is create like a 'pause mode' sort of button! so you can test your own app in the background.
Re: the CTRL button to scale. That's another tricky thing with WB3D because you can ONLY capture keyboard events when you activate the blitz runtime window ie. when it has focus! Hence the reason you current 'MUST' click on the background (=blitz runtimewindow) before you can use the cursor keys to move/scale a gadget! Kev did start on a global key event or 'hotkey' function but I don't believe that made it to the final release...
Re: the pull down menu not functioning correctly: Yes you're right. I don't know why it doesn't repaint in the editor, I'll look into it.
The menu options not being exported isn't a bug - but more a case of 'the total absence of code' :)) Sorry, guess I never came around to that. You'll have to do that manually for now :/ But I'll try and cough up a little update over the weekend pending hangovers...
cheers,
danny