sphh

Thanks! Very helpful indeed. Do I have to check for the existence of `self.item` or of `self.item.inputs[i].widget`?

Thanks, works perfect: The `dtypes` input widget is now disabled. The only minor problem is, that both widgets look the nearly the same; but this is a problem of the...

The workaround works perfectly, but I leave this issue open, because it refers to the feature request of disabling the whole input. I hope, this is ok.

I now encountered another ‘error’: When I add such a node, all input widgets are initially active. I tried to update the input widgets from the node's `__init__()` method (after...

Excellent! That's that one I was looking for. Thanks.

I mean: Flow updates – The `update_event()` of all nodes are called.

Yes, I use `dtype` widgets! And if we used the [`textEdited`](https://doc.qt.io/qt-5/qlineedit.html#textEdited) signal, `update_event()` would be called on every edit action and with [`returnPressed`](https://doc.qt.io/qt-5/qlineedit.html#returnPressed) the `update_event()` is only called, if the...

> Pressing return should IMO still be possible for forcing updates, but I can make the update on unfocus conditional, I think. Sounds like a good plan!!

Thanks! That looks really great. I applied your commit https://github.com/leon-thomm/ryvencore-qt/commit/48bab818bfacd4a5364b8e27b178c7fa15a27534, but the exception is not shown. I then tried to call `self.update_error(e)` from inside a `Node` and I get the...

> yes, sorry I had to add the update_error() function to the core, […] That makes absolute sense. Thanks. Still the icon and tooltip is not shown. I checked and...