nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Refresh toolset

wayfaringrob

With a toolset open in the catalog view, allow the user to refresh the toolset via the refresh button or F5. Doing so currently causes all models in the toolset to disappear (rendering the message "This container is empty."). The workaround is to head up a level (to the toolbox), refresh there, and re-open the toolset.

Trouver plus de publications taguées avec

Geoprocessing

Closed

Status: Closed

Réponses

JonathanNeal

@wayfaringrob Nice find, will check it out and log it.

JohannesLindner

I always thought that was the intended behavior. It's the reason why I stopped using tool sets when developing my Python toolbox. It's just one click to open the tool set again, but that adds up...

wayfaringrob

@JohannesLindner it's hard to tell what's a bug and what's a feature sometimes, huh? 🙂

Thanks @JonathanNeal !

JonathanNeal

@wayfaringrob (Oh I hope not, but unsure to whether to laugh or cry 🙂 ) @JohannesLindner Both I can repro what you are seeing in current Pro. Thanks for bringing this up.

Just for future reference on our process you can log bugs here: https://support.esri.com/en/report-bug
Also, we treat unclear doc as something that can lead to bugs. So if your unsure on a topic, the bottom of the doc page has a link to give us feedback on how we can improve. (We review it and put it into our workload).

wayfaringrob

@JonathanNeal yes, I've come to err on the side of idea posts vs. bug reports. After reporting many bugs the "right" way, I've just found it too much of a hassle, especially when there are so many bugs to report. Tech support always wants to call me (inevitably when I'm in the middle of something), screen share, screen share again; often, it takes multiple rounds of re-explaining the issue. I get that more detail is sometimes needed, but I can't count the number of times a support analyst has jumped straight to requesting a screen share without even looking at the steps I bothered typing out, or not following them closely. Just filling out the form to request a case takes more time than an idea posting; it really burdens users. Even after all that, sometimes, I'm told it's not a bug and I need to make an idea post. I suspect that that tedious process (and perhaps not knowing bugs can be reported) is why so many still persist -- we need something that's as easy as this site, but for bugs, like Microsoft's feedback hub. Click of a button, built into the app. Easy peasy.

At least here, I can get to someone without taking too much time out of my day.

JonathanNeal

@wayfaringrob Totally agree your time is what this is all about. So whatever is getting you the fewest clicks and the least distruption is what we need to go with.

Rejoindre la conversation

Connectez-vous pour publier, suivre du contenu, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.