"Klick" Problem since 3.5.0 / fine in 3.4.0

[bladecgn]

I have a very strange problem since Version 3.5.0:

When I start Ambermoon in 3.5.0 from hdd (on a hdf) via double klick on its icon, the loading screen with the fairy shows up very briefly.

It is stopped as if the left mousebutton had been pressed and the main menu appears.
If i move up the mousepointer the menu item "Quit" is selected an the program exits although i don't klick any button.

If I exchange the 3.5.0 exe with 3.4.0 everything gets back to normal.

HELP!

[bladecgn]

Additional:

When I am in 3.5.0 on the Ambermoons main menu screen and i remove the mouse dongle and reinsert it again everything is fine, i.e. when i move the mousebutton up to the "quit" menu entry it does not get selected automatically.

[Toni Wilen]

Not enough information. 1) HD based = too many unknown variables. Must be tested without startup-sequence. 2) Config is also missing.

[bladecgn]

Found out it has to do with "resolution autoswitch":
If enabled the above described problem occurs,
if not everything is fine.

After the resolution switches via autoswitch from superhires to lores WinUAE 3.5.0 thinks the left mousebutton is held.

Included is the config.

[Toni Wilen]

Strange.. Could you check 3.5 betas and find out the update the causes this side-effect? (http://eab.abime.net/showthread.php?t=85939 links should work)

[bladecgn]

Sure!

I checked the 3.5.0. (= 3.4.1) betas:

Beta 1: Still working fine
Beta 2 onwards: Not working any more

[mark_k]

I guess the problematic change was this:
- Clear button state mask when mouse capture state changes. If mouse or joystick button was kept pressed when mouse was uncaptured, button was kept pressed when capture state was restored even if real button was already released.

This issue is easy to reproduce. Set resolution autoswitch to always on. Boot to high res laced Workbench. Run Imploder which opens its own high res non-laced screen. Click and drag Imploder title bar down and up so display mode changes when the (interlaced) WB is visible behind it.

After you release the mouse button, it stays stuck in the down position so you can drag the screen up & down without holding any button. The mouse capture state isn't actually changing, but releasing/acquiring the D3D surface seems to make WinUAE think it is?

The same thing happens in full-screen mode. There, apart from the mouse-stuck issue, the screen blanks for about a second each time the resolution changes. Maybe that's unavoidable. Full-window mode doesn't have that blanking.

By the way, would it be possible to minimise freeing/reallocating when new size = old size? In the log output it looks like the draw temp buffer is being freed and reallocated with the same size on each mode change.

At PAL high-res laced WB, run Imploder:
PAL mode V=49.9204Hz H=15625.0881Hz (227x312+1) IDX=10 (PAL) D=0 RTG=0/0
RES -> 1 (1) LINE -> 0 (0) (0 - 0, 2 - 1)
window already open (1831x565 1536x1152)
Allocated draw temp buffer (1600*1280*32) = 1781F020
Device name: 'AMD FirePro W5100' 16001300a10a01.0
D3D9Ex: 00000056 00020000 E0020000 000003A0 ALPHA DYNAMIC SCANLINE
D3D9Ex: PS=3.0 VS=3.0 1536*1152*0p VS=0 B=0I 32-bit 0 (16384x16384)
Using non-shader version
D3D9Ex: 1504*1152 main texture, depth 32
Buffer size (1504*1152) Native
PAL mode V=49.9204Hz H=15625.0881Hz (227x312+1) IDX=10 (PAL) D=0 RTG=0/0
D3D9Ex: 752*287 main texture, depth 32
Buffer size (752*287) Native
RTGFREQ: 312*49.9204 = 15575.1668 / 49.9 = 312
POS (0 0 1536 1152) - (-392 -432 376 144)[768,576] (384 288)

Drag Imploder screen down to reveal WB behind:
PAL mode lace V=50.0003Hz H=15625.0881Hz (227x312+1) IDX=10 (PAL) D=0 RTG=0/0
RES -> 1 (1) LINE -> 1 (1) (0 - 0, 2 - 1)
window already open (1831x565 1536x1152)
Allocated draw temp buffer (1600*1280*32) = 1781F020
Device name: 'AMD FirePro W5100' 16001300a10a01.0
D3D9Ex: 00000056 00020000 E0020000 000003A0 ALPHA DYNAMIC SCANLINE
D3D9Ex: PS=3.0 VS=3.0 1536*1152*0p VS=0 B=0I 32-bit 0 (16384x16384)
Using non-shader version
D3D9Ex: 1504*1152 main texture, depth 32
Buffer size (1504*1152) Native
PAL mode lace V=50.0003Hz H=15625.0881Hz (227x312+0) IDX=10 (PAL) D=0 RTG=0/0
D3D9Ex: 752*574 main texture, depth 32
Buffer size (752*574) Native
RTGFREQ: 312*50.0003 = 15600.0869 / 50.0 = 312
POS (0 0 1536 1152) - (-392 -289 376 287)[768,576] (384 288)