Just fixed this. Is it worth backporting to the current beta? It will need some testing and affects
Just fixed this. Is it worth backporting to the current beta? It will need some testing and affects the save format. @mikesky ?
MThat would be awesome, yes please!
Aokey doke. that probably nixes any chance of slipping out a 1.1 release though - it really does need some testing!
MWe are due a big test as it is 
AIn which case I should probably only bother backporting it to xr_v2 
Alike - adding this to beta means beta will need to be delayed. which means xr_v2 will probably be ready. so why bother with the beta?
Moh, good point
Mthe part where it's not currently broken, just unexpected, tripped me up heh
Myeah go xr_v2 then
Acool.
AThere's another issue with layers that probably counts as "confusing UX" but I've found it to be more confusing than I originally thought
AIt's the fact that:
- Drawing on (say) layer 2
- Selecting your strokes
- Switching to (say) layer 1
- Deselecting
AThis was intentional as it provides a way to move strokes to a different layer. But it's very easy to do my mistake
AI keep doing it and I wrote the damn feature!
AI can't decide how best to handle this.
AMaybe block switching layers when there's an active selection and make it an explicit action to move stuff?
Moh yeah, I accidentally did that, thought it was intentional but cool 
Mit made sense at least to me, but perhaps not to others
AOptions:
- Disallow switching layers when there's an active selection.
- Deselect automatically when switching layers
- Objects remember their original layer (more work - how do you move things to a new layer?)
A- Ask the user what they want when switching layers?
Mif we were to block it, 2 would be my natural choice
M4 sounds clunky
AA variant of 2 might be "deselect when switching layers but recall that selection when you switch back"
Ai.e. each layer remembers it's selection
Abut 2 still leaves open "how do you move objects to a new layer?" - this is best as an explicit user action. It's just "where does it live and what do we call it?"
AI've been thinking about expanding "selection" with a new panel. Stuff like "saved selections list", "select all objects with same x (color, brush, type etc)"
Aor just another button on the layers palette.
A@ancientworlds or anyone who's used layers - would be good to get input from artists?
AAlso @dangerdano - have you got any thoughts?
BI would say layer switching should deselect strokes (so option 2)
BAs for moving strokes between layers, I have 2 ideas:
- Reworking the duplication, where copying and pasting don't happen at the same time anymore. You press a button to store a selection in the clipboard, and then paste it around with a different button (can also be the same button but differ by being pressed and held)
- Not touching the original duplication and instead just having some sort of storage "pocket" where you can store a selection and then extract it in a different layer
BIdea #1 would essentially make it work more similarly to ordinary art tools, which might make it more intuitive for experienced digital artists
AMost art tools I've used have both "copy+paste" and "duplicate"
BTrue, I might be a bit biased because I rarely use duplication
A1 doesn't sound that dissimilar to the current selection tool behaviour if you grab a selection and then drop copies
BThe key difference is that you don't have to keep holding the stroke to keep duplicating it
Ayeah
BAnd that opens up the opportunity to duplicate it in between layers
Aah of course
Athat gives me an idea. i wonder what happens to a held selection if you try and interact with a panel.
Ai'm guessing panel interaction is disabled while something is held
BCan you even do that given that holding a selection disables your pointer?
BYeah
Abut what if it wasn't...
BThat does feel a little unwieldy not gonna lie
BBut I might be wrong
Ayeah
Athis seems like a lot of change for one simple gap "move selection to another layer"
Amaybe we just need more buttons on the layers panel. at least that stops the complexity creeping into the rest of the app
BNo matter what I think this problem should be solved through a lot of experimentation
BBecause all solutions work, it's more of a matter of comfort and UX