[Gtk-sharp-list] ScrolledWindow and TextView

[Michael Hutchinson]

On Sat, Jun 28, 2008 at 8:14 PM, Jestin Stoffel
<jestin.stoffel at gmail.com> wrote:
> On Sat, 2008-06-28 at 17:26 -0400, Michael Hutchinson wrote:
>> On Sat, Jun 28, 2008 at 5:03 PM, Jestin Stoffel
>> <jestin.stoffel at gmail.com> 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.
>
> Works like a charm.  Thanks.
>
>>
>> This is clearly a bug in stetic; could you file a bug report?
>
> I checked, and it looks like there is already a report for this:
>
> https://bugzilla.novell.com/show_bug.cgi?id=323770
>
> However, it says that the issue was resolved in svn as of 2007-03-28
> (before the 1.0 release).  Do you think I should re-open it (not sure if
> I can even do that), or start a new bug?

Since it's been so long since the bug was closed, it'd probably be
best to open a new bug.

-- 
Michael Hutchinson
http://mjhutchinson.com