I have a spreadsheet ported from Excel which contains Macros. When Libra executes the following command in the macro
it gets the 423 run time error
Steps to Reproduce:
1. Create a macro with this VBA command in it
2.Execute teh macro
Basic Runtime error 423
Should clear the sort fields as in Excel
User Profile Reset: No
Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug.
I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document.
(Please note that the attachment will be public, remove any sensitive information before attaching it.)
How can I eliminate confidential data from a sample document?
Created attachment 147324 [details]
Excel spreadsheet ported from excel and saved as an ODS file.
Open spreadsheet. Enable macros.
Go to sheet called Session Scores.
Click on Calculate scores in cell Y18.
You get the run time error 423 occurring on the .sort.sortfields.clear command
Confirm with LO 6.2master; win7. Do you know if it worked in older version?
(In reply to raal from comment #3)
> Confirm with LO 6.2master; win7. Do you know if it worked in older version?
It fails with both LO 6.1.3 and LO 6.2
On previous versions, the error is
BASIC runtime error.
Message: That command cannot be used on multiple selection
in line 102: 'Selection.Copy'
So this macro never worked...
It’s not the selection.copy command that is failing. It’s the command
(In reply to Xisco Faulí from comment #5)
> On previous versions, the error is
> BASIC runtime error.
> Type: com.sun.star.uno.RuntimeException
> Message: That command cannot be used on multiple selection
> in line 102: 'Selection.Copy'
> So this macro never worked...
Attached is the screen shot of when the failure occurs. As you can see it has processed statement 102 and fails on the sort clear command.
Created attachment 147388 [details]
Screen Shot of failure
See latest comments
On previous versions I meant...
Please investigate the failure of command
Screen shot of failure has been attached
Can you please investigate this bug as per previous comment or provide me with an update
(In reply to Tony Donnelly from comment #11)
> Can you please investigate this bug as per previous comment or provide me
> with an update
You never asked to our question. Did it work on previous versions of LibreOffice ?
Happens when the Control is live (not edit mode) and the mapping is - due to non-linear ViewMapping in Calc - dependent on pixel sies. In these cases, ViewObjectContactOfUnoControl_Impl::positionAndZoomControl is called. That uses adjustControlGeometry_throw where
aTopLeft, aBottomRight change while
_rLogicBoundingRect does not (mostly flicker of a single pixel).
This is due to different _rViewTransformation being used, dependent on where the paint is compng from (yes, the live Controls' positioning works by lay-positioning these during paint what may lead to an invalidate in the window, but usually only *once*, except for the crude Calc non-linear ViewTransform mapping - ARGH)
Key to fix this will be to find out which tranform would be the correct one and which path uses the wrong one...
Was comment 13 meant to be written in bug 121963 instead ?
All calls emerge from a single ScGridWindow::DrawContent. Every 2nd paint triggers between two pixel value variations, this can be best seen in
One call inside ScGridWindow::DrawContent triggers one pixel value set, another triggers the alternative one. These calls are:
DrawRedraw( aOutputData, SC_LAYER_INTERN ); -> smaller/more left
pContentDev->SetMapMode(aCurrentMapMode); -> bigger, more right
These do then alternate endlessly, because they invalidate different parts. Question is why these lead to different pixel position values...
@Xisco: OOps - yes, sorry. Also the last one. Adding text to the correct bug...
Please ignore comments 13-15 at this task (can these be deleted...?)
Dear Tony Donnelly,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Dear Tony Donnelly,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker