Cherry-pick PRs 14394, 14424, 14500, 14740

[aparajit-pratap]

Purpose

Cherry-pick PRs #14394, #14424, #14500, #14740

Declarations

Check these if you believe they are true

• The codebase is in a better state after this PR
• Is documented according to the standards
• The level of testing this PR includes is appropriate
• User facing strings, if any, are extracted into *.resx files
• All tests pass using the self-service CI.
• Snapshot of UI changes, if any.
• Changes to the API follow Semantic Versioning and are documented in the API Changes document.
• This PR modifies some build requirements and the readme is updated
• This PR contains no files larger than 50 MB

Release Notes

• Clear element binding data from DYN upon Save As
• Don't save file to recent files list if Save As is canceled
• Add provision of tooltips to message boxes

Reviewers

(FILL ME IN) Reviewer 1 (If possible, assign the Reviewer for the PR)

(FILL ME IN, optional) Any additional notes to reviewers or testers.

FYIs

(FILL ME IN, Optional) Names of anyone else you wish to be notified of

[QilongTang]

Is the element binding one a must have? Because that cherry pick introduce new resource strings while the localization process is done for 2.19.5

[mjkkirschner]

should the element binding change really be made in 2.19? I thought that should only go into 3.0 - why would we cherry pick an API break like that?

Ah, sorry I think I am getting confused between the SaveAs dropping element binding change and the element binding serialization format change - please ignore me.

[mjkkirschner]

Is the element binding one a must have? Because that cherry pick introduce new resource strings while the localization process is done for 2.19.5

IMO - having the dialog which a user could translate themselves with more info is better than not having it - alternatively we could make it a known issue... which we also don't translate ;)

[aparajit-pratap]

Is the element binding one a must have? Because that cherry pick introduce new resource strings while the localization process is done for 2.19.5

IMO - having the dialog which a user could translate themselves with more info is better than not having it - alternatively we could make it a known issue... which we also don't translate ;)

I agree with having the messaging even if it's missing localization as it will be good to have something than nothing at all.

[QilongTang]

Two regressions remaining, see https://master-5.jenkins.autodesk.com/job/Dynamo/job/DynamoSelfServe/job/pullRequestValidation/15161/
Oh looks like everything is good in the next job, LGTM