v15.1 – Reload Current Package, reloads content, but not the package itself

[Paolo F Cantoni]

When you issue a "<context menu> | Content | Reload Current Package" command in the Project Browser, the contents of the package are reloaded, but the package itself is NOT.  For example, if another user changed something in the background in the package item itself, you won't see this.  The package item itself should be refreshed.

Reported,
Paolo

[Eve]

Are you referring to something within the Properties window?

I just tested making a change that is displayed in the Browser (in my case the name) and it was updated in the browser correctly.

It's also a little ironic that you're complaining about something only applying to the contents of the package, when it is accessed through the 'Contents' menu.

[Paolo F Cantoni]

Are you referring to something within the Properties window?

I just tested making a change that is displayed in the Browser (in my case the name) and it was updated in the browser correctly.

It's also a little ironic that you're complaining about something only applying to the contents of the package when it is accessed through the 'Contents' menu.

Yes, I'm talking about things that might end up in the properties window.

And I was talking about background changes not live.  It's not clear if your test was between machines (users) or not.  The name might well be picked up, I was observing this on the "lesser" properties.

As to the irony, as you know I like irony.  Supposing the Name had NOT been picked up correctly, would that have been a defect or not?

Paolo

[Eve]

That function doesn't make any attempt to load anything outside of the browser window.

Probably doesn't mean much, but the help makes that explicit.

https://sparxsystems.com/enterprise_architect_user_guide/15.2/model_navigation/contentssub-menu.html

Select this option to refresh the current Package in the Browser window.

There is certainly room for feature creep for the function. Yes, it doesn't reload the properties, notes or any other docked window. It also doesn't reload any diagrams under that package or update elements within that package that appear on open diagrams.

Yes, it could theoretically do all of those things. I'm not sure it should do any of them.

[Paolo F Cantoni]

That function doesn't make any attempt to load anything outside of the browser window.

Probably doesn't mean much, but the help makes that explicit.

https://sparxsystems.com/enterprise_architect_user_guide/15.2/model_navigation/contentssub-menu.html

Select this option to refresh the current Package in the Browser window.

There is certainly room for feature creep for the function. Yes, it doesn't reload the properties, notes or any other docked window. It also doesn't reload any diagrams under that package or update elements within that package that appear on open diagrams.

Yes, it could theoretically do all of those things. I'm not sure it should do any of them.

Wow, from previous behaviour in previous versions, I got the impression it did (at least) some of that.  I guess I got fooled.

I think there is a place for another function that did update everything.  Other than a complete reload, there's nothing like that.  I was using the functionality to reload only a particular branch, not the whole repository.  Now you tell me it wasn't doing that at all.  Oh well...

Should I put in a feature request for a "reload branch" functionality (a subset of "Reload Project")?

Paolo

[Uffe]

That function doesn't make any attempt to load anything outside of the browser window.
Probably doesn't mean much, but the help makes that explicit.

It doesn't really. It only does if you've decided beforehand to read it that way.

https://sparxsystems.com/enterprise_architect_user_guide/15.2/model_navigation/contentssub-menu.html

Select this option to refresh the current Package in the Browser window.

The sentence is ambiguous: "in the browser window" can refer to either the word "refresh" or to the word "current".
Reading that sentence to mean "select this option to make the client re-read from the repository the contents of the package currently selected in the browser and then refresh all current presentations of those contents" is not unreasonable.

Also, 15.2? Sneak preview?

It also doesn't reload any diagrams under that package or update elements within that package that appear on open diagrams.

There is a Reload <diagram> function in the context menu of the diagram tab.
The Save and Close functions are also available in that menu, but while there are Save All and Close All functions, there is no Reload All. Adding that would be useful regardless of everything else.

Should I put in a feature request for a "reload branch" functionality (a subset of "Reload Project")?

I can certainly see a case for that. I think it's better to update the current function (I can't see a case for refreshing just the browser), but if it has to be a separate function because it's important to cater to users who like their data to be presented inkonsiztently in two parts of the same GUI depending on when the different parts were last refreshed from the client's cache whose timestamps the user cannot see, then I guess that's OK.


/Uffe

[Eve]

Also, 15.2? Sneak preview?

Oops. I spend the majority of my time using unreleased versions and builds. I'll just say I wouldn't expect 15.1 to be the last version ever.

I can certainly see a case for that. I think it's better to update the current function (I can't see a case for refreshing just the browser), but if it has to be a separate function because it's important to cater to users who like their data to be presented inkonsiztently in two parts of the same GUI depending on when the different parts were last refreshed from the client's cache whose timestamps the user cannot see, then I guess that's OK.

Besides potentially making it a very slow operation (especially on slower connections), one of the complications of reloading everything would be needing to make sure that everything is saved before starting it. Possibly only a minor inconvenience from a user perspective, but it's not as simple as one behavior being definitively better than the other for all users.

[Eve]

Also, 15.2? Sneak preview?

Sneak preview no longer.

https://www.sparxsystems.com/products/ea/15.2/index.html