Bug 32736

Summary: mismanagement of the screen after switching to full screen by macro
Product: LibreOffice Reporter: pierre-yves samyn <pierre-yves.samyn>
Component: BASICAssignee: Not Assigned <libreoffice-bugs>
Status: NEW --- QA Contact:
Severity: normal    
Priority: medium CC: tml
Version: Inherited From OOo   
Hardware: x86 (IA32)   
OS: Windows (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Screenshot : form "cascading"
Sample odb
sample adapted

Description pierre-yves samyn 2010-12-30 01:10:02 UTC
Created attachment 41524 [details]
Screenshot : form "cascading"

Hello

LibO 330m18 - XP SP3

Unlike previous versions of OOo, displaying a form in full screen mode by macro causes a mismanagement of the screen (after switching to full screen).

- The form appears twice in cascade (see screenshot)
- The Windows taskbar is always displayed (but is not active)
- The screen is not refreshed ...

Note: The macro is associated with the event "on load"

Best regards
Comment 1 pierre-yves samyn 2010-12-30 01:12:38 UTC
Created attachment 41525 [details]
Sample odb

reproduce the bug : Enable Macros and then open the form
Comment 2 Yifan Jiang 2010-12-30 21:11:37 UTC
Reproduced on LibO 3.3 rc2 Windows XP.

It doesn't happen with the same LibO build on SLED 11 sp1.

However using C-S-j to full screen manually doesn't have this problem in either builds.

Hi Noel, I am not sure if this is proper for your review. Please re-assign if it is not a Basic problem. Thank you!

I also added Tor to the cc list to see if there's some thing changes in Windows build since previous build.
Comment 3 spYre 2011-02-04 01:50:17 UTC
Created attachment 42919 [details]
sample adapted

For information :
bug will not be reproduced when menubar is hidden first.

Best regards
Comment 4 Noel Power 2013-02-05 14:47:44 UTC
I see the same problem on windows 4.0 build ( with just the keybinding cntrl-shift-j ) so I don't believe this is macro related
Comment 5 pierre-yves samyn 2013-02-05 15:21:54 UTC
Hello

(In reply to comment #4)
> I see the same problem on windows 4.0 build ( with just the keybinding
> cntrl-shift-j ) so I don't believe this is macro related

You're right, I confirm with Windows XP Pro & Version 
4.0.0.2 .0.2 (Build ID: 5991f37846fc3763493029c4958b57282c2597e)

So "Basic" is not the appropriate component. What do you suggest?

Regards
Pierre-Yves

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.