Resolved Issues

Amplitude-Frequency-Visualizer.py

@@ -49,7 +49,7 @@
     ],
 ]
 
-_VARS["window"] = sg.Window("Mic to frequency plot + Max Level", layout, finalize=True)
+_VARS["window"] = sg.Window("Mic to frequency plot + Max Level", layout,icon="icons/amp-freq.ico", finalize=True)
 graph = _VARS["window"]["graph"]
 
 # INIT vars:

Code_Of_Conduct.md

@@ -1,76 +1,76 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
- advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
- professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

Contribution.md

@@ -1,58 +1,58 @@
-*This file contains the guidelines for contributing to the SoundScape project.*
-
-# Code of conduct
-Please be respectful and courteous to other contributors and users of the project. Do not use abusive, offensive, or discriminatory language. Do not harass, troll, or spam anyone. Do not post any personal or sensitive information. Violation of these rules may result in banning from the project.
-
-# Reporting issues
-If you encounter any bugs, errors, or unexpected behaviors while using the project, please report them as issues on GitHub. Before creating a new issue, please check if there is already an existing issue that addresses the same problem. If not, create a new issue with a clear and descriptive title, a detailed description of the problem, the steps to reproduce it, and any relevant screenshots or error messages.
-
-# Suggesting enhancements
-If you have any ideas or suggestions for improving the project, such as adding new features, improving the performance, or enhancing the user experience, please share them as issues on GitHub. Before creating a new issue, please check if there is already an existing issue that discusses the same idea. If not, create a new issue with a clear and descriptive title, a detailed explanation of your idea or suggestion, and any relevant examples or mockups.
-
-# Submitting pull requests
-If you want to contribute to the project by fixing bugs, implementing features, or improving the documentation, you are welcome to submit pull requests on GitHub. Before creating a pull request, please follow these steps:
-
-- Fork the repository and create a new branch for your changes.
-- Make sure your code follows the PEP 8 style guide and is well-commented and documented.
-- Make sure your code is tested and does not introduce any new errors or warnings.
-- Make sure your code does not conflict with the existing code base and can be merged smoothly.
-- Write a clear and concise commit message that describes what you have done and why.
-- Write a clear and concise pull request title and description that summarizes your changes and references any related issues.
-- Wait for the project maintainers to review your pull request and provide feedback or approval.
-
-### Alternatively contribute using GitHub Desktop
-
-1. **Open GitHub Desktop:**
-   Launch GitHub Desktop and log in to your GitHub account if you haven't already.
-
-2. **Clone the Repository:**
-   - If you haven't cloned the SoundScape repository yet, you can do so by clicking on the "File" menu and selecting "Clone Repository."
-   - Choose the SoundScape repository from the list of repositories on GitHub and clone it to your local machine.
-
-3. **Switch to the Correct Branch:**
-   - Ensure you are on the branch that you want to submit a pull request for.
-   - If you need to switch branches, you can do so by clicking on the "Current Branch" dropdown menu and selecting the desired branch.
-
-4. **Make Changes:**
-   Make your changes to the code or files in the repository using your preferred code editor.
-
-5. **Commit Changes:**
-   - In GitHub Desktop, you'll see a list of the files you've changed. Check the box next to each file you want to include in the commit.
-   - Enter a summary and description for your changes in the "Summary" and "Description" fields, respectively. Click the "Commit to <branch-name>" button to commit your changes to the local branch.
-
-6. **Push Changes to GitHub:**
-   After committing your changes, click the "Push origin" button in the top right corner of GitHub Desktop to push your changes to your forked repository on GitHub.
-
-7. **Create a Pull Request:**
-  - Go to the GitHub website and navigate to your fork of the SoundScape repository.
-  - You should see a button to "Compare & pull request" between your fork and the original repository. Click on it.
-
-8. **Review and Submit:**
-   - On the pull request page, review your changes and add any additional information, such as a title and description, that you want to include with your pull request.
-   - Once you're satisfied, click the "Create pull request" button to submit your pull request.
-
-9. **Wait for Review:**
-    Your pull request will now be available for review by the project maintainers. They may provide feedback or ask for changes before merging your pull request into the main branch of the SoundScape repository.
-
-⭐️ Support the Project
-If you find this project helpful, please consider giving it a star on GitHub! Your support helps to grow the project and reach more contributors.
+*This file contains the guidelines for contributing to the SoundScape project.*
+
+# Code of conduct
+Please be respectful and courteous to other contributors and users of the project. Do not use abusive, offensive, or discriminatory language. Do not harass, troll, or spam anyone. Do not post any personal or sensitive information. Violation of these rules may result in banning from the project.
+
+# Reporting issues
+If you encounter any bugs, errors, or unexpected behaviors while using the project, please report them as issues on GitHub. Before creating a new issue, please check if there is already an existing issue that addresses the same problem. If not, create a new issue with a clear and descriptive title, a detailed description of the problem, the steps to reproduce it, and any relevant screenshots or error messages.
+
+# Suggesting enhancements
+If you have any ideas or suggestions for improving the project, such as adding new features, improving the performance, or enhancing the user experience, please share them as issues on GitHub. Before creating a new issue, please check if there is already an existing issue that discusses the same idea. If not, create a new issue with a clear and descriptive title, a detailed explanation of your idea or suggestion, and any relevant examples or mockups.
+
+# Submitting pull requests
+If you want to contribute to the project by fixing bugs, implementing features, or improving the documentation, you are welcome to submit pull requests on GitHub. Before creating a pull request, please follow these steps:
+
+- Fork the repository and create a new branch for your changes.
+- Make sure your code follows the PEP 8 style guide and is well-commented and documented.
+- Make sure your code is tested and does not introduce any new errors or warnings.
+- Make sure your code does not conflict with the existing code base and can be merged smoothly.
+- Write a clear and concise commit message that describes what you have done and why.
+- Write a clear and concise pull request title and description that summarizes your changes and references any related issues.
+- Wait for the project maintainers to review your pull request and provide feedback or approval.
+
+### Alternatively contribute using GitHub Desktop
+
+1. **Open GitHub Desktop:**
+   Launch GitHub Desktop and log in to your GitHub account if you haven't already.
+
+2. **Clone the Repository:**
+   - If you haven't cloned the SoundScape repository yet, you can do so by clicking on the "File" menu and selecting "Clone Repository."
+   - Choose the SoundScape repository from the list of repositories on GitHub and clone it to your local machine.
+
+3. **Switch to the Correct Branch:**
+   - Ensure you are on the branch that you want to submit a pull request for.
+   - If you need to switch branches, you can do so by clicking on the "Current Branch" dropdown menu and selecting the desired branch.
+
+4. **Make Changes:**
+   Make your changes to the code or files in the repository using your preferred code editor.
+
+5. **Commit Changes:**
+   - In GitHub Desktop, you'll see a list of the files you've changed. Check the box next to each file you want to include in the commit.
+   - Enter a summary and description for your changes in the "Summary" and "Description" fields, respectively. Click the "Commit to <branch-name>" button to commit your changes to the local branch.
+
+6. **Push Changes to GitHub:**
+   After committing your changes, click the "Push origin" button in the top right corner of GitHub Desktop to push your changes to your forked repository on GitHub.
+
+7. **Create a Pull Request:**
+  - Go to the GitHub website and navigate to your fork of the SoundScape repository.
+  - You should see a button to "Compare & pull request" between your fork and the original repository. Click on it.
+
+8. **Review and Submit:**
+   - On the pull request page, review your changes and add any additional information, such as a title and description, that you want to include with your pull request.
+   - Once you're satisfied, click the "Create pull request" button to submit your pull request.
+
+9. **Wait for Review:**
+    Your pull request will now be available for review by the project maintainers. They may provide feedback or ask for changes before merging your pull request into the main branch of the SoundScape repository.
+
+⭐️ Support the Project
+If you find this project helpful, please consider giving it a star on GitHub! Your support helps to grow the project and reach more contributors.