Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MCC: Microchip Graphics Composer doesn't remember last saved project #37

Open
manolisss opened this issue Nov 15, 2023 · 2 comments
Open

Comments

@manolisss
Copy link

manolisss commented Nov 15, 2023

MCC v5.3.7
Core v5.5.7
Legato v2.3.15
MPLABX IDE v6.15

Hi,

We are transitioning from MHC3 to MCC and are having some issues with the graphics composer.
More specifically it seems that the composer doesn't remember the last saved project and always prompts us to either create a new project or open an existing one.
Additionally, checking the "Don't show this dialog again" checkbox doesn't work, as the dialog is shown again the next time we open the composer.

image

@microchip-graphics
Copy link

Hello,

When opening Composer, MCC will look for a file name that looks like: nameOfConfiguration_design.zip
Ex: legato_qs_mzda_cu_tm4301b_design.zip

Check to see if the Composer design name matches the project configuration name. If they match, launching Composer should automatically load the project's design.

It does appear that there is a bug with the "Don't show this dialog again" checkbox; thank you for providing feedback!

@manolisss
Copy link
Author

manolisss commented Nov 16, 2023

Hi,

Thank you for the quick response!

Indeed we can confirm that renaming the composer design to match project configuration name, makes the Composer open the imported design on startup.

Of course the user should be notified of this when importing a design with a prompt like:
"Would you like to rename the imported design so that the composer can open it automatically on startup?"

Otherwise the user can't really understand what's going on, please consider adding this to the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants