Main menu
You are here
GTk LV2 plugs small issue
29 May, 2013 - 19:56 — nobody (not verified)
Since some time I get any time on close a gtk based LV2 plug GUI,
(qtractor:7788): Gtk-CRITICAL **: IA__gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed
In the time before that, I have always close the widget twice, were the second close was just a gray empty widget. Now the widget close on the first click, but I get the warning above.
qtractor version is 0.5.8.23 svn update today.
greets
hermann
Forums:
re. GTk LV2 plugs small issue
i can't remember if it ever got to be clean and quiet, ever :) gtk lv2 uis are wrapped trough x11embed via libsuil (gtk2 on qt4). i must say that it works just barely enough and quite frankly it does it mostly due to great part of qt4 playing nice with glib so well--just try running qtractor with QT_NO_GLIB=1 and see (not) your gtk plugins falling apart if showing at all
all that to say that the above warning is the least of the problems when dealing with lv2 gtk plugin guis under a non-gtk host. yes i know that it says "critical" up there but well, i'd be lying if i say i care that much ;)
otoh. if that's one of your own plugins (ones of guitarix if i'm not mistaken), i'd recommend you to include support for lv2_external_ui in some near future. please. in the long run, when qt5 comes mainstream, that will be the only option for qtractor, as libsuil will be of no use, actually it will be hell counter-productive under qt5. sad but true :)
cheers
well, that's not only with my
well, that's not only with my own plugs, but with all gtk based plugs. However, I'll consider to add lv2_external_ui support, even if I prefer to stay with the standard only. If all get broken, there is still your internal ui so that plugs will leave useable in any case.
greets
hermann
re. consider to add lv2_external_ui support
re. consider to add lv2_external_ui support
just fyi. that's also what linuxdsp.org.uk applies to their plugins: besides their native lv2_x11_ui which is also wrapped by libsuil, they deliver a lv2_external_ui interface in addition so that a (future) qt5 host can pick them up as fine.
in fact, if you build qtractor against qt5 you'll see that it will only support lv2_external_ui or native qt5_ui; otoh. loading a qt4 shared object into a qt5 host does not work either--it's total havoc!
byee
Add new comment