Nando, you could always store and manipulate the frustrationLevel using bitwise logic, and then you could store frustration states for many different things in a single variable!
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Nando > Sent: Wednesday, December 17, 2003 1:46 PM > To: [EMAIL PROTECTED] > Subject: RE: [CFCDev] "Variables" scope....tearing out hair > > > Darcey, > > In addition to what others are suggesting here, to call that > example method first, I > *think* what you might need to add to this component are > opposing "increaseFrustrationLevel" and > "decreaseFrustrationLevel" methods that set a boolean, > "ripItOut" in the variables scope. > > Then you need another method that checks the frustrationLevel > expressed in the variables.ripItOut boolean and acts > accordingly. If you want to get sophisticated about it, you > can provide more levels that a simple boolean will handle and > get numeric about it, but for me, a boolean is almost always enough. > > I have a tendency to run my hands through my hair when i get > frustrated, and you can really see what type of a day i've > had from the amount left on my desk. :-) > ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
