Markup editing bug when reopening markup saved in a project json file?

Répondu

Peter Jackson

4 novembre 2022 16:30

In VertiGIS Studio Web SAAS I’ve done the following:

Is this a bug in the SAAS version of Web? I did the following:

1. Opened the Web GIS – Default template
2. Saved As my own app
3. Added Save Project and Load Project to the toolbar in my app
4. Drew a single point markup feature on the map
5. Used Edit Markup tool to move the point markup
6. Saved the state of my app as a project json file

All things work as expected to this point. BUT…

1. I refresh the Web application
2. I open the project file and it loads successfully
3. I now use the Edit Markup tool to move the point markup feature

At this point things go wrong:

1. The border/edge of the point markup feature moves using the Edit Markup tool, but the original markup feature remains in its original location.
   
2. Edit Markup allows me to select the red ring feature and move it or delete it
3. However, the original feature can no longer be selected using the Edit Markup tool so cannot be moved or deleted.
4. The 'ghost' feature can only be removed using the Clear all Markup option. 
5. I get similar 'ghost' features when moving Polygon or Line markup after saving the markup to a json project file and reopening it.
   This occurs in all our apps in Dev, Test and Prod environments of VertiGIS Studio Web (SAAS) 5.20.0. Does the same occur for other Web users?

0

• 

  Cam Barnard

  5 janvier 2023 22:45

  Thanks for pointing the issue out. Wanted you to know it was captured a while back when you told us as issue # 197609.

  The root problem is that when we do our markup it isn't just one thing, but two things together in order to be WCAG AA 2.1 contrast compliant. When we serialize it out to a project we lose the associated between those two things.

  We have a couple of ideas on how to fix it that are in progress now.

  0
• 

  Peter Jackson

  28 mars 2023 13:47

  A quick update on the above -

  As a workaround we have removed the WCAG contrast compliance and are using simple markup. However, there are still problems. When a user creates markup and then deletes one or more of their markup features. there are two significant problems. 

  1. Printing fails to start when clicking the Print button from the Print Template options. Nothing happens and there is no feedback/error displayed for the user. In Developer Tools there's this error: 

  Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'type')
      at e.fromEsriApiGraphicsLayer  

  2. After saving a json project file, when loading the saved project the map zooms to the correct location but fails to display any markup features at all. Again, there is no feedback/error displayed for the user. In Developer Tools there is this error:

  Uncaught (in promise) TypeError: Cannot read properties of null (reading 'spatialReference')

  In the project json the deleted feature is retained but lacks any "geometry" component:

   {
              "attributes": {
                  "graphic-visible": true
              },
              "symbol": {
                  "type": "esriSFS",
                  "color": [251, 43, 17, 33],
                  "outline": {
                      "type": "esriSLS",
                      "color": [251, 43, 17, 255],
                      "width": 2.5,
                      "style": "esriSLSSolid"
                  },
                  "style": "esriSFSSolid"
              }
          }

  This is causing a lot of issues for users and work for admin because the only way to recover the projects is to edit the json and remove the deleted features manually. 

  0

Vous devez vous connecter pour laisser un commentaire.