Is there a way to inject another button into the layerdocker?

[Fourtee2]

I’m writing a docker plugin that requires a toggle on each layer, but I’d very much rather not have to have a list of layers separate from the standard layerdocker in the UI. Is there a way my docker can inject a toggle into each layer listed in the layer docker?

[Celes]

Yes, you can subclass it:

Size of items in QTreeView

Hi Sorry, didn’t had the time to answer before It won’t be easy. In theory you have to override the sizeHint() method of QItemDelegate object of QTreeView. Then the sizeHint() is called internally (you don’t call it by yourself) and methods from QItemDelegate are called with this size. In Krita, the QItemDelegate object is called here. You can see the delegate property is an instance of NodeDelegate class which extend a QAbstractItemDelegate. This class is not available in …

Tips styling layers docker?

I’m customizing the appearance of Krita (it’s lovely but claustrophobic!) and one panel I can’t fully get to is the layer panel. I’d love to alter the size of the icons (lock, alpha, visbility, etc) or even the icons themselves and change the appearance of selected layers row. It’s possible to change the appearance of all rows at once through css (QTreeView::item), of folder rows (QTreeView::item:has-children), and of the middle column containing layer name and type icon of selected layers (QTr…

But it’s hard work indeed, you have to recreate the entire structure in Python and use hacks to display all information about the layer state like whether it’s visible and locked because that data can’t be accessed directly from the API.

[Fourtee2]

Alright, it sounds like for my purposes in the very short term, I should just maintain an internal list of layers. Is there a signal I can hook into that would make keeping track of layer addition/deletion easy to do without polling or waiting for different user-triggered interaction?

Also, just to clarify— are you talking like cheatEngine style direct memhacks for the non-api functions?

[Celes]

@Fourtee2

Alright, it sounds like for my purposes in the very short term, I should just maintain an internal list of layers. Is there a signal I can hook into that would make keeping track of layer addition/deletion easy to do without polling or waiting for different user-triggered interaction?

I don’t think there’s one. There’s no notifier and I don’t recall seeing a signal
either. I hooked everything I needed directly into the draw method for the docker since I was redrawing the entire thing anyway.

@Fourtee2

Also, just to clarify— are you talking like cheatEngine style direct memhacks for the non-api functions?

That level of sophistication is way above my paygrade, hah. I just retrieved the missing props directly from the document nodes.

---

If you didn’t see it already get the Python Developer Tools plugin.

[Fourtee2]

Would you be willing to give me a quick code snippet or reference another post for grabbing those less-accessible document properties? I really appreciate all of your help! I hope to be sharing a fun integration between Krita and live VJing software soon.