Zum Hauptinhalt gehen

Get Ready! VertiGIS Studio Web 5.44 Release Candidate is Here!

Kommentare

10 Kommentare

  • Nico Burgerhart

    I would like to have more information on the “Web Template Standardization” topic. What was changed/improved?

    0
  • Holger Frommer

    Version 5.43 listed the ID 386494 as “Known Issue” (Enable Show and Hide Layer Labels actions for Map Image sublayers without edit permissions). The changelog still lists it only as accepted (with a release-date 1970-01-01???), and your highlights for 5.44 don't mention it as solved. 

    How long do Known Issues “normally” take to be resolved (I know it's hard to tell)? This bug is blocking us from updating. Everything works fine in 5.36 but got lost somewhere inbetween 5.37 and 5.42 (german support wasn't able to pin down the exact version).

    2
  • Christian Wohlmutter

    Nico Burgerhart 

    • Basemaps were added explicity but their sublayers were left out
    • IDs were adjusted to be more descriptive
    • All menus were flattened
    • Geocoder settings were removed
    • The order of keys in each object were adjusted. Designer prefers IDs at the top, followed by the icon, and at the very bottom the type of item
    0
  • Christian Wohlmutter

    Holger Frommer it can't be generalized regarding when I known issue is going to be resolved. It depends on the severity of the issue and on how many customers are affected by it. Critical issues are fixed by the next release, while bugs which happen just under very specific conditions, or if there is a feasible workaround, then the fix happens just versions later.

    Regarding 386494. This was turned into a user story. While it is expected behaviour, hiding and showing labels shouldn't get the same restrictions as editing/updating. Therefore, more work needs to be done to solve it.

    0
  • Holger Frommer

    Hi Christian,

    Thanks for the clarification. Although I can't see why this should be an “expected behaviour”…

    It's not satisfying to read copy-paste sentences like “It depends on the severity of the issue and on how many customers are affected by it.”. We have reported bugs nearly two years ago which still are not solved. Some are regional issues, I know (308549, submitted Nov 2024), but others impact every user like returning false results (314895, submitted Jan 2025). And there are a lot more.

    Anyway, we will have to wait. Again.I know my post won't speed up anything, and please don't take anything of it personal. I'm just frustrated.

    2
  • Andreas Grimm

    Has anyone tried Next-Gen Editing yet? 

    I activated it under Services/Draw, yet am not noticing any difference to before. 

    0
  • Christian Wohlmutter

    We've already received some feedback from customers regarding Next Gen Editing. Please mind, that after activating it under Services/Draw, the App must be saved and restarted. Goal of current release was feature parity, so no new functionality yet.

    -2
  • Andreas Grimm

    So no changes, at all?

    I was getting my hopes up that at the very least, we'd be able to modify a drawing's symbology while drawing, and not only afterwards when editing it. 

    These are absolute basics that VSW still hasn't gotten right.

    1
  • Mike Diss-Torrance

    Is the requested feedback regarding whether the NGE addresses all the same capabilities as the legacy version in our existing applications? Overall, I'm just trying to understand what the “ask” is and if we to provide feedback beyond that, such as new capabilities or behaviors?

    Also, other the high-level listing of capabilities (above), where can we find guidance on what has been added/altered? For instance, I noticed there is a Edit Result command in the Attribute table now (good), but the guidance doesn't mention anything about it: https://docs.vertigisstudio.com/webviewer/latest/admin-help/settings-attribute-table.html (bad). 

    My main concern is that we have a suite of editing application that use a mix of out the box Vertigis Studio Web capabilities, Vertigis Studio Web events, and Vertigis Studio Workflows. What, specifically, will be retired in version 5.46 that we need to rewrite before then?

    0
  • Christian Wohlmutter

    Mike Diss-Torrance Thank you for your questions and for testing Next Generation Editing.

    What we are asking for. Our intent is to keep all commands the same and only change the engine behind them. When we ask for testing of the Next Generation Editing beta, the goal is that all of your existing functionality keeps working. The most valuable feedback is therefore any case where one of your editing apps behaves differently from legacy editing, whether it uses out-of-the-box capabilities, events or workflows. Feedback beyond that, such as ideas for new capabilities, is welcome too. Please post those as ideas in the community, so that they can be tracked separately.

    What will be retired in 5.46. What is retired is the legacy editing engine itself, not the commands you use. As announced, 5.44 lets you switch between Next Generation Editing and legacy editing. In 5.45, Next Generation Editing is on by default and the switch is still available. In 5.46, in February, legacy editing is removed. Because the commands stay the same, our intent is that you do not have to rewrite your apps, workflows or event handlers for this change. We cannot 100% rule out gaps, which is why we ask for testing your specific configurations and use cases before 5.46.

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.