Bug 75452 - BASIC: window frame controller doesn't update properly when the changes is made to the document model
Summary: BASIC: window frame controller doesn't update properly when the changes is ma...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Not Assigned
Depends on:
Reported: 2014-02-24 16:15 UTC by Todor Takov
Modified: 2016-02-22 17:32 UTC (History)
0 users

See Also:
Crash report or crash signature:

Snapshot1 is the situation before running thr copy/paste macro. Snapshot2 is after the macro is run. (365.11 KB, application/pdf)
2014-02-24 16:15 UTC, Todor Takov
Snapshot1 is the situation before running thr copy/paste macro. (200.77 KB, image/png)
2014-02-24 16:23 UTC, Todor Takov
Snapshot2 is after the macro is run. (202.22 KB, image/png)
2014-02-24 16:24 UTC, Todor Takov

Note You need to log in before you can comment on or make changes to this bug.
Description Todor Takov 2014-02-24 16:15:15 UTC
Created attachment 94666 [details]
Snapshot1 is the situation before running thr copy/paste macro. Snapshot2 is after the macro is run.

The machine here is running Linux 3.10.17, Slackware 14.1, fairly up to date,
KDE  4.12.2, LibreOffice_4.2.1.1_Linux_x86-64, downloaded from the official
LibreOffice site - no changes whatsoever.

I have one simple .ods file, that has 2 sheets - Sheet1 and Sheet2.
Sheet1 has a very long (~5000) list of rows (5 and more colums wide) . It is opened in one calc window.
Sheet2 is almost emty - 3 rows, containing the column headers only. And is
opened in another calc window.

In a macro, I pick up a row from Sheet1 and copy/paste it in Sheet2 in the
first available empty row. 
And  in order to see the last 3 pasted rows in Sheet2(Second Window) the
macro has a command:

Where numrow is about 3 rows up from where I pasted the last row.

This command acts on the Second open window and it's controller, containing
Up untill version 4.1.4 of LibreOffice this worked flawlessly.
Now in version the Frame Controller scrambles the Second window and
shows arbitrary rows in Sheet2, sometimes each row twice + emty rows in
between them, or even part of the desktop behind the window, which has
nothing to do with the document model. The copy/paste operation is always
correct, but the window frame view does not update correctly. It looks like
arbitrary graphical artefacts.

There is a way to restore the view in the second window, to show the correct
view corresponding to the document model - and this is by moving a little
the vertical scroll slider. Then everything is normal again , untill the
next oFrame.Controller.setFirstVisibleRow(numrow) command.

Has anyone met such behaviour?
And another question - how can I send to the second frame (window) a command
via the dispath DispatchHelper,
to move it's vertical scroll slider by 1 or more units - up or down, doesn't
I could not find a proper dispatch helper URL parameter for the scrollbar -
there is one called "ScrollBar", but I couldn't find an explanation what it
does, or wether it accepts argument , and if yes - what are they. 

Comment 1 Todor Takov 2014-02-24 16:23:56 UTC
Created attachment 94667 [details]
Snapshot1 is the situation before running thr copy/paste macro.
Comment 2 Todor Takov 2014-02-24 16:24:34 UTC
Created attachment 94668 [details]
Snapshot2 is after the macro is run.
Comment 3 QA Administrators 2016-02-21 08:37:26 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

   Test to see if the bug is still present on a currently supported version of LibreOffice 
   (5.0.5 or 5.1.0)  https://www.libreoffice.org/download/

   If the bug is present, please leave a comment that includes the version of LibreOffice and 
   your operating system, and any changes you see in the bug behavior
   If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave 
   a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

   Update the version field
   Reply via email (please reply directly on the bug tracker)
   Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
   appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)


2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword

Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2016-02-21
Comment 4 Todor Takov 2016-02-22 17:32:35 UTC
LibreOffice 5.1.0

kernel 4.4.1 64bit 

Slackware Linux

Kde 4.14.14 
Kde Plasma 5.5.4