https://bugs.kde.org/show_bug.cgi?id=473429
Bug ID: 473429
Summary: New start screen in 5.2 Beta adds extra steps to
docker plugins that create a new project
Classification: Applications
Product: krita
Version: nightly build (please specify the git hash!)
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Dockers
Assignee: krita-bugs-n...@kde.org
Reporter: chirn...@hotmail.com
Target Milestone: ---
Krita 5.2.0-beta1
The new reorganized start screen (with the donation banner at the top and
deactivated dockers section) has added extra steps for the docker plugin I'm
writing. The plugin allows you to create a new Krita project and sets some
settings like the color model, profile, bit-depth, along with creating a whole
layer/filter stack. It's opinionated due to purpose: creating normal maps and
other PBR maps for realtime engines. So, it won't let you even choose the CMYK
model or one of the float bit depths (because the height to normal filter
doesn't work with those at all), for instance.
In previous Krita versions, the docker plugin would be available from the start
screen and you could start a new project from there, but with the new start
screen, you have to create a new image first, and only then can you create a
new project from my docker plugin. This also means you now have two documents
open by default: the blank one and the one you actually want to work on.
Not sure what the solution is, but is there any way to add functionality to set
a property on a docker that will show it on the start screen? I assume the new
start screen is just looping through dockers and hiding everything, and then
unhiding when a document is created, because it's possible to unhide it
manually from the start screen, but that setting is not persistent. Actually,
unhiding only works on startup, not if you've closed a document and end up back
on the start screen. Interesting. Anyway, just adding an if check to that
hiding/unhiding function for a certain visibility property on the docker would
seem like a solution, right?
Alternately, I guess I could create a separate extension that would be
available from the Tools > Scripts menu whose sole purpose is to create a new
project, but that's pretty janky and not at all discoverable, on top of asking
people to install and activate two plugins... Or a section on the start screen
that is addressable from Python, where you can register a widget (even just a
single button would be enough to launch a new project creation window). Or,
something like Maya's custom "shelf" where you can pin scripts to it, which
would be part of the standard UI and therefore persistent (like the new
document, open existing document, save, etc. section at the top left). I dunno,
I'm just spitballing now.
--
You are receiving this mail because:
You are watching all bug changes.
