kOoO Test

[kOoO]

Hi,

attaching my notes after some random clicking

[Daniel]

1. Use Ctrl
2. In the pipeline.
3. We think this is fine
4. This was never planed and will not be implemented.

[kOoO]

1. More intuitive way for me was to try to select more objects by mouse. I can't even think of any grid/map interface that allows users to drag and drop elements by mouse, but doesn't allow them to select multiple elements by mouse.
4. This means, that after firmware upgrade, all old visualizations needs to be manually reworked into new visualizations? Or is it just about import? What's the reason that old visualization structure can't be transformed into the new one? Or at least some part of it? I think this is pretty crucial part as it would save a ton of man hours if users wouldn't have to redo the same work again!

[Daniel]

4. New visu combine two in one. It is not one to one conversion. Most users just need to import the icons. Old visu can still be used next to new one. Some transition period is needed.

[kOoO]

"two in one" - you mean visualization (plan/element) settings + visualization parameters of objects? That would make sense since old visu export doesn't contain objects' visparams. Those would have to be either defaulted or taken from actual objects (during the transition period) if such import was supported.

But now regarding firmware upgrade (or import of old project backup into new firmware with new visu), new visu will be prefilled with data from old visu (+ object "visparams" settings) or will it be completely empty? Because in this case there should not be any problem with creating the new visu structure based on old data, right?

[Daniel]

Old visu + Mosaic(Touch) = new Visu
There will not be any conversion tool. Old visu + Mosaic will coexist for some time with new visu and at some point they will be removed.

[kOoO]

Ok, clear.

Attaching some other findings, mostly details.

[kOoO]

What about object custom values? Will they be used or only the values defined in new visu will be relevant? (if latter, maybe could be at least prefilled) Probably related only to "Numeric value display (read-only)" widget.

[Daniel]

Custom values are there already. Additional values/icons....

[kOoO]

Which means that the ones defined Configurator->Objects->Custom values are ignored? That would mean some extra work for users to keep track of those custom values on more places. A some kind of "use by default, but possible to override" functionality could be nice.

[Daniel]

As I explain you already we integrating two visus into one and some functionality we had to choose to use one or another way. In this case Mosaic wins as we want to use full widgets capabilities. This gives you much more freedom as you can display same object in many ways.

[kOoO]

Giving users option like this could give them even more freedom:
   

Since the object's custom values only exist only for display/visualization purposes, it may be safe to say that in most cases, that's what will users want to see in their visualizations.

[Daniel]

We will consider this, thanks.