Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show the time interval in addition to the absolute time in the bottom left-hand corner text #25

Open
carlcotner opened this issue Jun 2, 2018 · 2 comments

Comments

@carlcotner
Copy link

When selecting and entering "in 150 minutes", for example, the bottom left-hand corner text shows what the time will be in 150 minutes, which might be (for example)

Alarm will be set for 1:00:00 AM tomorrow,
Saturday, June 2, 2018.

This is, obviously, very useful.

When selecting and entering "at 1:00 AM June 2, 2018" (for example), the bottom left-hand corner text does not indicate that the time interval will be 150 minutes. At least for me it would be helpful if it included the time interval so I could double check whether the alarm was set correctly.

@nriley
Copy link
Owner

nriley commented Jun 2, 2018

I agree and this feature already exists, but it is broken on the current macOS.

image

The way this is intended to work for "at" alarms is that you'll get a confirmation of the time until your alarm which will pop up if you have Growl installed; if it doesn't look right, you can at least delete/re-set the alarm. If this is the next alarm, of course you can also look at the time displayed over the Dock icon to make sure it makes sense, too.

Unfortunately the old Growl framework I'm using broke at some point and I didn't notice that these confirmations stopped popping up. (I barely use Pester any more — I don't have a Mac at work and am mostly on iOS at home these days.)

So a solution, if you want the above, is to install Growl and use Growl Version Detective to upgrade the Growl framework in Pester to the current version.

The real solution is that Pester should upgrade to a current Growl framework. The reason I didn't do so earlier is that the newer SDK was causing crashes, but I think these are fixed now.

@carlcotner
Copy link
Author

carlcotner commented Jun 5, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants