26 Jan
2004
26 Jan
'04
12:23 p.m.
From: torbenh(a)gmx.de
[ gnomecanvas ]
the only problem would be determining widget size when
you add a widget
to the canvas. gtk behaves sort of strange there.
[ Posted this to gtk-app-devel-list as well. Reply to where you wish
as I will summary. ]
Should the module widgets be put to a fixed size container before
they are inserted to the canvas? Or what is the problem?
I tested with Glade: created a top window with one "Fixed Position"
container widget, added viewport to the "Fixed Position", inserted
vbox to viewport, inserted horizontal scales to each slot of the vbox.
Then I took the properties of the viewport and changed viewport's
position and size. Only problem appeared when the viewport size
was made smaller than the minimum size of all scales. Viewport could
be made very small in which case the scales were clipped agains the
viewport.
Is there any way to determine when the viewport becomes smaller than
the vbox holding the scales? (Or the vbox larger than the viewport.)
Does the viewport generate any signals in these cases?
Is the viewport a wrong widget for the task? Is there any other constant
size container in GTK?
Regards,
Juhana
26 Jan
26 Jan
2:19 p.m.
From:
torbenh(a)gmx.de
[ gnomecanvas ]
the only problem would be determining widget size
when you add a widget
to the canvas. gtk behaves sort of strange there.
[ Posted this to gtk-app-devel-list as well. Reply to where you wish
as I will summary. ]
Should the module widgets be put to a fixed size container before
they are inserted to the canvas? Or what is the problem? Is the viewport a wrong widget for the task? Is there
any other constant
size container in GTK?
GtkLayout is the correct widget to use. But like all GTK containers,
it is not intended to handle overlapping widgets, although it can do
so under some circumstances.
--p
27 Jan
27 Jan
3:37 a.m.
On Mon, Jan 26, 2004 at 01:16:18PM -0500, Paul Davis wrote:
widgets on the canvas are second class citizens. don't go there.
all of GTK is slowly migrating toward a client-side compositing model
based on Cairo. do not expect the GTK crew to be supportive of any
attempts to fix up the existing canvas/widget dichotomy.
where do i fond info on that ?
the widget added last is displayed on top.
could work ok if one sorted the child list by hand.
note that there are also issues when adding widgets to a GtkLayout which
is not mapped.
but after half a year of sporadic fiddling i fixed it.
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language
From: torbenh(a)gmx.de
[ gnomecanvas ]
the only problem would be determining widget size
when you add a widget
to the canvas. gtk behaves sort of strange there.
[ Posted this to gtk-app-devel-list as well. Reply to where you wish
as I will summary. ]
Should the module widgets be put to a fixed size container before
they are inserted to the canvas? Or what is the problem? Is the viewport
a wrong widget for the task? Is there any other constant
size container in GTK?
GtkLayout is the correct widget to use. But like all GTK containers,
it is not intended to handle overlapping widgets, although it can do
so under some circumstances.
7401
days inactive
7402
days old
linux-audio-dev@lists.linuxaudio.org
2 comments
3 participants
participants (3)
-
Juhana Sadeharju -
Paul Davis -
torbenh＠informatik.uni-bremen.de