On Sat, Jun 28, 2008 at 5:03 PM, Jestin Stoffel <[EMAIL PROTECTED]> wrote: > Apparently there is a Gtk.Viewport that gets created, and that is what > the ScrolledWindow contains. Checking the gui.stetic file showed that > Stetic is adding in the Viewport. It seems that Stetic automatically > assumes add_with_viewport instead of a normal add, and creates a > Viewport in gui.stetic. Since a TextView is something that handle's > it's own scrolling, this Viewport is just mucking things up. Thanks for > pointing me in the right direction, but I still don't know how to use > the Stetic designer to accomplish a TextView inside a ScrolledWindow. I > looked for some sort of configuration option, but couldn't find one. I > can probably just work around the issue by creating a custom > "scrolledtextview" widget where I do my add()'s in code (without > Stetic), but it is starting to look like there's a bug somewhere.
Actually, I just played around with textviews in stetic, and discovered that adding a textview to a container that's not a ScrolledWindow *automatically* adds a ScrolledWindow without a viewport. Adding a textview to a ScrolledWindow does insert a viewport, which can be seen in the .stetic file (xml) but is not accessible from the designer. Fortunately the workaround is simple; just skip adding the scrolledwindow. This is clearly a bug in stetic; could you file a bug report? -- Michael Hutchinson http://mjhutchinson.com _______________________________________________ Gtk-sharp-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/gtk-sharp-list
