Publisher 2.0.3 - layers panel: first contextmenu raised on layers panel is displayed in the wrong screen position

[4dimage]

Hi, i found this by accident in Publisher. But this error affects all apps in all versions:

v1.10.6.x, 2.0.3, 2.0.3 beta.

If i just load a document and raise a contextmenu on a layer in the layers panel (right click) the contextmenu pane is always shown at the left screen border and a random y-position. If i close the first contextmenu (escape od clicking elsewhere) and do a rightclick on a layer in the layer panel again the second and all following contextmenus now appear at the correct position near the mouse cursor.

The same behaviour appears with each new document when right clicking on the initial master page layer directly after creating the document with "New...". Regardless of whether another document is already open.

If the first contextmenu is opened directly on an element in the workplane (e.g. right click on an image element) the contextmenu opens at the correct position near the mousepointer from the beginning.

I have a native screen resolution of 2560 x 1440. The video only shows fullhd. But the error also appears if i resize the app window to fullscreen.

v1:

 

v2:

 

 

[MikeTO]

Hi, I believe I've seen other reports of this, too, as well as reports of the context menus appearing at different scales depending on which monitor they were opened on. Hopefully these issues are all related and can be fixed at the same time in an upcoming update.

Cheers

[NathanC]

Hi @4dimage,

Many thanks for providing detail, i've now logged this instance with the developers.

[Affinity Info Bot]

The issue "Context Menu appears in top left of app if called on opened document without left clicking the layer first" (REF: AFB-7150) has been fixed by the developers in internal build "2.1.0.1736".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.