[hatari-devel] Problem with NVDI and latest hatari sources

[Uwe Seimet]

Hi,

> > starting Hatari the issue is gone. But in this case I have a different
> > problem: The Hatari window is placed elsewhere on the screen (looks as
> > if the Window manager now places the window at a location not yet used
> > by other windows) and the Hatari and X11 mouse cursor are not properly
> > synchronized anymore.
> 
> To keep mouse cursor in sync, you need to enable mouse grabbing.  To have it
> in sync from the beginning, you need to have mouse grab enabled from the
> beginning. There's a "--grab" command line option for latter and keyboard
> shortcut just for former.

But why is the Hatari windows placed at a different screen location when
starting Hatari with bUseExtVdiResolutions set to FALSE instead of TRUE?

> When you earlier said that:
> 	the print preview (as well as the actualprintout) do not correctly
> 	recognize the paper size (A4) anymore. The output is clipped, so that
> 	only the upper left corner is visible.
> 
> to what size it's clipped?   E.g. size of ST-low or ST-high screen size?

I think it's even less. I have added a screenshot to this posting. The
screen region in white is the area the Tarkus software, most likely
based on VDI information, clips the DIN A4 page size to. With
bUseExtVdiResolutions set to FALSE the complete page is white, and when
actually printing the complete sheet of paper is printed to. With
bUseExtVdiResolutions set to TRUE only the white area is printed to,
i.e. the printout is incomplete (clipped), just as the print preview
indicates.
Please note that with older versions of Hatari even with
bUseExtVdiResolutions set to TRUE there was no clipping and the
printouts were complete.

> Do similar issues happen with any other software?

I don't know because I do not use any other software which so
extensively uses the VDI, i.e. I have not observed similar problems with
other pieces of software.

> I need some way to reproduce the issue, otherwise I cannot debug it.
> Is this software available somewhere?

No, I'm afraid it isn't.

> With your config I could reproduce the crash and it happened also with v1.4
> release.
> 
> I've commited a fix to the crash and to another issue revealed by the fix.

Thank you, there is no crash anymore.

Best regards

Uwe
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hatari.jpg
Type: image/jpeg
Size: 93953 bytes
Desc: not available
URL: <https://lists.berlios.de/pipermail/hatari-devel/attachments/20110206/cd8ed8ab/attachment.jpg>