Changes between Version 2 and Version 3 of MapGuideRfc157


Ignore:
Timestamp:
Apr 11, 2017 6:44:41 AM (8 months ago)
Author:
jng
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc157

    v2 v3  
    88||RFC Template Version||(1.0)||
    99||Submission Date||9 Feb 2017||
    10 ||Last Modified||4 Apr 2017||
     10||Last Modified||11 Apr 2017||
    1111||Author||Jackie Ng||
    12 ||RFC Status||draft||
    13 ||Implementation Status||discussion||
     12||RFC Status||Adopted||
     13||Implementation Status||Pending||
    1414||Proposed Milestone||3.3||
    1515||Assigned PSC guide(s)||(when determined)||
     
    156156
    157157Community
     158
     159== Addendum, 11 April 2017 ==
     160
     161It has been discovered using {{{QueryFeatures}}}, that the {{{MgFeatureInformation}}} returned has a {{{MgSelection}}} that cannot be interrogated in detail (ie. {{{GetLayers}}} on this selection will throw)
     162
     163The reason is the selection object is "disconnected" in that it has no internal reference to the {{{MgMap}}} it was initialized from (due to the (de)serialization of the {{{MgFeatureInformation}}} from server to web tier). There is a method {{{SetMap}}} that allows one to "attach" the original {{{MgMap}}} instance to the selection so that methods like {{{GetLayers}}} will work again, but this method is not part of the public API.
     164
     165To enable the selection within a {{{MgFeatureInformation}}} to be interrogated, the {{{SetMap}}} method will be promoted to {{{EXTERNAL_API}}}