Closed corybarr closed 5 months ago
This appears to be functioning as expected.
My only question is should there be some feedback in the console when WMTS is configured incorrectly?
For example, with WMS and TMS if I put in a wrong URL, I'll usually get some form of error.
However, with WMTS nothing displays in the log at all.
This appears to be functioning as expected.
My only question is should there be some feedback in the console when WMTS is configured incorrectly?
For example, with WMS and TMS if I put in a wrong URL, I'll usually get some form of error.
However, with WMTS nothing displays in the log at all.
I think it would be better. I'll look into it.
For ref, it seems that a valid, although empty, result is returned when WMTS Urls are bad:
A bad TMS Url will fail the if (result)
test and trigger the error logger.
(Draft until UI polishing is complete)
Adds TMS support:
Adds WMTS support:
UI/UX Notes:
This PR hides them instead. I didn't find an obvious way to gray them out.
While Omniverse supports string[] parameters, they aren't by default editable in the UI:![image](https://github.com/CesiumGS/cesium-omniverse/assets/1040194/6f1b45f0-9e92-4633-bb1e-9ac5d7937b8c)
In this PR, users supply the strings comma-separated.
I don't have an example to test all settings. "Tiling Scheme Settings" is currently untested:![image](https://github.com/CesiumGS/cesium-omniverse/assets/1040194/9bcd3436-9f0b-47b0-b347-81ce44c159c3)
I hit some limitations trying to visually group parameters in the custom attribute widgets. In particular omni.ui.Line didn't appear. The UI is functional, but the UX and in particular visual groupings could use improvement.
reloading the tileset every time a property is changed is probably not ideal. See #676