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

    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
    • OpenAI is making Codex more useful in Chrome and the cloud by Pradeep Viswanathan OpenAI's Codex now has more than 5 million users, up nearly 4x from earlier this year. To further accelerate Codex's growth among developers, OpenAI today announced that it has agreed to acquire Ona, a company that builds secure cloud execution and orchestration technology for developers. Ona will enable developers to run Codex with persistent and controlled cloud infrastructure for long-running agentic workflows. Right now, most Codex execution happens locally on developers' laptops and PCs, and the agents work continuously for hours. Through Ona, OpenAI aims to make Codex agents keep working for days without being tied to a user’s local machine or an active session. This will be an important capability for enterprises that want to deploy AI agents in production while maintaining control over infrastructure, data, security boundaries, credential scope, logging, and review workflows. Like any acquisition, the deal is still subject to customary closing conditions, including regulatory approvals. Until the deal closes, OpenAI and Ona will continue to operate as separate companies. After closing, Ona’s team will join the Codex team to improve developer workflows. Alongside the Ona acquisition announcement, OpenAI today introduced a few Codex updates. Developers can now save Codex rate limit resets and use them later instead of losing them when they are not needed immediately. OpenAI is also adding a referral option where users can invite a friend to Codex and get a saved rate limit reset. OpenAI today also announced a developer mode for browser use in Chrome and the Codex in-app browser. With this mode, Codex can use the Chrome DevTools Protocol to debug web apps, inspect pages, and work more directly with browser-based development workflows. Developers can use this when they want Codex to profile JavaScript, inspect console output and network traffic, examine web page states including the DOM and applied styles, and more.
  • 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
      509
    2. 2
      PsYcHoKiLLa
      186
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!