Omnimaga
General Discussion => Technology and Development => Computer Projects and Ideas => Topic started by: Darl181 on November 29, 2010, 01:10:16 am
-
I've had this random idea for the past few days: a simple sig widget thing.
The idea I have in mind is kind of like one of those web counters, but each day it increases by one. And the person who's using it can reset the value.
So it would be like "2 days without a RAM clear" or something like that.
Any ideas of how/where to do this?
That or, any takers?
-
Hm, good idea, but I doubt it exists... I could work on it.
-
the clock counts that already....
current day in january is amount of days since last ram clear :)
-
I've had this random idea for the past few days: a simple sig widget thing.
The idea I have in mind is kind of like one of those web counters, but each day it increases by one. And the person who's using it can reset the value.
So it would be like "2 days without a RAM clear" or something like that.
Any ideas of how/where to do this?
That or, any takers?
That would be a good idea, but...
the clock counts that already....
current day in january is amount of days since last ram clear :)
This already counts the days since last RAM Clear, or since you bought calculator (if no RAM Clears, wow, that's impossible!)
-
But I always set my clock after a RAM clear D:
-
But I always set my clock after a RAM clear D:
What is the point of having the clock set? I see no advantage, is it because of TimeTools?
-
No, it's just because I prefer to have the clock set.
-
No, it's just because I prefer to have the clock set.
But I never find it useful, but that's just my opinion. Maybe you're very organised, though.
-
I have 1 time set my clock, when I bought it. (I had not heard of ram clears, wow) :)
-
That's a cool idea but I know I wouldn't be able you use it. I typically ram clear on purpose if something seems funky or if I am too lazy to clear the stat editor. Which means I will clear my ram almost every single day at school.
-
...or if I am too lazy to clear the stat editor.
lol :P
Sounds good to me. ;D
I think this is possible:
Hook into the time change code
Make it so that every time the time is changed, this new offset (from what it was) is stored somewhere
When "widget" is run, subtract that data from the current time
-
No, it's just because I prefer to have the clock set.
But I never find it useful, but that's just my opinion. Maybe you're very organised, though.
I never bother either, because it gets reset on resets. Bad design on TI part. I hope that if KnightOS supports the clock on 84+ calcs that it will not reset settings when the calc crashes.
The widget thing seems like a fun idea. It would be better than those Internetometer stuff because it would be calc-related and maybe encourage people to backup or something. :P
Just make sure it's on a stable and fast server.
-
No, it's just because I prefer to have the clock set.
But I never find it useful, but that's just my opinion. Maybe you're very organised, though.
I never bother either, because it gets reset on resets. Bad design on TI part. I hope that if KnightOS supports the clock on 84+ calcs that it will not reset settings when the calc crashes.
The widget thing seems like a fun idea. It would be better than those Internetometer stuff because it would be calc-related and maybe encourage people to backup or something. :P
Just make sure it's on a stable and fast server.
I don't think the clock is intentionally erased. It's probably one of those things that can't help but being erased. I don't fully know, though. But yeah, it would be nice for KOS to keep the time.
-
Maybe. Now that I think about it, though, wouldn't storing the clock in archive requires the flash to be written to every second? That wouldn't be good.
I'll have to post about the clock in KOS topic later. Maybe not the entire RAM gets erased when rebooting?
-
It is impossible to stop the clock from getting killed. I made a patch for 2.43 that killed the OS code that reset the clock. But the problem was that now instead of being reset, it was completely reset, (it showed 1997 and didn't run.) Which means that the hardware actually kills the clock. So any time the hardware says "ram clear!" the clock will be reset.
-
I was actually thinking of something computer-based...the person could click a link or the picture or something and the number resets.
Something like it on the calc would be pretty awesome, though ;D
-
I think I should say something to the effect of "What kind of developer are you whose RAM hasn't been cleared in any given 2-day period?" ;D
And yes, the clock on my TI-84+SE is essentially a counter :D
-
The computer-based one could be a matter of pride, maybe.
"Hey, I code with dangerous languages such as Asm or Axe, but I'm so clever and careful at programming that I've avoided RAM clears for X amount of days! Beat that!"
Or, perhaps
"Hey, I'm so awesome - I code with dangerous languages such as Asm or Axe, and I can prove it! Look at how many RAM clears I get!"
-
Yeah, the only time I bother to set the clock now is when I use MSD8x, so the times are realistic :P
-
It is impossible to stop the clock from getting killed. I made a patch for 2.43 that killed the OS code that reset the clock. But the problem was that now instead of being reset, it was completely reset, (it showed 1997 and didn't run.) Which means that the hardware actually kills the clock. So any time the hardware says "ram clear!" the clock will be reset.
I see, that sucks then. X.x
As for the widget thing, would it count how many RAM clear you got since a date? My worry, though, is that some people might just fake the number to pretend they had 31337 RAM clears. >.>
-
As for the widget thing, would it count how many RAM clear you got since a date? My worry, though, is that some people might just fake the number to pretend they had 31337 RAM clears. >.>
I was more thinking of an on-computer, forum thing, where the person can reset the number of days to zero if they get a RAM clear that day.
-
KOS only keeps the time on 15 MHz models. The current methods for tracking time on a lower model are just not good enough to be accurate.
-
It does on the 83+SE too? Because that calc had no clock function. It had crystal timers, though.
As for the widget thing, would it count how many RAM clear you got since a date? My worry, though, is that some people might just fake the number to pretend they had 31337 RAM clears. >.>
I was more thinking of an on-computer, forum thing, where the person can reset the number of days to zero if they get a RAM clear that day.
Yeah that's what I meant. I know some people would just fake it, though. :P
Plus for some people, it would be best to just do a still image that always shows 1 second since last RAM clear, since they get RAM clears this often. ;D
-
It does on the 83+SE too? Because that calc had no clock function. It had crystal timers, though.
The 83+SE has all of the hardware needed - it's just the OS that doesn't support it, if I recall correctly.
-
I think the 84+ had an additional hardware for the clock, because if I remember, crystal timers ran a bit slower when batteries were low. I could be wrong, though.
-
Maybe it does, I'm not too sure. I don't like messing around with hardware :P
-
I've gone a whole month without RAM clears ;D
The fact that I've only used Axe twice in that interval has nothing to do with it...
-
The 83+SE does have crystal timers that run at a base frequency of 32768Hz, and can be used to keep time. But, you can't keep updating a clock while the calculator is off. On the other hand, the TI-84+ series has a Real-Time Clock in addition that increases automatically every second. This and USB are the only hardware differences between TI-83+SE and TI-84+ series (other than little things like ways to detect calc models and the extra boot page on the 84+ that handles USB)
-
Right, that's what I guessed, thanks for clarifying :)
-
RAM clear :-\
-
My friend actually had me tell him every time my RAM cleared over the course of a week as a little study. When it was done, he gave me the statistics (these are the best I can remember):
-Average: 9 per day
-Highest Day: Saturday (13)
-Lowest Day: Monday (6)
-Average Time of Clear: 9:30AM-11:00AM (Math class ;))
Interesting note: 12:00AM-12:30AM averaged 2 per day
-
Does he code or play some unstable games like Mario? 9 per day seems like a bit much otherwise! O.O
-
Does he code or play some unstable games like Mario? 9 per day seems like a bit much otherwise! O.O
DJ, it's how many times SirCmpwn's RAM cleared. ;)
His friend was keeping track for him.
-
Oh ok, I misunderstood. :P