Well, that is interesting. It flickers for me when I rotate the drawing with
the frame clock on GTK3.22. Maybe it is just my slow computer. It works well
with GTK3.18 though.
With the socket_plug1.c drawing the flickering gets worse the farther "down" in
the drawing so I figured it is being
Hey Eric,
> I usually just test on ubuntu16.04 with GTK3.18. Now you have me
> checking a few things with GTK3.22. I have been working on a small
> drawing program that doesn't use sockets or plugs and it does the same
> flickering on GTK3.22 especially with animation but it works fine with
>
Hi Rene,
I usually just test on ubuntu16.04 with GTK3.18. Now you have me checking a few
things with GTK3.22. I have been working on a small drawing program that
doesn't use sockets or plugs and it does the same flickering on GTK3.22
especially with animation but it works fine with GTK3.18.
> If the GtkSocket and GtkPlug can be fixed they should be. They have
> worked at least through version 3.18 and have never been deprecated. It
> would be a good thing if they worked for all of GTK3 and the last stable
> version of 3.22 for consistency.
Ok, I've reported the bug here:
If the GtkSocket and GtkPlug can be fixed they should be. They have worked at
least through version 3.18 and have never been deprecated. It would be a good
thing if they worked for all of GTK3 and the last stable version of 3.22 for
consistency.
It looks like it has something to do with
You are right!
> Looking around it looks like the GtkPlug and GtkSocket never got
> deprecated but I don't see them in the master branch anymore.
Look at this commit:
https://git.gnome.org/browse/gtk+/commit/?id=021fe010b6cbf5119938efbad3122ef2854fc62b
and this article:
It looks like a bug in GTK but I haven't figured out what is causing it. A bug
report in bugzilla would be good. Maybe someone can pinpoint the cause of the
flicker better than I can.
Looking around it looks like the GtkPlug and GtkSocket never got deprecated but
I don't see them in the
Our opinion (ardour developers) is that no desktop GUI toolkit is
appropriate for plugins.
We were distressed to see Steinberg use gtkmm for this purpose (even though
we use gtkmm for ardour).
Plugins do not need to use the same toolkit as the host.
We have no plans to add VST3 support at any
Hey Paul,
thanks for your remark. Since Steinberg released the technical preview
of VST3 with Linux support, I try to port my synthesizer. The SDK
contains a tiny host called EditorHost. It simply opens up the GUI
editor of a plug-in. The host uses gtkmm (like my plug-in) and passes
the
Hey Eric,
> I looked at this a little more and can get the flicker. Testing on
> Ubuntu16.04 with GTK3.18 it works without flicker and on Ubuntu16.04
> with a jhbuild of GTK3.22 it does flicker. I tweaked your code a little
> so that I could test it a little easier.
Good, that you can reproduce
Hi Rene,
I looked at this a little more and can get the flicker. Testing on Ubuntu16.04
with GTK3.18 it works without flicker and on Ubuntu16.04 with a jhbuild of
GTK3.22 it does flicker. I tweaked your code a little so that I could test it a
little easier.
Eric
/*
gcc -Wall
I don't know about the flickering and don't have Ubuntu17.04 to test with.
If I test out 100 pixbufs and try to redraw with a timer at 16ms it will draw
without flickering but not update the drawing every 16ms. It is dependent on
the draw callback drawing time. For long drawing times you
For whatever it's worth, I was working on a similar plugin situation 16
years ago. I tried using plug+socket. Couldn't make it work. GTK+
developers at the time told me to stop using it.
We now get a Gtk::Widget* from a plugin and add that to our own Gtk::Window.
On Tue, Sep 26, 2017 at 1:54
Hey Eric,
It looks like you are trying to paint a surface 100 times every 16ms.
Maybe not such a good thing to do.
Yes, I agree but that's on purpose in order to make the problem *very*
obvious ;) In one of my projects I draw round about 25 bitmaps (which
partly overlap) onto the
Hi Rene,
It looks like you are trying to paint a surface 100 times every 16ms. Maybe not
such a good thing to do. If you are looking to animate a drawing, GTK has a
frame clock that is easy to use.
The plug and socket are separate programs. You would start your socket and add
one or more
> But you seems to do the drawing completely wrong.
>
> Generally gtk_widget_queue_draw() is involved in the drawing process,
> that is that your timer does not do the drawing directly, but only
> invalidates the widget, which cause a indirect draw.
True, you are right. I had a look at a bunch
On Sun, 2017-09-24 at 13:54 +0200, René Hansen wrote:
> it starts flickering constantly
I don't know what Socket and Plug is...
But you seems to do the drawing completely wrong.
Generally gtk_widget_queue_draw() is involved in the drawing process,
that is that your timer does not do the drawing
Hey GTK list,
I've uploaded a demo app on https://github.com/rehans/GtkSocketPlugDemo
It is very simple and just creates a GtkWindow with a GtkSocket child. A
GtkPlug with an GtkDrawingArea attached is connected to the socket. The
GtkDrawingArea redraws itself every 16ms and simply paints an
18 matches
Mail list logo
