Recommended Posts

  • 2 weeks later...

Looks like beta 2 is fairly solid. Only 2 real issues to fix and about 150 people using it (or have downloaded it). Nothing compared to the 5k downloads the last 2.x version had, but I'll take it.

I'm going to be fixing the two remaining issues and enabling the auto check for new versions and then I'll release 3.0.

i keep getting an error when i go to preferences to set my mail settings

[Window Title]
Gmail Notifier Plus Error

[Main Instruction]
An unhandled exception occurred:

[Content]
Error ID: d4afc596-1301-4f5a-9ad5-85b6ca7f89a7

Object reference not set to an instance of an object.

[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

AdverseDeviant, re-read the OP and try not to miss the HUGE EFFING MESSAGE regarding bug reporting this time. Boggles the mind how anyone could miss that.

Update on development - Managed to knock out most of the issues reported on github, but the tabstop issue with textboxes, etc. is really something. I'm fairly certain that my complex use of Panels has exposed a bug in the framework, so I'm prepping a bug report for Microsoft. That's really the only issue holding up another release. Once I can find a way around that, I'll post another build.

Found a workaround for the tabs. Forgot to mention that I was going to enable auto-version-checks. That's last on the list before a new beta for testing, and then depending on the bugs reporting I figure a week or two to a full release.

Found a workaround for the tabs. Forgot to mention that I was going to enable auto-version-checks. That's last on the list before a new beta for testing, and then depending on the bugs reporting I figure a week or two to a full release.

So could we see a new beta by the end of the week?

I cant edit the original post, and neowin hasn't given me an answer about it.

You can always find the downloads here: https://github.com/shellscape/Gmail-Notifier-Plus/downloads

(always be willing to do some digging on your own, you could have found that pretty easily)

Just wanted to update everyone who is patiently waiting - with the holidays creeping up, time got a little short. I'm taking vacation the last week of the year, so I'll have pooptons of time to get 3.0 wrapped up.

I'm also going to work on a GCal Notifier variant (because I desperately need a good one at home) during that time, and will hopefully have something in beta for that too.

I've been reading some on how Chrome does the seamless updates in the background and where it puts it's EXE files. It dumps everything into the User directory and gets around all kinds of permissions problems that way. I'm probably going to go that route as well here in the near future and put together an installer which puts files in Users\[user]\Local\Gmail Notifier Plus. Anyhow, just thinking out loud.

  • 2 weeks later...
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

    • 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
    • One Year In
      slackerzz earned a badge
      One Year In
  • 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!