Downloads:
5,935
Downloads of v 1.11.2:
43
Last Update:
04 Oct 2020
Package Maintainer(s):
Software Author(s):
- Aleab
Tags:
toastify spotify keyboard hotkeys- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
toastify
- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
5,935
Downloads of v 1.11.2:
43
Maintainer(s):
Software Author(s):
- Aleab
toastify
- 1
- 2
- 3
Some Checks Are Exempted or Have Failed
Not All Tests Have Passed
Validation Testing Failed
Verification Testing Exemption:
Scan Testing Resulted in Flagged:
This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.
We recommend clicking the "Details" link to make your own decision on installing this package.
This package was rejected on 08 Nov 2020. The reviewer chocolatey-ops has listed the following reason(s):
Toastify shows a popup, toast style, dialog on track change and it allows you to use global hot keys for Play/Pause, Next, Previous etc. Toastify is developed using C# and WPF.
Log in or click on link to see number of positives.
- ToastifyInstaller.exe (1701e58bb19f) - ## / 69
- toastify.1.11.2.nupkg (f9524d8dd6e7) - ## / 62
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
toastify 1.8.3 | 3525 | Thursday, April 7, 2016 | Approved | |
toastify 1.7.8 | 513 | Wednesday, October 21, 2015 | Approved | |
toastify 1.7.3 | 557 | Monday, March 23, 2015 | Approved | |
toastify 1.6.6 | 660 | Tuesday, August 19, 2014 | Unknown | |
toastify 1.6.3 | 455 | Wednesday, June 25, 2014 | Unknown |
Toastify v1.11.2 - 11/9/2019
- Fixed issue with API token refresh.
- Fixed major issue with the authorization flow (#110, #111, #118, #127).
- Fixed "paused" issue (#110).
- Fixed installer re-creating and moving the desktop icon.
- Fixed some more things and broke others, probably...
# Toastify v1.11.1 - 16/2/2019
- Removed the buggy Authentication window; the auth process now opens the default browser instead. This fixes issues #107 and #109.
# Toastify v1.11.0 - 14/2/2019
- Toastify can now use Spotify's Web API
- The use of the Web API is optional (enabled by default) and allows Toastify (provided the user has completed the authorization flow) to:
- Get more accurate information about the current song's title and artist(s)
- Fetch the current song's album art
- Known Issues
- The authorization may occasionally take quite some time (10-20 seconds), so certain features might be unavailable until the process completes.
- The toast may occasionally not update the current song if it's changed too frequently and/or too fast (e.g. when you "spam" the Next Song button).
# Toastify v1.10.14 - 19/9/2018
- Fixed a major issue with Toastify waiting indefinitely for Spotify at startup when the user has Spotify Premium.
# Toastify v1.10.13 - 16/9/2018
- Fixed an issue where the current song wasn't being updated in the toast when it was changed in Spotify while paused.
- Fixed an issue with song titles or artist names containing an hyphen (commit 88243da).
- Added Toastify Broadcaster, a WebSocket-based event broadcaster.
- NOTE: Toastify now needs .NET Framework 4.7.2 to run. The new installer should download and install it automatically; in case it doesn't, you can find it here.
# Toastify v1.10.12 - 3/9/2018
- Fixed major issue with hotkey settings not being loaded correctly (#93).
- Fixed issue with the Windows Key modifier never being set correctly.
- Fixed issue with Toastify directory in %LocalAppData% not being created (#94).
# Toastify v1.10.11 - 31/8/2018
- ❗️ Restored the toast using a temporary workaround to fetch the current song's info (#86).
- This workaround only allows us to fetch the current song's artist and title. The album art can't be updated; the song progress bar has been temporarily disabled.
- Added Stop hotkey (#88).
- Fixed an issue with the Store version of Spotify (#89).
- Improved the way Toastify checks if an hotkey is already in use.
- The user is now notified of an invalid hotkey as soon as it's changed instead of after it's been saved.
- Added automation properties to support screen readers (#76).
# Toastify v1.10.9 - 10/8/2018
- ❗️ Toastify should now start correctly with the latest version of Spotify (1.0.87.*)
- ❗️ Due to recent changes on Spotify's side, the toast notifications have been disabled (#86)
- Removed the Toast tab from the settings window
- Never show the toast on demand: the ShowToast global hotkey is still there but does nothing
- The installer and uninstaller have been changed slightly (see commit ee88029)
- Bug fixes (#71, #74, #75)
# Toastify v1.10.8 - 1/4/2018
- Fixed the "Launch on startup" setting still resetting to its default value after latest update (#52, #57)
- Fixed unexpected crash when trying to bind mouse buttons/wheel as hotkeys (#60)
- Toastify needs your feedback ❗️
- Would you like a Windows Store release of Toastify? Vote here.
# Toastify v1.10.7 - 31/3/2018
- Hotfixed auto-updater not working
- Hotfixed Changelog viewer not working as expected
# Toastify v1.10.5
- Added support for proxy configuration (#46)
- Added MWheelUp/MWheelDown to the allowed mouse buttons/actions for hotkeys (#47)
- Reduced minimum toast display time to 100ms (#51)
- Fixed certain saved hotkeys and settings reverting to their default values upon restart (#52, #55)
- Fixed saving of Top/Height when dragging the toast (#58)
- Implemented an auto-updater to automatically update Toastify when a new version is released (must be enabled in the settings first)
- Implemented a changelog viewer that will pop up the first time Toastify is launched after an update
- Minor bug fixes
- Acknowledgments
- Huge thanks to @trevtrevtrev for their availability to test out the software throughout the development of #46!
- Also thumbs up to @JohnnyCrazy for fixing #58! 👍
# Toastify v1.10.4 - 10/3/2018
- Automatically disable Analytics if connection to Google Analytics is not available (#41).
- Fixed toast default position for scale factors different from 100%.
- Fixed error when changing the "FadeOut Time" to a value outside the range of allowed values (#38).
- Added a couple of command-line arguments (see a2bdc95).
- Thanks to @hartmark for pull requests #39 and #40! 👍
# Toastify v1.10.3 - 7/3/2018
- Fixed critical bug introduced by the latest version of Spotify v1.0.75.483.g7ff4a0dc (#31).
- Unfortunately, some actions and functionalities had to be removed in the process because of how things changed in Spotify itself. The most notable removed feature is the possibility of controlling Spotify's in-app volume. See #31, 9cb83d1 and 0047a22 for details.
- Fixed critical bug that prevented people with a broken() config file from launching the app (#30).
- () broken = a config file that was missing certain settings; this caused these settings to be deserialized with their type default value, which in some cases resulted in an invalid value being passed to certain UI controls.
- Removed unnecessary modifier requirement on hotkeys (#32).
- Added the possibility to use mouse side buttons (XButton1/Mouse4 and XButton2/Mouse5) in hotkey combinations.
- Toastify will now pass any command line argument to Spotify when launching it.
# Toastify v1.10.2 - 28/1/2018
- Added support for multi-screen configurations (#28).
# Toastify v1.10.1 - 15/1/2018
- Toastify will now show a live preview of the Toast when editing the settings (#19).
- The toast will now consistently show the message "[UNKNOW TRACK TYPE]" and update the current track time when playing a podcast.
- (Podcasts are currently not supported by neither the unofficial Spotify local APIs nor by the official web APIs, so there's no way to get the name of the podcast or the current episode!)
- Fixed hotkeys not resetting properly when using the Default or Default All buttons (#18).
- [Error logging] Most errors and exceptions are now logged to the "Toastify*.log" file located in "%LocalAppData%\Toastify". Please, include that file to any issue report related to errors, bugs or crashes.
- Reduced average CPU usage (#22).
- Fixed an issue that caused Spotify window's position and dimensions to be reset every time Toastify terminated Spotify's process (#23).
- Toastify shouldn't crash anymore on 32 bit versions of Windows (66f7e08, fc16caa).
- Minor fixes and improvements (c713a30, cdbd79e, 895a4f1, d6fbb01).
# Toastify v1.10.0 - 13/10/2017
- Fixed a random and occasional startup error that prevented Toastify from functioning correctly when Spotify was lauched by Toastify and Spotify happened to take too much time to start (#13).
- Made the Default button in the settings window work contextually based on the current opened tab. A Default All option has been added to reset all settings at once (#15).
- Fixed a startup error that caused the application to crash without any error message (#16).
# Toastify v1.9.8 - 16/9/2017
- Added visual clues to make Artist and Track names unambiguous, thanks to @Vankog 👍 (#12).
- Made the order of Artist and Track customizable (#11).
- Redesigned the Toast tab in the Settings to allow further customization of the toast itself (#9).
- Added a song progress bar to the toast.
- Added a preview of the Toast when changing the Settings.
- (The Save button needs to be clicked for the changes to be visible)
- Fixed version number and homepage url not showing up in the About window.
- Re-implemented data collection.
- (You have to opt-out again, if you already did in previous versions)
# Toastify v1.9.6 - 3/9/2017
- Fixed an issue with the latest version of Spotify (v1.0.62.*) (#8)
# Toastify v1.9.5 - 11/7/2017
- Fixed hotkeys being sometimes triggered multiple times with a single key-press.
- Fixed Toast behaviour with fullscreen videogames.
- Toastify will always try to show the Toast as the top most window; however, if it is not possible, because a fullscreen videogame is running, then the Toast will not be showed and the videogame window will always mantain the focus.
- This behaviour can be changed to never show the Toast if a fullscreen (standard fullscreen or 'borderless windowed' fullscreen) videogame is running.
- Re-added option to change system volume instead of just Spotify's (#5).
# Toastify v1.9.4 - 5/7/2017
- Definitely fixed error related to issue #3.
- Added an option to use Spotify's volume control instead of the Windows volume mixer (#4).
- When using the Windows volume mixer, the volume increment can now be customized.
- FastForward/Rewind hotkeys (and VolumeUp/VolumeDown, when using Spotify's volume control) now work as intended.
- Removed AutoHotkey dependency.
# Toastify v1.9.3 - 2/7/2017
- Toastify will automatically terminate when Spotify is closed.
- The toast can fade-in if a fullscreen app (e.g. a videogame) is set to windowed borderless mode.
- Toastify doesn't require admin privileges anymore if using the Windows Store version of Spotify.
- Fixed a startup error that caused Toastify to not work as intended (#3).
- Changed target .NET Framework to 4.5.
# Toastify v1.9.2 - 29/6/2017
- Fixed an error that caused the toast's song to be different from the one played.
- Added support for the Windows Store version of Spotify (Windows 10).
# Toastify v1.9.1 - 22/6/2017
- Play state is checked also when the track changes: this should prevent a random, occasional glitch causing the current track to never being updated when paused.
- The toast never fades in when a fullscreen application is running (e.g. a videogame): this prevents the fullscreen application to go to the background when the toast is displayed.
# Toastify v1.9.0 - 6/6/2017
- Changes from nachmore's v1.8.3:
- Using JohnnyCrazy's SpotifyAPI-NET project.
- The toast doesn't fade out when pressing hotkeys while it is still visible.
- The toast fades out immediately if the ShowToast hotkey is pressed while it is still visible.
- The song's title is displayed after the artist name.
- The toast shows correct information about the current song when paused.
- Upgraded to .NET Framework 4.5.2.
# Toastify 1.8.3 - 10/3/2016
- BUG: Toastify was no longer minimizing Spotify on startup (when the setting was set) - thanks darrenshare!
- Exception handling cleanup
# Toastify 1.8.2 - 8/3/2016
- Fixed crash when clicking on toast (that should show Spotify)
# Toastify 1.8.0 - 8/3/2016
- Toastify now loads album art again
- Toastify no longer causes Spotify to consume copious amounts of system resources (Spotify readded the current playing song to the title).
- - We lose full control of Spotify, such as thumbs up / down :(
- Added setting to allow you to keep your computer awake while Spotify is playing music
- We have started collecting anonymous usage stats - opt out in Settings.
# Toastify 1.7.8 - 26/8/2015
- Fixed toast stealing focus (thanks to everyone who reported this)
- Fixed version constantly bugging to update
# Toastify 1.7.7 - 12/8/2015
- Fixed incorrect binaries pushed in 1.7.6 which caused the toasts to disappear on some devices
# Toastify 1.7.6 - 10/8/2015
- Support for extracting Artist / Song from the latest version of Spotify (thanks arosner3 and emptythecache!)
- Fixed empty toast during launch
- Fixed fps drop (in at least one case) as per https://toastify.codeplex.com/discussions/641430
# Toastify 1.7.5 - 23/3/2015
- Experimental hotkeys for thumbs up and thumbs down (fixes a long standing request, #11693)
- 13363 - use regular - instead of Unicode dash for "artist - title" to help with some older bits of ASCII only software
# Toastify 1.7.4 - 22/3/2015
- Added a setting to minimize Spotify on launch
- Feature Request 13516: Save current track to file (useful for scenarios such as piping the current playing track to Open Broadcaster Software etc.)
- Installer will now terminate any lingering ChromeDriver processes
# Toastify 1.7.3 - 20/3/2015
- Remove warning that hotkeys without a modifier are invalid (since they were, in fact, valid). Tracked under issue #13510
- More robust killing of Spotify (cleanly and eventually forcefully) when exiting Toastify
- Avoid potential for duplicate hotkey entries in the Settings list
# Toastify 1.7.2
- Corrected version (bug #13508)
- Added support for Win key in hotkeys (thanks bwp11!)
# Toastify 1.7.1
- Support for Spotify v1
- This support is much more invasive than previous versions due to changes made by Spotify (primarily the removal of the Artist / Track from the title bar). It has some benefits, but also comes with some down sides (we must restart Spotify when launching Toastify). There will also be bugs.
- Support for Toast positioning on high-DPI screens, you may need to re-position your Toasts
-
- spotify (≥ 1.1.41.634)
Ground Rules:
- This discussion is only about toastify and the toastify package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or toastify, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
sergiotecnico (maintainer) on 08 Sep 2020 18:11:32 +00:00:
User 'sergiotecnico' (maintainer) submitted package.
chocolatey-ops (reviewer) on 08 Sep 2020 18:48:23 +00:00:
toastify has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
chocolatey-ops (reviewer) on 09 Sep 2020 03:58:33 +00:00:
toastify has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/93036acf574c15dfe7a925aaa4e74c84 for details.
This is an FYI only. There is no action you need to take.
gep13 (reviewer) on 09 Sep 2020 07:42:04 +00:00:
If you are going to be looking after this package going forward, can you please update the packageSourceUrl in the nuspec file to point at the new location of the files?
Or, if you are going to help with the maintenance in the existing repository, that is fine, just need to make sure which one is being used.
It would also be good to start including checksums for the downloaded files, so that these can be verified at the time of installation.
Thanks
sergiotecnico (maintainer) on 09 Sep 2020 14:22:48 +00:00:
User 'sergiotecnico' (maintainer) submitted package.
chocolatey-ops (reviewer) on 09 Sep 2020 14:53:11 +00:00:
toastify has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
chocolatey-ops (reviewer) on 09 Sep 2020 15:06:34 +00:00:
toastify has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/ac6f8e885812b4156d2dc32da0f4e638 for details.
This is an FYI only. There is no action you need to take.
gep13 (reviewer) on 10 Sep 2020 06:24:24 +00:00:
There are a couple of slight changes that I would like to see made to this, and then we can move forward with getting it approved.
Can you change the licenseUrl in the nuspec file to be the following:
https://github.com/aleab/toastify/blob/master/LICENSE
In the chocolateyInstall.ps1 file, you are using the $url64 variable, but this is no longer declared. Can you please remove it?
Within the author element of the nuspec file, there is Geoff's name. This isn't correct, this should be the name of the person who actually writes the software, in this case aleab.
chocolatey-ops (reviewer) on 30 Sep 2020 06:28:29 +00:00:
We've found toastify v1.11.2 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.
sergiotecnico (maintainer) on 04 Oct 2020 14:23:07 +00:00:
User 'sergiotecnico' (maintainer) submitted package.
chocolatey-ops (reviewer) on 04 Oct 2020 14:55:06 +00:00:
toastify has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
chocolatey-ops (reviewer) on 24 Oct 2020 14:24:11 +00:00:
We've found toastify v1.11.2 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.
chocolatey-ops (reviewer) on 02 Nov 2020 09:30:34 +00:00:
toastify has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
chocolatey-ops (reviewer) on 08 Nov 2020 14:24:23 +00:00:
Unfortunately there has not been progress to move toastify v1.11.2 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.
Status Change - Changed status of package from 'submitted' to 'rejected'.