Auto-Alert Usage Fails
Reported by Patrick Quinn-Graham | January 28th, 2009 @ 07:03 PM | in v1.3.1
If i have "warn me when total usage exceeds x mb" is enabled, it will automatically pop up with a warning instantly, and repeatedly. I'll attach a screenshot below. the error pops up regardless of what you set the value to. Only way to stop it is to uncheck this option.
-
Screenshot__199.jpg
138.7 KB
Screenshot__199.jpg
Comments and changes to this ticket
-
Patrick Quinn-Graham March 4th, 2009 @ 05:51 PM
- State changed from “new” to “open”
- Milestone set to “v1.3.1”
-
-
-
Dan Milne March 5th, 2009 @ 10:47 PM
This version doesn't seem to spawn windows, but none of the menu items are enabled. It's not possible to quit the app, connect or disconnect the modem.
-
-
Patrick Quinn-Graham March 24th, 2011 @ 01:54 PM
- State changed from “open” to “resolved”
- Milestone order changed from “0” to “0”
This section has been rewritten in 1.4, so should fix whatever issue that might have caused that.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
This little mac app provides you with signal strength, network mode (GRPS/WCDMA/HSDPA), network name control over your connection, and statistics about your current connection (current throughput, total data transferred, connection time). It does this through a little icon in your menu bar (and a bigger window, if you want to see it), and also helps you keep track of your usage - no need for a nasty surprise from your provider.
People watching this ticket
Patrick Quinn-Graham
Attachments
-
Screenshot__199.jpg
138.7 KB
Tags
Referenced by
-
3
Cheetah watch spawns heaps of windows
Closing as this does indeed seem to be a duplicate of #1.
-
4
multiple windows
This is a duplicate of
bug #1, please follow that bug fo...