Re: Change components of JPanel autonomously and simultaneously

2012-01-31 Thread Dave Ray
Calling repaint directly on the panel (not the frame) should be all that's necessary to update the display. updateComponentTreeUI() is only used when the look and feel of an app changes. Dave On Tue, Jan 31, 2012 at 8:44 AM, Jonathan Cardoso wrote: > I used   (SwingUtilities/updateComponentTreeU

Re: Change components of JPanel autonomously and simultaneously

2012-01-31 Thread Jonathan Cardoso
I used (SwingUtilities/updateComponentTreeUI *frame*), worked great and seems faster even without using watch yet. Thank's -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that post

Re: Change components of JPanel autonomously and simultaneously

2012-01-31 Thread Jonathan Cardoso
Thank's, I will try to adapt my code to use watch (I didn't know this feature and found it really interesting!). The problem with JPanel repaint is that, I don't surely know why but the JFrame doesn't "understands" it when I change and has an awkward behavior: if I click on the button that make

Re: Change components of JPanel autonomously and simultaneously

2012-01-31 Thread Dave Ray
> ;; This is how I repaint the frame, after changing the list > (doto *frame* >       (.setContentPane (make-panel)) >       .repaint >       (.setVisible true)) > This is probably the reason it's slow (you don't say how many rects you're drawing). It's only necessary to set the content pane of th