Recommended Posts

The next version of GNP is ready for testing. The download contains a debug build of GNP with debug symbol files (which makes the download larger) so that any error output with contain more information to help fix any issues. Once I feel it's stable, I'll put together a final release build. I've been running this version on my system for the last two weeks and it's very stable here.

Changes in 3.0 b1 include:

  • New preferences dialog (again) based on the Windows Control Panel UX. I've made a lot of effort to use the same system resources, layout and measurements that the actual control panel does in order to give this a native appearance and feel.
  • Reorganized the jumplist commands and jumplist email display. Should make it more obvious what the default account is for.
  • Improved the logic for displaying emails and fixed the toast email display.
  • Improved locale (i18n) file layout.
  • Improved lots of internal mechanisms.
  • Fixed all of the issues that were reported (if it was possible) since the last version.

For a full list of specific changes, see the COMMIT-LOG file or https://github.com/shellscape/Gmail-Notifier-Plus/commits/master

Please note: since the locale file layout/format changed for this version, most of the old locales were left out of the beta build. I'm hoping to get them back into the app for the final version, but I only have access to so many folks that speak another language. If you speak another language fluently, please consider submitting a locale file. (I'd prefer it if folks used github and submitted it via a pull request, but I'm not picky on this one)

Info on Gmail Notifier Plus is here Gmail Notifier Plus Readme

Download: https://github.com/downloads/shellscape/Gmail-Notifier-Plus/Gmail-Notifier-Plus-3.0-beta1.zip

Please report any errors on the project on Github, along with error data. I won't triage issues on the forums here.

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. Report issues here: https://github.com/s...ier-Plus/issues

Cheers

Link to comment
https://www.neowin.net/forum/topic/1033601-gmail-notifier-plus-30-beta-1/
Share on other sites

Yeah it sounds like exactly the problem.

And no, you shouldn't ever need to delete any files in AppData from previous versions. Im not sure how the original author did every release, but personally, I hate having to reconfigure each new version :)

For anyone following the thread; looks like this is an issue isolated to 64bit Windows users. I'm trying to track it down and working with a guy through github that's helping. If we cant come up with a solution I'll either be recompiling as a 32bit assembly or putting in a stop-gap for the issue at hand.

I presume this is the error you're talking about? (I'm on Win 7 64bit)

2n19f00.jpg

[Window Title]

Gmail Notifier Plus Error

[Main Instruction]

An unhandled exception occurred:

[Content]

Error ID: 52b38cc1-3669-4352-9ed1-df257084eeab

Parameter is not valid.

[Expanded Information]

Server stack trace:

at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)

at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)

at Shellscape.Remoting.RemotingSingleton.Run(String[] arguments) in N:\Git\Gmail-Notifier-Plus\External\Shellscape.Common\Shellscape.Common\Remoting\JumplistRemotingSingleton.cs:line 32

at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)

at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:

at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

at Shellscape.Remoting.RemotingSingleton.Run(String[] arguments)

at Shellscape.Program.CallRunningInstance(String[] arguments) in N:\Git\Gmail-Notifier-Plus\External\Shellscape.Common\Shellscape.Common\Program.cs:line 105

[V] See details [OK]

[Footer]

Press CTL + C to copy this error to the clipboard.

@PsYcHoKiLLa yes, thats the error that users will see. If you'd like to help troubleshoot it, please shoot over to the github issues.

@aznkid - slowly. its not an error that is well documented, as its probably not something that folks have run into very often. the solution is to target x86 (32 bit) processors only, but I'd rather not go that route unless i absolutely have to.

@aznkid - slowly. its not an error that is well documented, as its probably not something that folks have run into very often. the solution is to target x86 (32 bit) processors only, but I'd rather not go that route unless i absolutely have to.

What do you mean by targeting 32-bit processors only? Have you decided to do this yet?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Because Chrome is doing it. And no one said anyone had to update immediately. That's silly. They could update every day for all I care as long as it's fast, and the next time the browser restarts, you're good. And the basic point is not to tee it up for bigger updates. As it is right now, all the windows I had open reopen anyway except inprivate.
    • Why? Does anybody actually want this? The constant need to close all browser sessions and wait for a new version to install, just so that there’s a integrated coupon manager feels like a waste of everyone’s time
    • I remember when Louis used to just do interesting Mac/iPhone repairs, now he's boring and just launches "crusades" every week
    • A shame it don't allow people to bypass the MS account, I will stick to using Rufus.
    • Microsoft about to radically change how often your Edge browser updates by Paul Hill Microsoft has just announced that starting with Edge 152, it will be moving to a two-week release cycle for faster, smaller updates. This faster release cadence will begin on August 27. This change comes just several months after Microsoft switched Visual Studio Code to weekly updates. The company said that the Extended Stable releases will remain on an eight-week cycle and that no admin changes are needed to experience the faster release cycle on the Stable channel. The new two-week release cycle will enable the faster delivery of security updates and platform improvements, all while reducing the size and complexity of individual updates. Microsoft claims that organizations will benefit from this change as it offers predictable validation cycles. For organizations that prefer a “more deliberate pace”, the Extended Stable channel remains an option. This change will affect Edge Stable releases on Windows, macOS, Linux, and mobile. The Extended Stable channel will continue to be updated every eight weeks, or every fourth Stable release, for example: versions 152, 156, 160, and 164. The Extended Stable could be a good option for organizations that don’t want the latest updates twice a month and don’t want as much hassle constantly updating browsers. In the case of Visual Studio Code, many of the updates being pushed by Microsoft are AI-related. As we all know, Microsoft Edge has a lot of AI features, so we could see Microsoft pushing more AI, thanks to the faster cycles. On the flip side, quicker releases could mean faster security updates, which is beneficial in a world where AI systems are hunting for software exploits. What do you think? Let us know in the comments. For more updates on Edge, be sure to follow Neowin's coverage. In May alone, we reported on Edge offering in-browser pop-ups to assist users with website compatibility issues, that Edge was losing Copilot Mode, and that Microsoft had fixed a plain-text password bug in Edge. Source: Microsoft 365 Admin Center
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      514
    2. 2
      PsYcHoKiLLa
      185
    3. 3
      +Edouard
      159
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!