[Octave-patch-tracker] [patch #9993] Property inspector GUI

[Remi Thebault]

Follow-up Comment #22, patch #9993 (project octave):

> * the inspector should be able to live without the GUI running, at least I'd
be very happy if that happened :-). Since your inspector window inherits
octave_dock_widget, that makes me suspect that the inspector won't run without
the main window running. Am I wrong?

With an intermediate container, that should not be the main problem to solve.
The main problem (for me at least), is that I have no clue how works the code
in the QtHandles namespace.

> * we already have a mechanism to notify the graphics toolkit when graphics
object properties change and at first sight you seem to have re-engineered
another independent one. Maybe your approach is better (and we know the
current mechanism is sometimes fragile), and it could be merged, but it would
be better to not have multiple functions for the same task.

I agree with this. I didn't intend my code to work without the GUI, and it
lives outside of the graphics toolkit.
I currently don't have a grasp on the QtHandles namespace code and how it
connects to the interpreter.

BTW this makes me think that I currently don't listen to properties change
(only to object creation/deletion). I will add this.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/patch/?9993>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/