Lets just all agree that all things considered, putting the hallides on a short brust feed timer array like a feed timer setting is probalbly like wearing your shoes on the wrong feet because "it can be done".
FOR hallides I give the Idea a 9.5 for enginuity and creativity. For application.... well it late and I'm kinda cranky. Halides preform best if turned on, left on and turned off. we'llall agree on that part.
If I were running t-5's or compacts... which I may add supplemental eventually, this may be an option. In that case... it has an "application" rating much higher. After some further thought and research back to my email to you about this last time, I think I mentioned that I thought it could be done with a single addition of a single status setting in to programming... at a "Bump" feature to the Man On, Man Off, Auto... settings. If sellected, it puts the device in the opposite state it is in at the time... Ie: off to on... untill on changes automatically to off again.
I realize it sounds simpler that it is in real life. but it would be handy.
The more I think about it, it would really be nice to have a device or set of optional defices to apply to a lunar calander. I have a graphic that i started that I'll have to post that would explain this better...
Just not right now... It's later here than it is by you Curt - and the digits that drive these keys are getting tired.
I'll email it to you tomorrow when I change computers.
BTW, can I make changes to my database file to get rid of the columns or re-organize the columns to display my commonly used parameters first in notes... Like Calcium, Alkalinity, Temp, pH... then the ones I don't track... I would actually use User1 and user2 since I track Specific addatives in those.. and would like them over next to Cal and Alk. Yes, I know I can arrance them this way in notes already, but if I refresh, they get put back to defaults.
Jason
BTW... you were in time there... I din't take it apart...
