dx-packages team mailing list archive

[Marc-Andre Laperle <1188831@xxxxxxxxxxxxxxxxxx>]

also fixes https://bugs.eclipse.org/bugs/show_bug.cgi?id=368929

** Bug watch added: Eclipse bugs #368929
   https://bugs.eclipse.org/bugs/show_bug.cgi?id=368929

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to overlay-scrollbar in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1188831

Title:
  Scrollbar not visible when it's the only child in a container

Status in Overlay Scrollbar:
  New
Status in “overlay-scrollbar” package in Ubuntu:
  Triaged

Bug description:
  Using Ubuntu 13.04 (overlay-scrollbars
  0.2.16+r359daily13.02.06-0ubuntu1). We have a GtkScrollbar that is
  managed "manually" in it's own container (GtkFixed). The size of the
  scrollbar is requested in order to allocate the right size for the
  container. However, because overlay scrollbar always request 0 width
  (or height for horizontal), the container is shrunk and the scrollbar
  is not visible. So, I think the scrollbar should at least request
  BAR_WIDTH when it knows it's alone in a container. There is also a
  problem with the scrollbar getting allocated to 0 position (x or y)
  and then being offset to -3 (BAR_SIZE) in
  hijacked_scrollbar_size_allocate. I think those should be clamped to
  be >= 0.

  A bit of background:
  The application demonstrating this bug is Eclipse using the Lttng plug-in. Eclipse uses the SWT library which interfaces with GTK. It maps GridLayout (a bit like a table) to GtkFixed containers. It allocates the cells by requesting the size of gtk widgets (gtk_xyz_size_request) then allocating the container size. The bug appears in the TMF events editor because a virtual table is used so the scrollar bar has to be managed "manually" in its own container.

  I will submit a fix and screenshots.

To manage notifications about this bug go to:
https://bugs.launchpad.net/overlay-scrollbar/+bug/1188831/+subscriptions