Recommended Posts

Gmail Notifier Plus 3.6 has been released. Thanks to all who donated, tested and submitted bugs.

Info on Gmail Notifier Plus is here Gmail Notifier Plus Readme

The latest Installer and version/release can always be found here: http://shellscape.org/#gnp

Other Downloads can always be found here: https://github.com/s...-Plus/downloads

For my own sanity, I won't be replying to support requests or error reports on the forums here. But members should feel free to help out other members. Please report issues here:https://github.com/s...ier-Plus/issues

Changes in 3.6 include:

  • Gmail Notifier Plus now works on Windows 8.
  • Significant memory and resource usage improvements.
  • Fixed errors related to sleep and hibernate.
  • Fixed custom sound and browser selection.
  • Added a tray icon menu identical to the jumplist menu.
  • Updated the Windows Installer used to build the installer.
  • Updated the installer to support upgrades without having to remove a previous version.
  • Removed the version number on the installer given that we're auto-upgrading without MSI.
  • Now showing the About window after the first start after an auto-upgrade.

For a full list of specific changes, see https://github.com/s.../commits/master

If you've been using Gmail Notifier Plus a long while and have been enjoying the updates, have had a feature request fulfilled or are a first time user and really like the app, please consider donating. There is a link to donate in the jumplist, the about dialog and the preferences dialog.

Link to comment
https://www.neowin.net/forum/topic/1107333-gmail-notifier-plus-36/
Share on other sites

  • 2 weeks later...

Hi andrew_, love your gmail checker, but still doesn't work on win8 for me :/

Tried the installer version and the portable.


[Window Title]
Gmail Notifier Plus Error
[Main Instruction]
An unhandled exception occurred:
[Content]
Error ID: 97061af5-ca79-411e-9fa8-3bd5ad696c29
Exception decrypting. Decryption failed. Schl?ssel ist im angegebenen Status nicht g?ltig.

[Expanded Information]
bei GmailNotifierPlus.Utilities.DataProtector.Decrypt(Byte[] cipherText, Byte[] optionalEntropy)
bei GmailNotifierPlus.Utilities.EncryptionHelper.Decrypt(String encryptedValue)
bei ReadaccountFromXml(XmlReaderDelegator , XmlObjectSerializerReadContext , XmlDictionaryString[] , XmlDictionaryString[] )
bei System.Runtime.Serialization.ClassDataContract.ReadXmlValue(XmlReaderDelegator xmlReader, XmlObjectSerializerReadContext context)
bei System.Runtime.Serialization.XmlObjectSerializerReadContext.ReadDataContractValue(DataContract dataContract, XmlReaderDelegator reader)
bei System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
bei System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Int32 id, RuntimeTypeHandle declaredTypeHandle, String name, String ns)
bei ReadArrayOfaccountFromXml(XmlReaderDelegator , XmlObjectSerializerReadContext , XmlDictionaryString , XmlDictionaryString , CollectionDataContract )
bei System.Runtime.Serialization.CollectionDataContract.ReadXmlValue(XmlReaderDelegator xmlReader, XmlObjectSerializerReadContext context)
bei System.Runtime.Serialization.XmlObjectSerializerReadContext.ReadDataContractValue(DataContract dataContract, XmlReaderDelegator reader)
bei System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
bei System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Int32 id, RuntimeTypeHandle declaredTypeHandle, String name, String ns)
bei ReadconfigFromXml(XmlReaderDelegator , XmlObjectSerializerReadContext , XmlDictionaryString[] , XmlDictionaryString[] )
bei System.Runtime.Serialization.ClassDataContract.ReadXmlValue(XmlReaderDelegator xmlReader, XmlObjectSerializerReadContext context)
bei System.Runtime.Serialization.XmlObjectSerializerReadContext.ReadDataContractValue(DataContract dataContract, XmlReaderDelegator reader)
bei System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
bei System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name, String ns)
bei System.Runtime.Serialization.DataContractSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
bei System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
bei System.Runtime.Serialization.XmlObjectSerializer.ReadObject(XmlDictionaryReader reader)
bei GmailNotifierPlus.Utilities.Serializer.DeserializeContract[T](String xml)
bei GmailNotifierPlus.Config.Init()
bei GmailNotifierPlus.Program.<Main>b__0()
bei Shellscape.Program.OnMainInstanceStarted()
bei Shellscape.Program.Run[TForm](String[] arguments)
[^] Details ausblenden [OK]
[Footer]
Press CTL + C to copy this error to the clipboard.
[/CODE]

  • 4 weeks later...

[Thread Cleaned]

Please try to keep this on topic. The op has requested that all support requests be submitted via Github, so that he doesn't have to track support requests across multiple forums. This isn't the place to argue about his reasoning for doing that.

I recently switched to Windows 8 full time and found that there's a bug in .NET 4 with regard to launching URLs. The old method we'd been using worked well on previous versions of windows, so I'm not sure whats happened on windows. I've documented the issue here, if you're curious about it: https://github.com/s...Plus/issues/110

I'll be pushing out a new build shortly to remedy this.

Edit:

Turns out that this is a bug with chrome and the latest version () on Windows 8. The workaround is to set the browser to Chrome for each of your accounts. For some reason on Windows 8, when the default system url handler launches chrome, it snips the hash in the url argument and anything after it (eg. http://mail.google.com/mail#inbox/13ae97fd0f7e1464'>http://mail.google.com/mail#inbox/13ae97fd0f7e1464 becomes http://mail.google.com/mail). I'll be submitting this to the chrome team to take a look at.

Found another interesting Windows 8 quirk. The mailto handling code that worked in previous versions of Windows doesn't work in Win8. Win8 goes a different route with different registry settings. I'll be fixing this (theres a bit of work involved) for a maintenance release.

  • 4 weeks later...
  • 1 month later...

Github just announced that they would be ceasing the availablibity of project downloads on their site. While I think this is an incredibly stupid move, there's not much I can do about it.

I've setup a repo at bitbucket and have placed the latest downloads there. Please see https://bitbucket.org/shellscape/gmail-notifier-plus/downloads for downloading Gmail Notifier Plus moving forward.

Great news. Chrome 24 was released today and it fixes the bug on Windows 8 with launching urls from a system command with a hash at the end. What's that mean for GNP? It means that opening emails directly from GNP works again in that system scenario.

  • Like 2

Just a heads up for anyone still following the project - because Github is discontinuing the api which allowed GNP to check for a new version, the auto-upgrade wont work for the next version. I've since moved everything to bitbucket, but the code in the current version relies on Github. I honestly didn't think that'd be going away anytime soon. Lesson learned. I'm going to write an intermediate web layer for my own server that'll handle the upgrade notice, but that'll come in the next version, which you'll have to install manually, unfortunately.

  • 2 months later...
  • 4 weeks later...
  • 9 months later...
  • 2 weeks later...

Well I've done all the legwork to investigate the possibility and I've got a project in progress. It's definitely doable, although it'll look a little different than the Windows version (naturally). I'll start a new thread when I have an alpha working.

This topic is now closed to further replies.
  • Posts

    • Wow, imagine you dump hundreds of hours into completing things and unlocking stuff and you lose it all. Back in the day when cheats were built into games, you could at least unlock things again that way without spending hundreds of hours again. But those days are long gone for some reason as no one builds cheats into games anymore. So it's even more painful that studio that's on its 6th installment **** it up so badly.
    • Spotify finally removes the disco ball app icon in the latest update by Ivan Jenic Image: Spotify Spotify has just released an update that removes its now infamous disco ball icon. The update reverts the app icon to the familiar flat green logo after weeks of mixed reactions online. The icon arrived on May 13 as part of the company's 20th anniversary celebration and was always intended to be temporary, though Spotify only confirmed that after the backlash started. The disco ball took the internet by storm, as the reception was split. A vocal group of users called it ugly and disorienting, with some iOS users noting that the 3D glowing effect made the app look like it was stuck mid-update. On the other end, the icon picked up a following of its own. Its retro, three-dimensional look immediately stood out against the flat, minimalist aesthetic that has dominated app design for years. It even started a small movement, spawning what people started calling "discomorphism," a mashup of disco and skeuomorphism. Other brands started posting disco ball versions of their own logos, probably in an effort to ride the wave of memes that flooded the internet during late May. Spotify has had a turbulent relationship with its user base lately. Besides the disco ball icon, which certainly wasn't appreciated by everyone, the company has also received backlash for its willingness to include AI-generated music on its platform. On May 17, Spotify promised the old icon would return “in a few weeks.” And now it looks like that time has finally arrived. So, whether you liked the disco ball or it made you uncomfortable, it’s now gone for good. The next time you update the Spotify app on your phone, the old, flat-design icon will return.
  • Recent Achievements

    • One Year In
      slackerzz earned a badge
      One Year In
    • One Year In
      highriskpaym earned a badge
      One Year In
    • One Month Later
      highriskpaym earned a badge
      One Month Later
    • Week One Done
      highriskpaym earned a badge
      Week One Done
    • Week One Done
      FBSPL earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      519
    2. 2
      PsYcHoKiLLa
      197
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      84
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!