Eric Jardim wrote: > On 7/4/05, *Paul Malherbe* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > What I would like to do, when this occurs, is display a TextView > widget > directly under the Entry widget and display each character entered so > that with the formatting facilities of the TextView the operator would > be able to view all the text. Once the text has been accepted, the > TextView would be deleted. > > > Sounds easy. Lay out your widgets on a VBox, with the Entry above the > TextView. Set the textview's visibility to false. Connect signal to > the Entry, so you can detect when it's text length is greater than 150 > chars. > > When it happens, copy the text to the textviews buffer and set the > visibility to true. And it will apear "magicaly" under the Entry. > > But this approach might not be intuitive for the user. You should try > something like a button aside of the Entry which turns it into a > TextView, or pops up a TextView dialog, or something like that. > > Anyway, does this trick help? > > [Eric Jardim]
Hello Eric Yes, thank you, this does help where I can use a vertical box. In some instances, however, I have a table with many rows and columns and it is here that I have the width constraints e.g. capturing transactions where I have the date, reference number, details, amount, discount etc and the details field can be 150 characters long. In this case I would like to create a TextView and place it under the details field as and when required i.e. when the data entered exceeds the widget width. Can you think of any way I could achieve this. Thanks, Paul _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
