Miss behaviour of EmberPlusViewer 1.1.3

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start TinyEmberPlus.exe and open the attached Test.EmBER
2. Start EmberPlusViewer.exe and open a connection to TinyEmberPlus
3. Browse to the parameter 'MyParameter' and select it
4. Adjust the minimum of 'MyParameter' from 0 to 4 (by using the up arrow)
5. Activate now the EmberPlusViewer window by clicking e.g. in the title bar 

What is the expected output? What do you see instead?
1. When changing the minimum, i expect the minimum to be updated in the 
consumer (EmberPlusViewer), which is not the case (or not visible).
2. On step 5. the EmberPlusViewer updates the value on the provider by setting 
it to the new minium.

I could verify 2. to happen also with one other provider.

Please provide any additional information below.
The EmberPlusViewer from here (v1.1.3): 
https://groups.google.com/d/msg/ember-plus-discuss/Hp2bzni-FXs/g7hoSCjnFBwJ
The TinyEmberPlus from the SDK 1.2.0

Original issue reported on code.google.com by nullable...@gmail.com on 29 Apr 2013 at 8:16

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Added missing Test.EmBER file.

Original comment by nullable...@gmail.com on 29 Apr 2013 at 8:19

Attachments:

• Test.EmBER

[GoogleCodeExporter]

Similar behaviour experienced with EmberPlusViewer 1.1.2. When clicking in the 
tree view on a parameter, value change requests are sent to the provider.

Original comment by nullable...@gmail.com on 29 Apr 2013 at 8:26

[GoogleCodeExporter]

It is even worse - it seems that value change requests with the previous 
clicked parameter value are sent.

Original comment by nullable...@gmail.com on 29 Apr 2013 at 8:35

[GoogleCodeExporter]

Sorry, I cannot reproduce this issue. When following steps 1 to 5 I always see 
the correct minimum value.
The reason for the parameter update is the following:
- default slider value is the parameter's minimum
- when the minimum is changed, the slider values gets changed which triggers a 
notification.
- this does not happen when you change the parameter value using the slider 
before changing the parameter's minimum.
Best regards,
Philip

Original comment by p...@l-s-b.de on 29 Apr 2013 at 9:28

[GoogleCodeExporter]

Ok, about point 1. of the expectations: I recognize, that the minium value is 
applied after leaving the focus of the minimum value text field (in 
TinyEmberPlus). That explains, why the minimum value is not transfered to 
consumer when just using the up and down arrows (controled by the mouse).

I think, the slider problem explains point 2.

So, it would be better if the slider is set to the position of the actual value 
retrieved from the provider.

Original comment by nullable...@gmail.com on 29 Apr 2013 at 11:24

[GoogleCodeExporter]

Another story is this:
1. Start TinyEmberPlus.exe and open the attached Test2.EmBER
2. Start EmberPlusViewer.exe and open a connection to TinyEmberPlus
3. Browse to the parameters by clicking the small arrows in the 
EmberViewerPlus, the values are:
-> 001, MyParameter, 8
-> 002, MyStringParam, text
4. Adjust the minimum of 'MyParameter' to 4
5. Select 'MyParameter'
6. Select 'MyStringParam' in the EmberViewerPlus and the value changes from 
text to 0

Original comment by nullable...@gmail.com on 29 Apr 2013 at 11:36

Attachments:

• Test2.EmBER

[GoogleCodeExporter]

I got #7 reproduced, thanks for the report! Next version will bring improvement 
here...

Original comment by p...@l-s-b.de on 30 Apr 2013 at 1:49

[GoogleCodeExporter]

Original comment by Kimon.Ho...@lawo.com on 2 May 2013 at 3:31

• Added labels: Component-TinyEmberPlus, Milestone-Release1.2

[GoogleCodeExporter]

Original comment by Kimon.Ho...@lawo.com on 2 May 2013 at 3:35

• Changed state: Started

[GoogleCodeExporter]

Fixed in version 1.2.0

Original comment by p...@l-s-b.de on 2 May 2013 at 3:38

• Changed state: Fixed