55 links is the "cap" (maximum) - please help

[d.andrew STEWART]

Hello everyone

55 links is the "cap" (maximum) when loading into Webmapper. 

I can create more than 55, in Webmapper, and save the JSON file.  I currently have a mappings file with 56 "Destinations", which I can verfiy by opening the JSON and counting then number of "Destinations". However, when I load the file into Webmapper (GUI), it caps at 55?

Suggestions?  I will try saving 56 mappings in separate JSON files

D> 

[d.andrew STEWART]

I went back to an earlier mappings file (53 Mappings) and then, rebuilt – gradually adding one mapping at a time. It seems I can surpass 55.  I now have 57 mappings; however, there is some inconsistency.  When I load the 57-mapping JSON, sometimes it works, sometimes I only get 56 connections realised.  I'll keep monitoring the situation to try to find a consistent pattern. Could this issue be related to speed limits and timing of messaging within the programming? Please advise

[Joseph Malloch]

Hi Andrew,

I responded to this question on Friday but perhaps you missed it – the file you provided contains 1 map where the destination is the webmapper “monitor” input. This map should not have been saved and it is the correct behaviour for the map to fail to load since this destination is handled privately by webmapper when you click the monitor button for a signal. This map is used only for webmapper to display the signal values.

The next version of mappersession will have better tests to exclude monitor maps from being saved, but for now they may be included if the monitor is open when you save the mapping.

There is NOT a cap of 55 maps :)

Cheers,

Joe

--
You received this message because you are subscribed to the Google Groups "dot_mapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dot_mapper+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dot_mapper/fc2ee05f-06d2-48e6-abed-053909bc7466n%40googlegroups.com.

[d.andrew STEWART]

Thanks for reply, regarding "monitor input".  I'm not exactly sure what this is and , thus, I do not fully understand; however, I'll look at this weekend. Send screenshot to help, if that makese sense to do. 

I guess the question is: how did I `accidentally` map to the monitor input?

 I do know, however, that on sevearl occasions, one mapping connection was missing (consistently).....I'll keep exploring... Thanks again.

[Joseph Malloch]

Hi Andrew,

Briefly: Webmapper also registers itself as a hidden device with one signal named “monitor”. If you click one of the little mouseover eye icons on a signal in list view it will open a rudimentary signal visualizer and show live updates of the signal’s value. In order to get these values webmapper creates a map from the signal you want to view to its own “monitor” signal. This map shouldn’t be included in saved files but in your case it was… the next version of mappersession will include better checks to ensure the map is not included.

Cheers,

Joe

To view this discussion visit https://groups.google.com/d/msgid/dot_mapper/9699b572-2b4b-4d37-8c81-99e65919252an%40googlegroups.com.