-
Notifications
You must be signed in to change notification settings - Fork 56
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]: Powered by Krypton Toolkit button #1009
Comments
That would be nice of developers to do that, but those sort of things go into about box's and / or license text that should be shipped with apps. |
And as most apps have a theme changing component, then it could include that combo as well.. |
How about a preconfigured about box? |
too restrictive, AS most about boxes need to have additional info about the actual app, with areas for licensed components, and actual licensed status etc. |
Another option/addition would be a KAboutButton with the Logo and a text like "About KT" / "Powered by KT", which displays a KAboutForm |
@Smurf-IV Might be a good idea to use the |
@Wagnerp @Smurf-IV, some more info that's needed I can think of,
I think displaying any system info would be redundant / Windows version / KLibs (since dev can see that in VStudio).. Your input please.... |
It needs to be a drop-in component, restricting the editing of text should be easy, translations (if required) can be done via the new |
I don't know if we've done a KAboutForm yet... I guess we could take the default one from VB, CSharpify it, and modernise the layout? @Smurf-IV Thoughts? Edit: This looks good https://www.codeproject.com/Articles/7390/About-The-About-Box |
The link I posted would kill two birds with one stone, look at the GIF in the article... |
@Wagnerp @Smurf-IV Our AboutBox will contain that GroupBox as well. If info changes / needs updating than only the GroupBox component needs to be fixed. I thought that might be the most simple way to do it and please all of them in one go ;) |
Going to try and implement this tomorrow |
I think it should also state the License type before the "Click here" link. |
Hi @Smurf-IV
Trying to use a |
Try using the padding option 0, 10, 0, 0 |
|
I'm thinking to also have the option to display the version of the toolkit DLLs being used? |
Is that on the picturebox itself? |
That can be a option the dev can turn on/off, I think you can apply a filter to it also |
It also needs to be accessible to the dev if the theme selection is stored / restored on program shutdown and startup. |
Think the toolstrip default 'embedded' resources was the cause... that message is too vague MS should do better |
@Wagnerp It's not a priority request so... ;) |
Hi @giduac The feature is now in |
Hi @Wagnerp I had a brief look at it. Can you please elaborate a bit here on the two components |
Hi @giduac Sure, so the I hope this helps. |
Just thought on that and the previous ideas. How about to combine the information from both dialogs into one. Maybe said better, add the application info as a separate page/button? And on the previous ideas. Altogether that would save a bit of work and still work as a whole? |
Will work on it this week :) |
Hi @giduac Is this still needed? |
Imo to leave this open for later on when there's time left. Keep it for a rainy day... :) |
I'll make a pr turning them off for now |
v100? |
Definitely. All this stuff can go on the back burner until we have things sorted and well under control. |
Trying to be stricter. I think a list needs to be created for what to do for v90. |
Time is at a premium... Actually we should look actively to attract one or two more persons at least to take the pressure off |
Post a message on Discord? |
KAboutBox was already hidden from the toolbox |
Describe the solution you'd like
Would it be an idea to add a Button or other type of control to emphasize the use of KToolkit and link to it and that developers can incorporate into their programs...
These options are disabled for now (06-20-2024) and will be not in V90. until there's more time.
All components will be hidden from the toolbox for now.
The text was updated successfully, but these errors were encountered: