Often i build drawings with Libreoffice. I extensivly use the layers to struct them. Since Version 3.4.xx i isn't possible to move drawed objects between a visible and a invisible layer. The way i find this out is: 1. Open a new drawing 2. draw some figures (e.g. 100 rectangles) :-) now you have 100 rectangles on layer "Layout". 3. switch to another layer (no need to build it) we just use "Controls". 4. draw another rectangle in this layer 5. right-click on the layername and choose "Modify layer" 6. in the upcoming dialog deselect the option visible (so layer Controls is invisible) 7. switch back to layer Layout 8. mark one (or may be more) rectangles and press and hold the left mousekey to move them. Now press and hold the ctrl-key too. 9. try to move the figures to the layer Controls. (you'll see that is impossible) but it is possible to move them to the Layer "Dimensions Lines". Since many versions of Openoffice/Libreoffice it's possible to move figures to invisible layers. Who ever changed this feature, never used it!
Reproducible You can modify layer of an element (like a rectangle) as following a) click element with selected "Layout" layer where object is drawn > control points become visible b) press <control> key and hold c) click element again (still <control>) and leave left mouse button pushed d) move mouse pointer a little > mouse pointer view changes, a little "+" in a rectangle becomes visible below the normal mouse pointer e) move on mouse pointer to an other layer tab ('Controls') > layer tab now shows selected > layer of element has changed, you can see that by making invisible new layer tab To test that I created new DRAWings with additional layer4 (visible) and layer5 (invisible) and did steps a...e for a rectangle each for moving from layer "Layout" to "layer4" and "layer5". My results (all WIN7 64bit) with a new drawing created from (LibO / OOo) Start Center: OOo 3.1.1: Can move to visible layer4, but not to invisible layer5. Mouse pointer view changes to "forbidden" when it is above Tab for an invisible layer, changes back when you move it back above a Tab for a visible layer LibO 3.3.0: Like OOo 3.1.1 LibO 3.4.5: Like OOo 3.1.1 LibO 3.5.1 RC1: Like OOo 3.1.1 So may be I can confirm reporter's observation that it's impossible to change layer that way to an invisible layer, but not the regression, because it never has been possible. I can't understand reasons for that limitation. With <control+x> / <control+x> you can transfer an element to an invisible layer without problems @vohe: With what version (EXACT) did you do the drag and drop successfully? "Controls" is not "a" layer, but very special one. Can you confirm your observations with a new layer? May be, instead of drawing 99 useless rectangles you can try to find out your Operating System? ;-)
NEW due to Comment 1
Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
** 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.4 or later) 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 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) http://downloadarchive.documentfoundation.org/libreoffice/old/ 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: 2015-12-20
Not sure about the use case of being able to draw within hidden layers. But it adds an aspect to layer management. Clarification is needed.
** 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.4.1 or 5.3.6 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) http://downloadarchive.documentfoundation.org/libreoffice/old/ 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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170901
The problem still exists in Version: 6.0.0.0.alpha0+ Build ID: 4c99b8a9de59f3c5280ff2944d9f828822897f4a CPU threads: 4; OS: Windows 6.1; UI render: default; Locale: de-DE (de_DE); Calc: group
** 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The problem still exists in Version: 6.2.0.0.alpha0+ (x64) Build-ID: a201c5c8c3e7ea14001b5634f330dbce2b1f4314 CPU-Threads: 8; BS: Windows 10.0; UI-Render: GL; Gebietsschema: en-US (en_US); Calc: CL
The reason is in View::AcceptDrop in https://opengrok.libreoffice.org/xref/core/sd/source/ui/view/sdview2.cxx#446 Part && pPV->IsLayerVisible( aLayerName ) has to be deleted. But I have not tested, whether this has any side effects.
Perhaps an "easyHack"?
Dear vohe, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear vohe, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Reproduced in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 64d1a735b2b371495bfd56faf7070fb3274533ad CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Like in comment 1, I can see it inherited as OOo 3.3 has the same limitation. Hossein, what do you think of Regina's comment 10?
Issue is still on 7.5.2.3 Any technical workaround? regarding a real solution What about an alternative approach to drag and drop? Maybe adding the layer to the shape-organize submenu? Creating a side view for layers?
I've realize that sometimes and using CRTL or shift key I am able to drap and drop on the target layer. I dunno the exact pattern as Crtl key makes a copy of selection but sometimes when dragging i got a different cursor icon.
(In reply to dapgo from comment #15) > Issue is still on 7.5.2.3 > Any technical workaround? > > regarding a real solution > What about an alternative approach to drag and drop? > Maybe adding the layer to the shape-organize submenu? > Creating a side view for layers? dapgo, please always try to reproduce with the latest release. Also, please don't change the Hardware fields to your personal ones, as the issue has already been confirmed for various hardware and OS. I'm setting those back to "all". An alternative to drag-and-drop is requested in bug 122587. I guess a currently functional workaround is cutting, changing layer, pasting.
(In reply to Stéphane Guillou (stragu) from comment #17) > (In reply to dapgo from comment #15) > > Issue is still on 7.5.2.3 > > Any technical workaround? > > > > regarding a real solution > > What about an alternative approach to drag and drop? > > Maybe adding the layer to the shape-organize submenu? > > Creating a side view for layers? > > dapgo, please always try to reproduce with the latest release. > Also, please don't change the Hardware fields to your personal ones, as the > issue has already been confirmed for various hardware and OS. I'm setting > those back to "all". > > An alternative to drag-and-drop is requested in bug 122587. > I guess a currently functional workaround is cutting, changing layer, > pasting. Thanks Stéphane, i changed hardware by mistake. Yes the cut and paste between layers work, but i suppose that many users will not expect this feature if they see that drag and drop seem to not exist.