Problem 1:
wx.ScrolledWindow shows the scrollbars even if they are not needed.
uncommenting line 27 of the attached file "fixes" the problem. Is this the way it's supposed to work?
Problem 2:
this is eating me for some time:
What does wx.Window.SetSize() means? What does it suppose to do? because it most certainly doesn't set the size, not for some time.
replacing line 10 from the attached file with:
self.SetSize((400, 600))
shows what I'm talking about.
Problem 3:
With the unnecessary scrollbars visible I drag the horizontal scrollbar to max right. Now I can see and use the inner scrollbar of the second(right) ListBox BUT the inner scrollbar of the first ListBox is frozen (it cannot be grabbed)
Problem 1:
wx.ScrolledWindow shows the scrollbars even if they are not needed.
uncommenting line 27 of the attached file "fixes" the problem. Is this the way it's supposed to work?
I think the width of the scrollbars is factored in to the calculation for when to show them and when to hide them. Once the scrollbars are shown (when the client size is smaller than the virtual size) the window has to get larger than the virtual size plus the scrollbars before they will be hidden again. Look at this file for the gory details:
You can find the size of the scrollbars from wx.SystemSettings if you want to try and calculate things out.
Problem 2:
this is eating me for some time:
What does wx.Window.SetSize() means? What does it suppose to do? because it most certainly doesn't set the size, not for some time.
replacing line 10 from the attached file with:
self.SetSize((400, 600))
shows what I'm talking about.
SetSize has very little meaning when the window is managed by a sizer. No matter what you set the size to be the sizer is going to resize is acccording to its rules. One of the rules that it follows however is to honor the minsize of the window which is why SetMinSize works for you.
Problem 3:
With the unnecessary scrollbars visible I drag the horizontal scrollbar to max right. Now I can see and use the inner scrollbar of the second(right) ListBox BUT the inner scrollbar of the first ListBox is frozen (it cannot be grabbed)
It works here.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
A look at this page reinforce my urge to buy a "I love Guido" poster
Problem 3:
With the unnecessary scrollbars visible I drag the horizontal scrollbar to max right. Now I can see and use the inner scrollbar of the second(right) ListBox BUT the inner scrollbar of the first ListBox is frozen (it cannot be grabbed)
It works here.
Well... I still think this is some kind of a bug.... More details:
I make the window smaller so I can scroll more... this results in the following:
if I move the horizontal scroll bar one step to the right first list's scrollbar cannot be grabbed
if I move the HScroll one more step to the right the first list's scrollbar still doesn't work BUT if I move it to the left, back where it was after the first move, the first list's scrollbar works. If at any time I move the VScroll bar the fist list's scrollbar becomes "active". Even when the scrollbar cannot be grabbed it can still be moved with the wheel of the mouse or with the keyboard (page down for example)
Moving the HScroll to the far right shows that the second list's scrollbar works BUT if I add a button after the lists.... ooops it doesn't work anymore.
Further more when moving the HScroll to the left only the first list's scrollbar gets "activated", the second list's scrollbar stays "frozen" unless the HScroll is at its left end case in which the both lists work. This "moving to the left" behaviour is not consistent, playing around with the size of the frame and with the HScroll can create situations where the fist list doesn't work and the second works OR when both work HOWEVER "moving to the right" ALLWAYS freezes both lists scrollbars.
Weird Stuff!
···
On Tue, 10 Aug 2004 09:10:25 -0700, Robin Dunn <robin@alldunn.com> wrote:
