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

[Feature Request]: Bring MessageBox States inline with latest .Net 6 #728

Closed
Smurf-IV opened this issue Jun 6, 2022 · 14 comments
Closed
Labels
completed This issue has been completed. enhancement New feature or request new feature A new feature has been requested. suggestion A suggestion has been requested.
Milestone

Comments

@Smurf-IV
Copy link
Member

Smurf-IV commented Jun 6, 2022

https://docs.microsoft.com/en-us/dotnet/desktop/winforms/whats-new/net60?view=netdesktop-6.0#updated-apis

image

===================
Edit:
The "Idea" of these changes is to bring the functionality "Down" from .Net 6 / 7 into the earlier versions, so that a Single code base will work for multi-target builds.

@Smurf-IV Smurf-IV added enhancement New feature or request suggestion A suggestion has been requested. labels Jun 6, 2022
@PWagner1 PWagner1 added this to the Version 7 milestone Jun 6, 2022
@PWagner1 PWagner1 added the new feature A new feature has been requested. label Jun 6, 2022
@PWagner1
Copy link
Contributor

PWagner1 commented Jun 6, 2022

@Smurf-IV Just thinking about it, do these new features need the #if definition to work? If so, I'll try to tackle some of the messagebox portion of it today.

@Smurf-IV
Copy link
Member Author

Smurf-IV commented Jun 6, 2022

#if would be one way to "Limit" the functionality,
But... It would be nice if it could be made "Backward compatible" (i.e all the way down down to .net 4.6.2);
This resulting in a single code base for the User developer to use regardless of TFM

Smurf-IV added a commit that referenced this issue Jun 11, 2022
* Semi implement #728, with points 2 & 4 outstanding
@PWagner1 PWagner1 added the awaiting feedback A fix for this issue has been implemented, waiting for feedback on the fix. label Jun 11, 2022
@PWagner1
Copy link
Contributor

Needs testing >= .162

@PWagner1
Copy link
Contributor

@Smurf-IV Do we know if this is working, also what is button4 used for?

PWagner1 added a commit that referenced this issue Jul 16, 2022
@Smurf-IV
Copy link
Member Author

Smurf-IV commented Jul 17, 2022

@Smurf-IV Do we know if this is working,

It is displayed via a new System API, where uType has all the "styles" placed into a DWORD:
image

also what is button4 used for?

image

@PWagner1
Copy link
Contributor

@Smurf-IV Do we know if this is working, also what is button4 used for?

image

So, is there a help button now?

@PWagner1
Copy link
Contributor

PWagner1 commented Jul 17, 2022

@Smurf-IV I assume the "new" button4 option would go to the left of the existing buttons if it's a dedicated help button?

i.e.

ButtonPanel

@Smurf-IV
Copy link
Member Author

You will have to create a demo app in .Net 6 and try....

@PWagner1
Copy link
Contributor

I'm not sure if we even need this, as a button for help is already catered for

@PWagner1
Copy link
Contributor

Got it!! PR coming soon

PWagner1 added a commit that referenced this issue Jul 18, 2022
Smurf-IV added a commit that referenced this issue Jul 24, 2022
@PWagner1 PWagner1 modified the milestones: Version 7, Version 8 Oct 23, 2022
@Smurf-IV Smurf-IV removed the awaiting feedback A fix for this issue has been implemented, waiting for feedback on the fix. label Dec 4, 2022
@Smurf-IV Smurf-IV self-assigned this Dec 4, 2022
@Smurf-IV Smurf-IV added the under investigation This bug/issue is currently under investigation. label Dec 11, 2022
@Smurf-IV
Copy link
Member Author

@Wagnerp I think in order to get "Backward compatible with previous versions of TFM", _we_would need to use a krypton type for buttons etc. Like you did for the Icons. e.g.
MessageBoxButtons -> KyrptonMessageBoxButtons

Thuoghts ?

@PWagner1
Copy link
Contributor

@Wagnerp I think in order to get "Backward compatible with previous versions of TFM", _we_would need to use a krypton type for buttons etc. Like you did for the Icons. e.g. MessageBoxButtons -> KyrptonMessageBoxButtons

Thuoghts ?

@Smurf-IV No problem, I may look into the feasibility of #866

@PWagner1
Copy link
Contributor

@Smurf-IV I think I did something similar in the extended toolkit, regarding buttons, so you can borrow that code

@Smurf-IV
Copy link
Member Author

Point 1 done:
MBox

Smurf-IV added a commit that referenced this issue Dec 11, 2022
…`MessageBoxButtons`

- Fix fallout for the new dialogResult type
- Fix Help button not being shown
- Add missing `private` monikers
- Fix usage of controls in the KryptonMessageBox demo
- Remove some usages of .net 5
- Remove some compile warnings / messages from Example projects

##867
##728)
Smurf-IV added a commit to Krypton-Suite/Standard-Toolkit-Demos that referenced this issue Dec 11, 2022
…`MessageBoxButtons`

- Fix fallout for the new dialogResult type
- Fix Help button not being shown
- Add missing `private` monikers
- Fix usage of controls in the KryptonMessageBox demo
- Remove some usages of .net 5
- Remove some compile warnings / messages from Example projects

#Krypton-Suite/Standard-Toolkit#867
#Krypton-Suite/Standard-Toolkit#728)
@Smurf-IV Smurf-IV removed their assignment Dec 11, 2022
@Smurf-IV Smurf-IV added completed This issue has been completed. and removed under investigation This bug/issue is currently under investigation. labels Dec 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
completed This issue has been completed. enhancement New feature or request new feature A new feature has been requested. suggestion A suggestion has been requested.
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants