Transparency via keyboard stops working (.26)
-
@Ingolf If the issue is encountered: try clicking on the selected object, or select it again, and try again the numeric key transparency input.
It might be that some panel gets the key input. -
@vectoradmin said in Transparency via keyboard stops working (.26):
@Ingolf If the issue is encountered: try clicking on the selected object, or select it again, and try again the numeric key transparency input.
It might be that some panel gets the key input.- Select the object on the canvas, transparency keys work
- Click it in the layers panel, transparency keys do not work
- Select the object on the canvas, transparency keys work
Etc. Selecting something directly from the layers panel disables input for this feature. Panel get that input allright.
Deja-vu? Didn't we establish this pattern last week you and I and some user?
🍏 macOS Sequoia Apple Silicon
-
@Ingolf Yes this happens when panels are "focused" for keyboard. I will try to figure out how to solve this.
Some panels might need those key inputs. -
@Ingolf said in Transparency via keyboard stops working (.26):
- Select the object on the canvas, transparency keys work
- Click it in the layers panel, transparency keys do not work
- Select the object on the canvas, transparency keys work
Etc. Selecting something directly from the layers panel disables input for this feature. Panel get that input allright.
I was looking into this issue, and at least here, when something is selected on the canvas, the transparency keys work (even if the layers panel is clicked).
But of there is no selection on the canvas, and an object is "highlighted" on the layers panel, then of course the keys don't work on the Layers panel selection.Since in VS (by default) selections on canvas and selections in Layers panel are not the same, and the transparency keys were defined only for selection on canvas, so far this works as designed.
Should the transparency keys work in the Layers panel on "highlighted" objects in Layers panel?
-
@vectoradmin said in Transparency via keyboard stops working (.26):
Should the transparency keys work in the Layers panel on "highlighted" objects in Layers panel?
Yes
-
@vectoradmin said in Transparency via keyboard stops working (.26):
Should the transparency keys work in the Layers panel on "highlighted" objects in Layers panel?
You should really also consider letting the space bar activate panning (hand tool) when the layers panel is active.
It is a common scenario for me to select a object/layer in the layers panel and then hit spacebar to pan to that area or another area but I have to click on the canvas first.
-
@Ingolf said in Transparency via keyboard stops working (.26):
@vectoradmin said in Transparency via keyboard stops working (.26):
Should the transparency keys work in the Layers panel on "highlighted" objects in Layers panel?
You should really also consider letting the space bar activate panning (hand tool) when the layers panel is active.
This should be working now, unless an object name editing is open in the Layers panel.
I just tested this on Mac: click with the mouse in the Layers panel (to activate it) and then press space for panning, moving the mouse over the canvas did show the panning cursor, and panning was active. -
@vectoradmin said in Transparency via keyboard stops working (.26):
@Ingolf said in Transparency via keyboard stops working (.26):
@vectoradmin said in Transparency via keyboard stops working (.26):
Should the transparency keys work in the Layers panel on "highlighted" objects in Layers panel?
You should really also consider letting the space bar activate panning (hand tool) when the layers panel is active.
This should be working now, unless an object name editing is open in the Layers panel.
I just tested this on Mac: click with the mouse in the Layers panel (to activate it) and then press space for panning, moving the mouse over the canvas did show the panning cursor, and panning was active.Nothing
-
@Ingolf I keep this issue open and will try to replicate it.
-
@Ingolf This problem should be fixed in build 1.1.048
