Group selected strokes will not 'Bring to Front'/'Send to Back' if one of the selected strokes is already there #87321

Closed
opened 2021-04-09 01:37:04 +02:00 by Matthew Gafford · 18 comments

Operating system: Win10 Home 64
Graphics card: rtx3070

Blender Version
Broken: 2.93
Worked: N/A

Exact steps to reproduce the error:

Open file frontorback.blend

or

  • Make a grease pencil object
  • Create a fill shape
  • Draw a stroke above the fill, and one stroke behind it

Select both strokes and try to use "Bring to Front" or "Send to Back"

If one of your selected strokes is already in the very back/front, nothing happens. If one of your selected strokes is already in the front when you "Bring to Front" it should ignore that one and still move the other selected strokes to the front. Instead, it just ignores all of them.

[edit] This also happens with "Bring Forward" and "Send Backward."

Operating system: Win10 Home 64 Graphics card: rtx3070 Blender Version Broken: 2.93 Worked: N/A Exact steps to reproduce the error: Open file [frontorback.blend](https://archive.blender.org/developer/F9926330/frontorback.blend) or - Make a grease pencil object - Create a fill shape - Draw a stroke above the fill, and one stroke behind it Select both strokes and try to use "Bring to Front" or "Send to Back" If one of your selected strokes is already in the very back/front, nothing happens. If one of your selected strokes is already in the front when you "Bring to Front" it should ignore that one and still move the other selected strokes to the front. Instead, it just ignores all of them. [edit] This also happens with "Bring Forward" and "Send Backward."

Added subscriber: @AFoxInSpace

Added subscriber: @AFoxInSpace

Added subscriber: @antoniov

Added subscriber: @antoniov

This is something we have designed in this way to keep the integrity of the drawing (stroke order) when move multiple strokes. I will talk with the team to check if must change it or not.

This is something we have designed in this way to keep the integrity of the drawing (stroke order) when move multiple strokes. I will talk with the team to check if must change it or not.

In #87321#1143617, @antoniov wrote:
This is something we have designed in this way to keep the integrity of the drawing (stroke order) when move multiple strokes. I will talk with the team to check if must change it or not.

Every vector drawing program I have ever used would move all selected pieces forward in this situation, not ignore them and expect the user to unselect every individual stroke that is already in that desired position. As a 2d animator, this is definitely something that is a large inconvenience for me every day, group-selecting materials having to find which strokes I've already sent to the front and manually unselecting them before the Send to Front/Back function will actually work. It's extremely frustrating.

> In #87321#1143617, @antoniov wrote: > This is something we have designed in this way to keep the integrity of the drawing (stroke order) when move multiple strokes. I will talk with the team to check if must change it or not. Every vector drawing program I have ever used would move all selected pieces forward in this situation, not ignore them and expect the user to unselect every individual stroke that is already in that desired position. As a 2d animator, this is definitely something that is a large inconvenience for me every day, group-selecting materials having to find which strokes I've already sent to the front and manually unselecting them before the Send to Front/Back function will actually work. It's extremely frustrating.
Antonio Vazquez self-assigned this 2021-04-09 21:40:05 +02:00

Added subscribers: @mendio, @pepe-school-land

Added subscribers: @mendio, @pepe-school-land

@mendio @pepe-school-land What do you think about stroke order and how works now? the change is not complex, it's just a design decission.

@mendio @pepe-school-land What do you think about stroke order and how works now? the change is not complex, it's just a design decission.

I have been checking in Inkscape and if you select a group with something that is on back, you cannot move to back.

The logic is, If you have select a group of strokes, all are managed as one, so if any of the stroke is on back, you cannot move to back because the stroke is already there. The same in the oposite direction for infront.

@mendio @pepe-school-land I think the arrange is working as expected. If we change the logic, it's very easy to destroy the drawings.

I have been checking in Inkscape and if you select a group with something that is on back, you cannot move to back. The logic is, If you have select a group of strokes, all are managed as one, so if any of the stroke is on back, you cannot move to back because the stroke is already there. The same in the oposite direction for infront. @mendio @pepe-school-land I think the arrange is working as expected. If we change the logic, it's very easy to destroy the drawings.

Added subscriber: @filedescriptor

Added subscriber: @filedescriptor

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'

I suppose that this is design has already been confirmed. Right?
So I'm marking it as such then.

I suppose that this is design has already been confirmed. Right? So I'm marking it as such then.

Added subscriber: @Dantti

Added subscriber: @Dantti

I agree with Matthew here, I also was experiencing this issue just moments ago.
This is how arranging works in Illustrator.
The arranging order stays even if there is one already at said position.
But the arranging still works. It is also faster to work.
Hope the video or anything made any sense. :D
arranging_order_example.mp4

I agree with Matthew here, I also was experiencing this issue just moments ago. This is how arranging works in Illustrator. The arranging order stays even if there is one already at said position. But the arranging still works. It is also faster to work. Hope the video or anything made any sense. :D [arranging_order_example.mp4](https://archive.blender.org/developer/F9935129/arranging_order_example.mp4)

I'm going to take a look.

I'm going to take a look.

@Dantti Could you check the patch D10997?

@Dantti Could you check the patch [D10997](https://archive.blender.org/developer/D10997)?

@antoniov

Yes! It works perfectly!
Tested the same behaviour as upper video (OK)
Tested with 6 different fill boxes or strokes (OK)
Works even when 1 point selected in each color.
So good man! Thank you :)

blender_arranging_order_fixed.mp4

@antoniov Yes! It works perfectly! Tested the same behaviour as upper video (OK) Tested with 6 different fill boxes or strokes (OK) Works even when 1 point selected in each color. So good man! Thank you :) [blender_arranging_order_fixed.mp4](https://archive.blender.org/developer/F9936577/blender_arranging_order_fixed.mp4)

This issue was referenced by d9224f64a1

This issue was referenced by d9224f64a1b9f745531a0de408c3b778abff8881

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#87321
No description provided.