Skip to content

example needed to mitigate dev floundering #4210

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

Merged
merged 1 commit into from
Oct 11, 2022

Conversation

rtischer8277
Copy link
Contributor

It is not easy to match up variant vt types with POD types. Especially since there is a gradual transition to modern C++. I used a number of dev hours on attempts to match the variant type, vt, to make the true/false work. The m_bValue type for the simple property was a BOOL type, but trying to create a variant of type BOOL directly didn't work. Only by looking at VC Sample code for VisualStudioDemo did I see the (_variant_t)true construct, which becomes the standard_cast contruct in modern C++. I figured my Example code could make other programmer's efforts easier.

It is not easy to match up variant vt types with POD types. Especially since there is a gradual transition to modern C++. I used a number of dev hours on attempts to match the variant type, vt, to make the true/false work. The m_bValue type for the simple property was a BOOL  type, but trying to create a variant of type BOOL directly didn't work. Only by looking at VC Sample code for VisualStudioDemo did I see the (_variant_t)true construct, which becomes the standard_cast contruct in modern C++. I figured my Example code could make other programmer's efforts easier.
@prmerger-automator
Copy link
Contributor

@rtischer8277 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@opbld31
Copy link

opbld31 commented Oct 11, 2022

Learn Build status updates of commit 47e995c:

✅ Validation status: passed

File Status Preview URL Details
docs/mfc/reference/cmfcpropertygridproperty-class.md ✅Succeeded

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

@Court72
Copy link
Contributor

Court72 commented Oct 11, 2022

@TylerMSFT

Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged Tracking label for the PR review team label Oct 11, 2022
Copy link
Collaborator

@TylerMSFT TylerMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rtischer8277 , thank you very much for adding to the docs! We really appreciate that you'd take the time to add your learnings to the doc. There are some minor stylistic things in terms of spacing, and we prefer to say if (property != null) instead of if (property). But these are small things and I'll update them later. The important thing is the example you contributed and I'm approving your changes so we can get them in and published tomorrow. Thank you!

@TylerMSFT
Copy link
Collaborator

#sign-off

@TylerMSFT TylerMSFT merged commit 18a064d into MicrosoftDocs:main Oct 11, 2022
mstorsjo pushed a commit to mstorsjo/cpp-docs that referenced this pull request Oct 12, 2022
…-non-blocking

Address non-blocking issues from 4207
@rtischer8277 rtischer8277 deleted the patch-3 branch October 12, 2022 13:53
opbld17 added a commit that referenced this pull request Oct 12, 2022
* Document ARM64 unwind handling for return address signing

* Update date, fix step numbers

* Fix style, grammar in Arm64 Exception

* Rename pac_sign_lr and update reserved ranges.

* example needed to mitigate dev floundering (#4210)

It is not easy to match up variant vt types with POD types. Especially since there is a gradual transition to modern C++. I used a number of dev hours on attempts to match the variant type, vt, to make the true/false work. The m_bValue type for the simple property was a BOOL  type, but trying to create a variant of type BOOL directly didn't work. Only by looking at VC Sample code for VisualStudioDemo did I see the (_variant_t)true construct, which becomes the standard_cast contruct in modern C++. I figured my Example code could make other programmer's efforts easier.

* Confirm merge from FromPublicMasterBranch to main to sync with https://github.com/MicrosoftDocs/cpp-docs (branch main) (#4571)

* 10/11/2022 AM Publish (#4570)

* Document ARM64 unwind handling for return address signing

* Update date, fix step numbers

* Fix style, grammar in Arm64 Exception

Co-authored-by: opbld17 <[email protected]>
Co-authored-by: Colin Robertson <[email protected]>
Co-authored-by: opbld16 <[email protected]>
Co-authored-by: opbld15 <[email protected]>
Co-authored-by: Martin Storsjö <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>

* example needed to mitigate dev floundering (#4210)

It is not easy to match up variant vt types with POD types. Especially since there is a gradual transition to modern C++. I used a number of dev hours on attempts to match the variant type, vt, to make the true/false work. The m_bValue type for the simple property was a BOOL  type, but trying to create a variant of type BOOL directly didn't work. Only by looking at VC Sample code for VisualStudioDemo did I see the (_variant_t)true construct, which becomes the standard_cast contruct in modern C++. I figured my Example code could make other programmer's efforts easier.

Co-authored-by: Taojunshen <[email protected]>
Co-authored-by: opbld17 <[email protected]>
Co-authored-by: Colin Robertson <[email protected]>
Co-authored-by: opbld16 <[email protected]>
Co-authored-by: opbld15 <[email protected]>
Co-authored-by: Martin Storsjö <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: rtischer8277 <[email protected]>

Co-authored-by: opbld17 <[email protected]>
Co-authored-by: Colin Robertson <[email protected]>
Co-authored-by: opbld16 <[email protected]>
Co-authored-by: opbld15 <[email protected]>
Co-authored-by: Martin Storsjö <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: Pedro Miguel Justo <[email protected]>
Co-authored-by: rtischer8277 <[email protected]>
Co-authored-by: Feng Xu <[email protected]>
opbld15 added a commit that referenced this pull request Oct 13, 2022
* Document ARM64 unwind handling for return address signing

* Update date, fix step numbers

* Fix style, grammar in Arm64 Exception

* Rename pac_sign_lr and update reserved ranges.

* example needed to mitigate dev floundering (#4210)

It is not easy to match up variant vt types with POD types. Especially since there is a gradual transition to modern C++. I used a number of dev hours on attempts to match the variant type, vt, to make the true/false work. The m_bValue type for the simple property was a BOOL  type, but trying to create a variant of type BOOL directly didn't work. Only by looking at VC Sample code for VisualStudioDemo did I see the (_variant_t)true construct, which becomes the standard_cast contruct in modern C++. I figured my Example code could make other programmer's efforts easier.

* Confirm merge from FromPublicMasterBranch to main to sync with https://github.com/MicrosoftDocs/cpp-docs (branch main) (#4571)

* 10/11/2022 AM Publish (#4570)

* Document ARM64 unwind handling for return address signing

* Update date, fix step numbers

* Fix style, grammar in Arm64 Exception

Co-authored-by: opbld17 <[email protected]>
Co-authored-by: Colin Robertson <[email protected]>
Co-authored-by: opbld16 <[email protected]>
Co-authored-by: opbld15 <[email protected]>
Co-authored-by: Martin Storsjö <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>

* example needed to mitigate dev floundering (#4210)

It is not easy to match up variant vt types with POD types. Especially since there is a gradual transition to modern C++. I used a number of dev hours on attempts to match the variant type, vt, to make the true/false work. The m_bValue type for the simple property was a BOOL  type, but trying to create a variant of type BOOL directly didn't work. Only by looking at VC Sample code for VisualStudioDemo did I see the (_variant_t)true construct, which becomes the standard_cast contruct in modern C++. I figured my Example code could make other programmer's efforts easier.

Co-authored-by: Taojunshen <[email protected]>
Co-authored-by: opbld17 <[email protected]>
Co-authored-by: Colin Robertson <[email protected]>
Co-authored-by: opbld16 <[email protected]>
Co-authored-by: opbld15 <[email protected]>
Co-authored-by: Martin Storsjö <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: rtischer8277 <[email protected]>

* cleanup empty remarks and tidy up code example formatting

* Confirm merge from FromPublicMasterBranch to main to sync with https://github.com/MicrosoftDocs/cpp-docs (branch main) (#4573)

* Use the correct canonical opcode name in the packed unwind table

This was a leftover from the original tentative name before the
real one was known.

* Correct Month range in `ok` member description (#4215)

Co-authored-by: Martin Storsjö <[email protected]>
Co-authored-by: Colin Robertson <[email protected]>
Co-authored-by: Christopher Doyle <[email protected]>

Co-authored-by: opbld17 <[email protected]>
Co-authored-by: Colin Robertson <[email protected]>
Co-authored-by: opbld16 <[email protected]>
Co-authored-by: opbld15 <[email protected]>
Co-authored-by: Martin Storsjö <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: Pedro Miguel Justo <[email protected]>
Co-authored-by: rtischer8277 <[email protected]>
Co-authored-by: Feng Xu <[email protected]>
Co-authored-by: TylerMSFT <[email protected]>
Co-authored-by: Christopher Doyle <[email protected]>
Co-authored-by: Linda Spiller <[email protected]>
opbld15 added a commit that referenced this pull request Oct 14, 2022
…//github.com/MicrosoftDocs/cpp-docs (branch main) (#4571)

* 10/11/2022 AM Publish (#4570)

* Document ARM64 unwind handling for return address signing

* Update date, fix step numbers

* Fix style, grammar in Arm64 Exception

Co-authored-by: opbld17 <[email protected]>
Co-authored-by: Colin Robertson <[email protected]>
Co-authored-by: opbld16 <[email protected]>
Co-authored-by: opbld15 <[email protected]>
Co-authored-by: Martin Storsjö <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>

* example needed to mitigate dev floundering (#4210)

It is not easy to match up variant vt types with POD types. Especially since there is a gradual transition to modern C++. I used a number of dev hours on attempts to match the variant type, vt, to make the true/false work. The m_bValue type for the simple property was a BOOL  type, but trying to create a variant of type BOOL directly didn't work. Only by looking at VC Sample code for VisualStudioDemo did I see the (_variant_t)true construct, which becomes the standard_cast contruct in modern C++. I figured my Example code could make other programmer's efforts easier.

Co-authored-by: Taojunshen <[email protected]>
Co-authored-by: opbld17 <[email protected]>
Co-authored-by: Colin Robertson <[email protected]>
Co-authored-by: opbld16 <[email protected]>
Co-authored-by: opbld15 <[email protected]>
Co-authored-by: Martin Storsjö <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: rtischer8277 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants