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

    • Normally, I admit when a title is clickbait (unfortunately, it's become somewhat necessary in AI-dominated news sections today), but in this case, all supported versions is implied and doesn't need to be spelled out in the title. Of course, I'm covering a Patch Tuesday update but that is only available to supported Windows SKUs. All our coverage relates to supported Windows software and SKUs only unless we expressly state that it's "unsupported", "unofficial", or "third-party". I'm sorry, but supported/official SKUs don't need to be spelled out as such in every Neowin headline.
    • ALL versions or ALL SUPPORTED versions? Neowin does it again.
    • But the reality is it will work for people's needs, and they don't care about the technology that makes it. Clearly not everyone's needs, but that low end space where personal laptops were only used to type emails, watch content and browse websites, but they didn't want to do that on a small screen device. Heck, writing that out I can now see the connection and reason it'll do so well. Apple is about experience. If the experience is bad, they don't release it. Low end Windows laptop manufacturers up until this point have not taken that into consideration ever before, so slow laggy usage with brittle slimey plastic shells were common. I hope that the low end space at least creates better physical products that last a bit longer, and if Microsoft get their act together, they could also have a solid OS on such low end hardware that would actually make the experience work for what the hardware was intended for. The fact that the CPU is a "cellphone", sorry mobile phone processor is irrelevant. It's about the experience, and so far, that sounds quite solid.
    • Hello, Bonjour is Apple's implementation of a multicast-DNS service, which allows devices running Apple's software and/or hardware to find each other on your local network.  I believe the Windows version was last updated around 2010. If you do not need it, you can stop and disable the Bonjour service in the Services Control Manager (filename: SERVICES.MSC).  Once you have done that, the operating system will no longer attempt to load the service. Regards, Aryeh Goretsky  
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      581
    2. 2
      +Edouard
      184
    3. 3
      PsYcHoKiLLa
      75
    4. 4
      Michael Scrip
      73
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!