| View previous topic :: View next topic |
| Author |
Message |
leosdad
Joined: 21 Jun 2011
Posts: 5
|
 Posted: Fri Jun 24, 2011 9:38 pm Post subject: CountUsageOncePerDay and clock winding |
 |
|
I'm considering using CountUsageOncePerDay along with UsageCount, which seems fair to the user. But I still want to monitor against clock winding. I believe that checking some values would help, but I'm not quite sure:
| Code: | evalMonitor.FirstUseDate > today
evalMonitor.DaysInUse < evalMonitor.UsageCount
etc.
|
Is there a sure-fire checking method?
(Incidentally, I believe that it would be possible to do a much more robust checking against clock winding and other time tricks, like keeping the application open, by monitoring usage dates more closely. This would be a very welcome addition to ILS) |
|
| Back to top |
|
 |
Infralution
Joined: 28 Feb 2005
Posts: 5027
|
| Posted: Sun Jun 26, 2011 10:40 pm Post subject: |
|
|
The EvaluationMonitor already includes clock winding detection logic. If clock winding is detected then the Invalid property is set to true.
_________________
Infralution Support |
|
| Back to top |
|
|
leosdad
Joined: 21 Jun 2011
Posts: 5
|
| Posted: Mon Jun 27, 2011 2:34 pm Post subject: |
|
|
| Here you say that UsageCount is unaffected by clock winding, that's why I wasn't using it. However I tested its value and I see that Invalid is True if I set the clock back and False when the clock is set forward again. |
|
| Back to top |
|
|
Infralution
Joined: 28 Feb 2005
Posts: 5027
|
| Posted: Mon Jun 27, 2011 10:18 pm Post subject: |
|
|
I meant that the UsageCount property is unaffected by clock winding - and the EvaluationDialog by default checks the Invalid flag so that he didn't need to check it separately in this case.
_________________
Infralution Support |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
