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

    • 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  
    • This AMD RX 9070 16GB GPU that performs close to Nvidia 5070 is under $600 by Sayan Sen With the memory shortage that's prevalent nowadays, discounts are super-hard to get. As such we post good deals whenever they pop up. Recently, we covered a few great discounts on SSDs wherein you can get a 4TB TeamGroup NVMe PCIe Gen4 drive for just $400 thanks to a special coupon. If you want a faster product but don't need all that capacity, you can also opt for Samsung's 990 PRO 2TB that is on sale for its lowest price in over three months. Let's say though that you are on the hunt for a 1440p gaming card. In that case AMD's RX 9070 non-XT can help, and with its 16GB VRAM, you can also run AI models locally without worrying about bottlenecking (check out our recent 9070 GRE reviews for gaming and productivity to get an idea). The PowerColor Reaper variant of the RX 9070 is currently on sale for just $580 which is a very good price in the current state of affairs (purchase link under the specs table down below). The Reaper cooler on this 9070 uses a triple‑fan design with ring‑blade fans, paired with premium dual ball bearings to extend lifespan and reduce friction. "Intelligent" fan control allows the fans to remain idle at lower temperatures, only spinning up when the GPU is under load. A nickel‑plated copper base makes direct contact with both the GPU and memory modules, helping to spread heat evenly. PowerColor also applies Honeywell PTM7950 phase‑change thermal interface material (TIM), which fills microscopic gaps between the die and heatsink for more efficient thermal transfer. The fan shroud is shorter in height as the firm has made it such that it can be used in certain SFF (small form factor) cases. The technical specifications of the Reaper RX 9070 are given in the table below: Specification Value Stream Processors 3584 Units Video Memory 16GB GDDR6 Memory Speed 20.0 Gbps Memory Interface 256-bit Engine Clock Game Clock: up to 2070 MHz Boost Clock: up to 2520 MHz Bus Standard PCI Express 5.0 x16 Display Connectors 1 x HDMI 2.1b, 3 x DisplayPort 2.1a Maximum Resolution DisplayPort: 7680 × 4320 HDMI: 7680 × 4320 Board Dimensions 289mm × 111mm × 41mm 304mm × 127mm × 42mm (with bracket) Slot 2 Minimum System Power Requirement 600W Power Connectors Two 8-pin PCI Express Get the PowerColor Reaper RX 9070 at the links below (you get only a 90-day warranty on Woot): PowerColor Reaper Radeon RX 9070 16GB Graphics Card (RX9070 16G-A): $579.99 (Sold and Shipped by Amazon US) (Was: $700) PowerColor Reaper Radeon RX 9070 16GB Graphics Card (RX9070 16G-A): $559.99 (Sold and Shipped by Woot US) Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
    • Are they marketed as an entry into astronomy or astrophotography? I do astrophotography. With big rigs, lots of computers, cables and headaches. I love it. And by learning this ridiculously complex hobby, I’ve learned about the objects I’m shooting. Astronomy followed from photography.
    • Microsoft confirms Recycle Bin bug across all versions of Windows by Usama Jawad A couple of days ago, we reported that the latest Patch Tuesday update has seemingly resulted in a lot of issues for many users, including OneDrive and Dropbox access problems, BitLocker recovery lockouts, and BSODs. Although Microsoft is yet to acknowledge these bugs, it has confirmed another, relatively smaller issue across all supported versions of Windows. In an update on its Windows Release Health Dashboard, Microsoft has confirmed that after installing June's Patch Tuesday update (KB5094126), you'll experience unexpected behavior when leveraging Recycle Bin. Basically, when you attempt to delete an item from the Recycle Bin, the confirm dialog will show you the internal file name of that content rather than the actual name. For example, the file may be named abc.png, but the confirm dialog will ask if you're sure that you want to permanently delete $Rxxxxx.png from the Recycle Bin. This is pretty much it for the scope of the bug itself; it just displays the wrong name in the confirm dialog. The correct name will be shown in the list view of the Recycle Bin and if you restore the file, it will return with the correct name as well. This issue affects pretty much all supported versions of Windows client and server, including: Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSB 2016 Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012 As things currently stand, Microsoft is working on a concrete solution that will be released in a "future" Windows update. It remains to be seen if the firm will wait till the next Patch Tuesday or roll out an out-of-band (OOB) fix. The good news is that commercial customers can deploy a workaround right now, but they will have to reach out to Microsoft Support for Business for additional details.
  • 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
      579
    2. 2
      +Edouard
      184
    3. 3
      PsYcHoKiLLa
      75
    4. 4
      Michael Scrip
      72
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!