Open GoogleCodeExporter opened 9 years ago
This happens in QA
Original comment by JBWagenaar
on 8 Jul 2013 at 1:34
Original comment by samd.p...@gmail.com
on 9 Jul 2013 at 5:27
Original comment by samd.p...@gmail.com
on 7 Aug 2013 at 6:21
Original comment by samd.p...@gmail.com
on 14 Aug 2013 at 5:29
[deleted comment]
the trick here is to highlight the dataset in the Dataset Explorer before
expanding it. Then you'll see them.
Original comment by samd.p...@gmail.com
on 1 Oct 2013 at 5:24
I believe this only works if you do it right the first time. If you click on
arrow first, and see nothing, then close tree and select dataset, it still does
not show the results (caching?).
Also, what happens if people derive new datasets? Do you get appended or are
they only visible after you relog in?
Original comment by JBWagenaar
on 1 Oct 2013 at 8:19
Original comment by zack.i...@gmail.com
on 8 Oct 2013 at 11:59
Original comment by john.fro...@gmail.com
on 9 Oct 2013 at 7:43
still an issue as of r3206
Original comment by samd.p...@gmail.com
on 9 Oct 2013 at 7:47
Original comment by samd.p...@gmail.com
on 9 Oct 2013 at 7:48
you need to select one of the datasets first in the view to populate the
derived datasets. If you first hit one of the exapand arrows you don't see the
derivations.
Original comment by samd.p...@gmail.com
on 9 Oct 2013 at 7:55
Problem is that if you don't do that the first time, you'll never be able to
see them until you log out and log back in.
Original comment by JBWagenaar
on 9 Oct 2013 at 7:57
Weird, I am not seeing this at all in my local version. I did a search, then
looked at Studies 6, 10, etc. by clicking on the triangle, and there were
values even in the absence of specifically highlighting the item. This was in
Firefox.
Original comment by zack.i...@gmail.com
on 9 Oct 2013 at 8:26
So far as I can tell upon further investigation, this is a GWT bug and we'll
have to come up with a workaround. Looks like there is a way of doing fully
dynamic CellTrees and I'll look at it.
Original comment by zack.i...@gmail.com
on 11 Oct 2013 at 4:58
Original issue reported on code.google.com by
JBWagenaar
on 8 Jul 2013 at 1:33