The only problem I found (which is OK in 241):
When I set to DirectX+VRAM, Full screen (change res mode) and no menu and no header options selected, the top of the screen is a black strip, cuts off around 20 or so pixels from the top of the frame.
The only problem I found (which is OK in 241):
When I set to DirectX+VRAM, Full screen (change res mode) and no menu and no header options selected, the top of the screen is a black strip, cuts off around 20 or so pixels from the top of the frame.
Andy H @ ovine.net
Awful Jokes - a new cartoon every day: http://awful.ovine.net/
Ovine's games: http://www.ovine.net

Andy, I cannot reproduce it, I must miss something, could you send me an example? Thanks!
Yves.












[]Andy, I cannot reproduce it, I must miss something, could you send me an example?[/]
http://x.jflom.com/files/klik/AndyH_bug.mfa
http://x.jflom.com/files/klik/AndyH_bug1.gif
http://x.jflom.com/files/klik/AndyH_bug2.gif
.:::.Joshtek.:::.

Thanks. Hmm... works fine on my machine... I'll try on others.
Yves.
I'm running on a laptop with a GeForce Go 7900 GS. Not been able to try on any other PC's yet.











Bug still exsists... (JUMP TO FRAME) in the Event editor.
If for example, you had multiple frames, and you wanted to return to frame#1 from any other frame, you cant insert it using the CHOOSE A STORYBOARD FRAME window.
How to reproduce:
1. Setup 2 or more frames - (the renumbering has been fixed)
2. ON FRAME 2: start the event editor.
3. START OF FRAME -> JUMP TO FRAME ( )
you cannot select frame 1 here with the CHOOSE A STORYBOARD FRAME window.
*workaround*
you CAN however do it by using the calculation button and typing in 1 in the expression box.

Yes, strat59 already said it above. I've redone the whole dialog box as I'm unable to reproduce this problem, on all the machines I've tried it. I'll post a new version later.
Yves.




These new builds always come out when my computer is in bits being shipped across America. Thanks anyway <img src="/center/images/graemlins/smile.gif" alt="" />

Update - I've uploaded a new version of the build #242.
Bug fixes in this version
- Runtime: collision mask problem when a non-obstacle object is positioned (or pasted) in an obstacle (= one of the problems reported above by Joshtek - ps: the other one is actually a limitation, collisions with quick backdrop objects are always in box mode).
- Runtime: crash or problems when you use the Set Full Screen Mode action and the application hasn't the "Change resolution mode" option (fixes the problem reported some time ago when you switch to full screen mode with a 32000 color application).
- Runtime: bug specific to first version of build 242, frame caption bar incorrectly displayed in full screen DirectX mode (reported by Andy above).
- Moo extensions: crashes when using uninitialized or deleted objects.
Also, could someone (danjo, strat59, etc. or anyone else who was able to reproduce this issue with a previous build) please test the Jump to Frame bug and let me know if it's fixed in this version? Thanks!
Yves.

Where is the file?
Is the updated file in the first post?