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

add icon to gg.Config to be used with gg.new_context() #23135

Closed
1 of 2 tasks
YukiiVR opened this issue Dec 11, 2024 · 4 comments
Closed
1 of 2 tasks

add icon to gg.Config to be used with gg.new_context() #23135

YukiiVR opened this issue Dec 11, 2024 · 4 comments

Comments

@YukiiVR
Copy link
Contributor

YukiiVR commented Dec 11, 2024

Describe the feature

by adding a window icon to gg.Config, it allows for developers to add an optional icon while creating there window with gg.new_context(). this is still possible by manually creating the window with sokol (as seen on examples\sokol\08_sdf.v) but this would only make it slightly easier.

Use Case

this is still possible by manually creating the window with sokol (as seen on examples\sokol\08_sdf.v) but this would only make it slightly easier. in the case of someones project not having an icon and later adding one, they would not need to replace code to generate a window that allows an icon to be passed through, instead, we can just use gg.new_context(window_icon: sapp.IconDesk{...})

Proposed Solution

in the gg.Config struct, we can add window_icon which will be a sapp.IconDesc. then inside of the new_context method, we can add icon: cfg.window_icon

Other Information

I currently have a fork and branch that implements this at bd98905

Acknowledgements

  • I may be able to implement this feature request
  • This feature might incur a breaking change

Version used

V 0.4.8 77e4594

Environment details (OS name and version, etc.)

OS: windows, Microsoft Windows 10 Enterprise v19045 64-bit
Processor: 8 cpus, 64bit, little endian,

Note

You can use the 👍 reaction to increase the issue's priority for developers.

Please note that only the 👍 reaction to the issue itself counts as a vote.
Other reactions and those to comments will not be taken into account.

@spytheman
Copy link
Member

imho just make a PR, since you already have it implemented

@YukiiVR
Copy link
Contributor Author

YukiiVR commented Dec 11, 2024

I went ahead and did the PR (#23138), I'll go ahead and close this issue as well.

@YukiiVR YukiiVR closed this as completed Dec 11, 2024
@JalonSolov
Copy link
Contributor

If you add #<issue number> to the comment on a PR, the issue will be automatically closed when the PR is merged.

@YukiiVR
Copy link
Contributor Author

YukiiVR commented Dec 11, 2024

If you add #<issue number> to the comment on a PR, the issue will be automatically closed when the PR is merged.

Did not know this, thanks for the tip!

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

No branches or pull requests

3 participants