| AW: AW: [geclipse-dev] Filesystem bug(s) |
|
I’ll have a look at it
right after fixing the no-children-bug ;-) This will be a long day … Von:
geclipse-dev-bounces@xxxxxxxxxxx [mailto:geclipse-dev-bounces@xxxxxxxxxxx] Im Auftrag von Harald Gjermundrod Hi Mathias You are right about the re-loading, it doesn't get refreshed. The
problem is that when you use the setChildCount method it crashes the
application. Is there another way to clear out the content of the subtree then
to use the setChildCount? Thanks, Harald On Feb 27, 2008, at 3:31 PM, Stuempert, Mathias IWR wrote:
Hi Harald, Unfortunately your fix
leads to the behaviour that once loaded contents are never reloaded again since
the resource tree is not reset. At least for me on windows when expanding a
node the first time the children get fetched. Collapsing this node and expanding
again does not fetch the children again but does simply show the result of the
former fetch. This means that if in the meantime the content of the code
changed online you will not recognise this in your workspace. Actually I believe that
this should also be the behaviour on Linux and MacOS since these parts should
not be OS dependent. Please have a close look if really everything gets
refreshed/reloaded when re-expanding a node. Cheers, Mathias Von: geclipse-dev-bounces@xxxxxxxxxxx
[mailto:geclipse-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Harald
Gjermundrod Hi All, I did a small fix to
make the collapsing on the tree work on the Mac OS X platform. I tested this
out on Linux and Mac and it works, so I committed it. Please test it out on
Windows as-well. In eu.geclipse.ui.providers.GridModelContentProvider::treeCollapsed I
commented out the following lines. //this.treeViewer.setChildCount(
element, 0 ); //this.treeViewer.setChildCount(
element, 1 ); PS: No
problems found except the known issue. On Feb 27, 2008, at 2:33 PM, Stuempert,
Mathias IWR wrote:
Hi All, I just committed a fix
that should at least partially solve the problems with the virtual nodes. Those
of you that did experience problems with connections and resource nodes please
update core and ui and test the fix. Please report back ASAP if this helps. One known issue is still
there. If you are opening a node without any children the fetching stops with
the progress bar at 100% but the progress bar does not disappear. Since this is
a known bug I am already working on don’t report this ;-) Cheers, Mathias _______________________________________________ _______________________________________________ |