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

menu tray bugs #179

Closed
mmikeww opened this issue Jun 3, 2024 · 7 comments
Closed

menu tray bugs #179

mmikeww opened this issue Jun 3, 2024 · 7 comments

Comments

@mmikeww
Copy link
Owner

mmikeww commented Jun 3, 2024

from forum
https://www.autohotkey.com/boards/viewtopic.php?p=573895&sid=a856ddeab374f28658a4e1d432887b4e#p573895

@Banaanae
Copy link
Collaborator

Banaanae commented Jun 3, 2024

Icons were fixed in #126, but the fix isn't running, example one should be an easy fix

@andymbody
Copy link
Contributor

andymbody commented Jun 8, 2024

Proposed fix...

Submitted PR... hopefully I did it correct... it's so confusing! lol

@mmikeww
Copy link
Owner Author

mmikeww commented Jun 8, 2024

you can submit the PR and then we can test

typically the work flow is:

  1. you test on your local machine and try to get it as clean as possible before sharing
  2. you upload to branch on your personal repository
  3. you submit PR into main repository pointing to your branch
  4. people can review and test your PR code
  5. if suggestions/changes need to be made, you update your PR accordingly by updating your branch
  6. people retest your changes
  7. if looks good, PR is accepted and merged into main repository

remember to add new tests in your PR showing what your changes accomplish

@andymbody
Copy link
Contributor

you can submit the PR and then we can test

Ok... will do... thanks...

@andymbody andymbody mentioned this issue Jun 8, 2024
Banaanae pushed a commit that referenced this issue Jun 8, 2024
@Banaanae
Copy link
Collaborator

Banaanae commented Jun 8, 2024

Fixed in #182

@Banaanae Banaanae closed this as completed Jun 8, 2024
@andymbody
Copy link
Contributor

The OP posted an update after testing this fix, and it was not fixed. I made an adjustment to fix it. Does this require a new issue to be created, or can this one be reopened? I am almost ready to post the updated fix, but wanted to find out how to handle this.

@mmikeww
Copy link
Owner Author

mmikeww commented Jun 9, 2024 via email

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