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

Update Submodel Aliases Using Mapping #4510

Closed
blun23 opened this issue Apr 18, 2024 · 3 comments
Closed

Update Submodel Aliases Using Mapping #4510

blun23 opened this issue Apr 18, 2024 · 3 comments

Comments

@blun23
Copy link

blun23 commented Apr 18, 2024

Is your feature request related to a problem? Please describe.
Not a problem but you can currently update Aliases this way on Models but not submodels

Describe the solution you'd like
There is a button at the bottom of the Mapping screen that allows you to Update Aliases of Models by using Mapping. This would be awesome if it could be upgraded to also updated the Submodel Aliases. This would make auto mapping much more easier for the user. Currently you only can do something like this with a Mapping File.

Additional context
Screenshot 2024-04-18 at 12 53 46 PM

@derwin12
Copy link
Collaborator

FYI ,, the import dialog is the next piece in the puzzle for the submodel aliases. Stay tuned.

@AzGilrock
Copy link
Collaborator

For all the new work please try to minimize how much XML interaction there is. Try to have classes that hold their own state in member variables instead of inside the XML as much as possible to make it easier for me to transition that XML stuff out of there later.

@cybercop23
Copy link
Collaborator

Will be available in the nightly build and next version.

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

No branches or pull requests

4 participants