The code prints out the names of the widgets in the font selection widget.
Using the names you can figure out the internal widget pointers you want to get
from the selection widget. This might take a little trial and error to figure
out. Maybe try, if it is a treeview,
Erc,
On Sun, Sep 24, 2017 at 7:17 PM, wrote:
>
> Igor,
>
> It sounds like you are determined to hack at this. I would recommend the
> newer GtkFontChooserWidget but OK. The PangoFcFamily* isn't much help. You
> need to get your widget pointers and setup up callbacks on your
On Sun, Sep 24, 2017 at 10:54 PM, wrote:
>
> A widget has encapsulated functionality that the designer of the widget does
> not expect you to use or see in your application code. Changing a "private"
> widget may have negative consequences for how the widget works. If a widget
A widget has encapsulated functionality that the designer of the widget does
not expect you to use or see in your application code. Changing a "private"
widget may have negative consequences for how the widget works. If a widget
doesn't have the functionality that you need then file a
Eric,
Why am I breaking the design?
Is it illegal to do?
Thank you.
On Sep 24, 2017 7:17 PM, wrote:
>
> Igor,
>
> It sounds like you are determined to hack at this. I would recommend the
> newer GtkFontChooserWidget but OK. The PangoFcFamily* isn't much help. You
> need to
Igor,
It sounds like you are determined to hack at this. I would recommend the newer
GtkFontChooserWidget but OK. The PangoFcFamily* isn't much help. You need to
get your widget pointers and setup up callbacks on your treeviews. Maybe all
you need is to connect a "row-activated" to know if
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
Eric,
On Sun, Sep 24, 2017 at 1:47 PM, Igor Korot wrote:
> Eric,
>
> On Sun, Sep 24, 2017 at 1:51 AM, Igor Korot wrote:
>> Eric,
>>
>> On Sun, Sep 24, 2017 at 12:33 AM, wrote:
>>>
>>> When I test it out it looks like the font selection
> 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
Eric,
On Sun, Sep 24, 2017 at 1:51 AM, Igor Korot wrote:
> Eric,
>
> On Sun, Sep 24, 2017 at 12:33 AM, wrote:
>>
>> When I test it out it looks like the font selection widget doesn't work very
>> well in GTK3.
>>
>> Not quite sure how you have it setup for
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
12 matches
Mail list logo