On 07 Nov 2014, at 21:02, Tudor Girba <tudor@tudorgirba.com> wrote:
Hi Sven,
Neither of these requests are being ignored (see the other two replies), but good things take time.
So the editing is coming, super.
We would be happy to get more contributors :).
So how are we going to make the inspectors really live ? The old inspectors had this busy loop (well part of the morph step protocol) for updating. I am sure I do not have to explain why we need this. Before, it was maybe not efficient (enough) and you said it would be too expensive for large computations. So what is the solution ? An opt-in or opt-out mechanism ? Per object, per presentation ?
Doru
-- www.tudorgirba.com
"Every thing has its own flow"
On 07 Nov 2014, at 19:31, Sven Van Caekenberghe <sven@stfx.eu> wrote:
It simply has to be possible to edit values and to see live updates, there is no way around it - else the GT inspector looks at dead objects, bye bye live programming.
I think it is not cool that this is being ignored.
On 07 Nov 2014, at 19:24, Alexandre Bergel <alexandre.bergel@me.com> wrote:
This is strange, I do not remember to have use this when I was using the old inspector. I usually trust what the inspector tells me only having open one.
Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Nov 7, 2014, at 12:40 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
Yes, editing state and inspectors need to be updated so you see live how value are changing even when they are changed from somewhere else.