Resolve compatability between v2.4 and anticipated v2.5
See original GitHub issuePrerequisites
-
Put an X between the brackets on this line if you have done all of the following:
-
Running the latest version of Constellation
-
Attached the Support Package via
Help
>Support Package
-
Checked the FAQs: https://github.com/constellation-app/constellation/wiki/FAQ
-
Checked that your issue isn’t already filed: https://github.com/constellation-app/constellation/issues
-
Checked that there is not already a module that provides the described functionality: https://github.com/constellation-app/constellation/wiki/Catalogue-of-Repositories
-
Description
Major refactoring of code is currently underway in PR’s (https://github.com/constellation-app/constellation/pull/1415) and another already in master
being the Table View refactor. Though these changes are necessary, we should look to make sure the migration from versions prior to the anticipated v2.5 work seemlessly with v2.5.
There is an issue identified with the Data Access View that will occur when #1415 is merged in because the Top Component has moved packages. The state of the views make reference to the full class path including the package name so for instance if you have the Data Access View open in v2.4 and move to v2.5, there is an exception that is thrown (because the class was not found) and the view opens in the graphs section rather than on the left pane. This is a result of the exception.
A similar issue is likely with the Table View as it’s Top Component has moved packages.
One option is to temporarily restore these packages to their old package until v3’s release next year.
Steps to Reproduce
- Open the Data Access View in v2.4
- Close v2.4
- Open v2.5
Expected behaviour: [What you expect to happen] The Data Access View stays open in the position when it was closed in v2.4
Actual behaviour: [What actually happens] The Data Access View opens in the “explorer” graph position
Reproduces how often: [What percentage of the time does it reproduce?] 100%
Additional Information
All views should be opened in v2.4 and then in v2.5 and made sure they look and operate as expected.
Note that if v2.5 is not build then compile a stand alone version from the branch or master
.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8
Top GitHub Comments
@arcturus2 If the distribution version isn’t having this issue then I think I’m ok with this being closed
This is an interesting issue @antares1470 and @arcturus2. I have used the reset.bat and it was quite handy so that is very useful to have for new releases. I liked the warning it gave too. It would be great to promote it more broadly, noting it was on the latest blog. FAQs might be good on the main Constellation website, something to consider