|
|
|
Re: Composite.redraw() - Does it work or not? [message #527406 is a reply to message #527381] |
Thu, 15 April 2010 03:38   |
Eclipse User |
|
|
|
Hi,
see my comments below:
Bassspieler wrote:
> The main error was on my side. I told my model in my TableViewer to
> refresh and wanted to handle the data on the next line of code. But this
> was just wrong. I had to add a Listener to my model, that triggers, when
> all the data was provided.
To better understand how to work with TableViewers, have a look at the
JFace examples in the wiki, e.g. [1].
> But it is still interesting for my, what redraw stands for. What code is
> in there? You said it does the same as "computeSize".
No, I said that using redraw() makes no difference for computeSize(),
not that it would do the same!
As I said, redraw() makes sense on other platforms, that use the
operating system to draw. I think the JavaDoc is pretty clear, so what
is your question?
> But computeSize
> does nothing, does it? It just computes a size, but does not set any
> values to a widget or something like that.
computeSize() may use caching, but does not have other side effects.
Best regards,
Ralf
[1]
http://wiki.eclipse.org/index.php/JFaceSnippets#Snippet029Vi rtualTableViewer
|
|
|
|
Re: Composite.redraw() - Does it work or not? [message #527455 is a reply to message #527448] |
Thu, 15 April 2010 06:38  |
Eclipse User |
|
|
|
Bassspieler wrote:
> ;) My question is: What "physically" happens in RAP, when I call this
> method? Is it like:
>
> public void redraw(){
> // just for API
> }
yes
>
> or is it more like:
>
> public void redraw(){
> this.pack();
> this.layout();
> }
|
|
|
Powered by
FUDForum. Page generated in 0.04418 seconds