I'm a newcomer to wxPython (and GUI programming in general). I'm also
almost completely blind, so creating good-looking interfaces is often
not a walk in the park.
I have attached a simple example program, consisting of a read-only
multi-line text control and two buttons. In the call to
wx.Frame.__init__(), I have specified a size, as using the defaults
seems to create a ridiculously small window. However, sighted users
report that the text in the window is too small, so small as to be
unreadable. If I omit the size parameter and then resize the window
manually, the text is readable, and everything looks as it should (with
the two buttons underneath the text control, aligned to the left and right).
Could anybody tell me where I'm going wrong? I have a feeling I've
messed up somewhere when writing the code for my sizers; it was
suggested that I call sizer.Fit() but when I did that, the buttons
disappeared.
Odd -- it works great for me, either with or without specifying an
initial size for the Frame.
Ans i"m confused, initial size and/or doing sizers oddly shouldn't
change the size of the text itself, only the size of widgets and how
they are laid out.
On Thu, Mar 14, 2013 at 2:24 PM, James Scholes <james@jls-radio.com> wrote:
I have attached a simple example program, consisting of a read-only
multi-line text control and two buttons. In the call to
wx.Frame.__init__(), I have specified a size, as using the defaults
seems to create a ridiculously small window. However, sighted users
report that the text in the window is too small, so small as to be
unreadable. If I omit the size parameter and then resize the window
manually, the text is readable, and everything looks as it should (with
the two buttons underneath the text control, aligned to the left and right).
Could anybody tell me where I'm going wrong?
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Windows 7 X64, Python 2.7.2, wxPython 2.9.4.0. Running your code
without a size supplied to the frame constructor results in an
absolutely tiny window.
I'm a newcomer to wxPython (and GUI programming in general). I'm also
almost completely blind, so creating good-looking interfaces is often
not a walk in the park.
I have attached a simple example program, consisting of a read-only
multi-line text control and two buttons. In the call to
wx.Frame.__init__(), I have specified a size, as using the defaults
seems to create a ridiculously small window. However, sighted users
report that the text in the window is too small, so small as to be
unreadable. If I omit the size parameter and then resize the window
manually, the text is readable, and everything looks as it should (with
the two buttons underneath the text control, aligned to the left and right).
Could anybody tell me where I'm going wrong? I have a feeling I've
messed up somewhere when writing the code for my sizers; it was
suggested that I call sizer.Fit() but when I did that, the buttons
disappeared.
I think Chris gave you the answers on your original code.
Attached is an alternative way of doing it using my favorite way of dealing with sizers, i.e. using wx.lib.sized_controls and I also added the WIT - which is very helpful for debugging sizer issues.
Windows 7 X64, Python 2.7.2, wxPython 2.9.4.0. Running your code
without a size supplied to the frame constructor results in an
absolutely tiny window.
The default size of a frame is something like 400x250 pixels, which is not necessarily "absolutely tiny" for a sighted person depending on what the content of the frame is, but which I expect it could certainly be considered to be tiny by a vision impaired person.
The layout in the sample scripts is correct for how the code is written, but I'm guessing that James is expecting something different. It does look a little odd when the window size is increased because the normal sized labels are then sitting inside of a very large empty space, and that is probably what was meant by those who said that the text looked tiny. James, if you are wanting the size of the text to also increase as the space around them increases then you will need to manage that in the code. wxWidgets does not automatically scale the font sizes of labels to fit the widget. That is doable in the application code, but that may look odd for a sighted person too.
On the other hand, if you want the application to look normal for a sighted person but still be large enough to display your results, then one easy change to make would be to use a zero for the proportion parameter when adding the horizontal sizer to the vertical sizer. That will keep the buttons from expanding vertically and to stay at their default height.
On the other hand, if you want the application to look normal for a
sighted person but still be large enough to display your results, then
one easy change to make would be to use a zero for the proportion
parameter when adding the horizontal sizer to the vertical sizer. That
will keep the buttons from expanding vertically and to stay at their
default height.
I implemented your suggestion into my main program, generated some
results and took a screenshot of the main window (attached). While this
isn't a code-related question per say, are the results inside the
TextCtrl and the text of the buttons readable? In short, does the
window look normal/usable?
On the other hand, if you want the application to look normal for a
sighted person but still be large enough to display your results, then
one easy change to make would be to use a zero for the proportion
parameter when adding the horizontal sizer to the vertical sizer. That
will keep the buttons from expanding vertically and to stay at their
default height.
I implemented your suggestion into my main program, generated some
results and took a screenshot of the main window (attached). While this
isn't a code-related question per say, are the results inside the
TextCtrl and the text of the buttons readable? In short, does the
window look normal/usable?
The "Save to file" button is stuck in the upper-left corner and is underneath the results label, so it probably was accidentally removed from its sizer. Other than that it looks good to me.
The "Save to file" button is stuck in the upper-left corner and is
underneath the results label, so it probably was accidentally removed
from its sizer. Other than that it looks good to me.
The "Save to File" button isn't shown until the user selects a valid
folder and the results have been loaded. I added a call to
BoxSizer.Layout after the call to Button .Show, which has hopefully
fixed the problem (hopefully I called Layout on the correct Sizer!).
Screenshot is attached.
The "Save to file" button is stuck in the upper-left corner and is
underneath the results label, so it probably was accidentally removed
from its sizer. Other than that it looks good to me.
The "Save to File" button isn't shown until the user selects a valid
folder and the results have been loaded. I added a call to
BoxSizer.Layout after the call to Button .Show, which has hopefully
fixed the problem (hopefully I called Layout on the correct Sizer!).
Screenshot is attached.
Thanks again for all the help on this.
Ok. Yes, everything looks good in the 2nd screenshot.
Do you call Hide() on that button when it is created? If so then what I saw in the other screenshot may just be a Windows glitch and perhaps adding a wx.CallAfter(self.panel.Refresh) will help, so it gets an extra refresh after the frame is first shown.
The "Save to file" button is stuck in the upper-left corner and is
underneath the results label, so it probably was accidentally removed
from its sizer. Other than that it looks good to me.
The "Save to File" button isn't shown until the user selects a valid
folder and the results have been loaded. I added a call to
BoxSizer.Layout after the call to Button .Show, which has hopefully
fixed the problem (hopefully I called Layout on the correct Sizer!).
Screenshot is attached.
Thanks again for all the help on this.
Don't like to disagree with Robin:-) , but the statictext "Results" takes up too much space.
