Adium

Ticket #9757 (new defect)

Opened 22 months ago

Last modified 16 months ago

User Permitted To Enter Negative Time To Idle

Reported by: JeremyBanks Owned by: nobody
Milestone: Adium bugs Component: Adium UI
Version: 1.3svn Severity: minor
Keywords: negative idle time input Cc:
Patch Status:

Description

Hi. Pretty minor thing here. I'm not sure it even counts as a bug but I figured I'd submit it because it couldn't hurt.

OS X Version: 10.5.2 build 9C7010
Adium Version: Latest trunk (r23246) and latest stable (1.2.5).

The user is permitted to input a negative value for their time to idle, and it will be saved correctly, rather than reset to 0 as non-numeric values are. It's treated as expected, as a zero value would be.

Attachments

-42idle.png (9.3 KB) - added by JeremyBanks 22 months ago.
Setting a time-to-idle of -42 seconds.

Change History

Changed 22 months ago by JeremyBanks

Setting a time-to-idle of -42 seconds.

Changed 22 months ago by jas8522

  • priority changed from normal to lowest
  • severity changed from normal to trivial
  • milestone set to Adium X 1.3.x

Changed 22 months ago by zacw

The NSStepper needs a -setMinValue on it.

Changed 21 months ago by djmori

Changed 20 months ago by jeremyw.sherman

It is also possible to type in negative and non-integral values for the other NSTextField in that pane (After N minutes of inactivity, set...). However, pressing any of the stepper buttons acts as if you had entered 0, going either to 999 (down button) or 1 (up button). Interface Builder reports that both AISmartSteppers have minimum values of 0 set in their attributes, and indeed, you cannot set a negative value using the steppers.

The similar NSTextField + (presumably) AISmartStepper in the General Preferences pane is not affected by this defect (instead, it catches negative values and throws up a sheet reporting that the value "Fell short of minimum"; it is possible to use the stepper to set a value that garners a similar error because the value is now greater than the (unspecified) maximum). I was not able to examine this in Interface Builder for comparison, since attempts to open any variety of GeneralPreferences.nib yielded a series of errors from IB: The document "General Preferences.nib" could not be opened, followed by Open: While opening "GeneralPreferences.nib", the following error occurred: *** -[NSKeyedUnarchiver decodeObjectForKey:]: cannot decode object of class (SRRecorderControl), followed by the same error reported again.

If I could examine the similar case in the General Preferences pane, I imagine I could fix up the Status Preferences pane, as well as the odd behavior of the similar widget in the General Preferences.

Recommend title change to "User-supplied numbers not validated in preferences". Now that I thought to check it, the textfield for port number under options when editing an account also performs no validation; it's got no problem if you want to try to use port -80.5.

Changed 20 months ago by zacw

In order to edit the general preferences you need the shortcut recorder plugin, which is attached to wiki:Localization

Changed 16 months ago by jas8522

  • milestone changed from Adium 1.3.x to Adium bugs
Note: See TracTickets for help on using tickets.