On 7/6/05, Jose de Paula Eufrasio Junior <[EMAIL PROTECTED]> wrote: > Hello there, > > I'm making a pygtk app and got several fields wich values are inserted > (like textviews, spinbuttons) and these values can be changed with > values from other widgets on the app.
> I'm not very friendly to the idea of a 'refresh' button, and like to > know from you guys what's the best manner to do it... I'm not sure I understand your question. Do you mean that a value in Entry A will change the value in Entry B or somesuch? If there is a direct relationship, I would enforce that relationship essentially instantaneously. That said, if the user can't infer why the limitations are being inforced, it could be quite frustrating to have values changing suddenly, especially values they typed in -- you might want to search the archives for some work on Entry validation that you could use to pop up a non-intrusive warning about conflicting Entries (if Entry A makes Entry B a non-valid choice). Anyway, if I understand your question correctly, I'd say the correct thing to do is make your application instantly validate and update the interface and make Undo easily available for the cases where a user has not intended the results they got (if putting $500 into the "Expenses" widget" makes the "Savings" widget change to $0, for example). Of course, more details would help us give better suggestions for your particular case. Tom _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
