That works very nicely.... When run locally, it also fills up the screen and makes it readable from across the room. I notice that it skips a stop at a second once in awhile and the next ring will come an equal amount of time later than expected at the following ring. Just curiosity in asking but is this some sort of correction that it's doing?
That works very nicely.... When run locally, it also fills up the screen and makes it readable from across the room. I notice that it skips a stop at a second once in awhile and the next ring will come an equal amount of time later than expected at the following ring. Just curiosity in asking but is this some sort of correction that it's doing?
Yes I just noticed that is happening. Problem is that when it self corrects the time, it will adjust a second or two but you never know when its going to happen and throws out the interval time.
It should have been a simple task but flash is not good at this because its intenal timer speeds up and slows down depending on cpu usage. So you have to repeatedly request the system time which I've done but that makes timing other events tricky as you never know where flash is in its cycle.
There must be an easier way...
Rob -
THat's nice, can you add in steps for the rest of the process, i.e. stop, fix, wash, presoak. Perhaps check boxes to include/not include a particular step, like you want a presoak you check it to include it or not check it to not have a presoak.
ALso, large digital readout for across the room. Or check box for digital/analog.
Rob -
THat's nice, can you add in steps for the rest of the process, i.e. stop, fix, wash, presoak. Perhaps check boxes to include/not include a particular step, like you want a presoak you check it to include it or not check it to not have a presoak.
ALso, large digital readout for across the room. Or check box for digital/analog.
There's always one. You can start as many instances of it running as you want. So just start one or more and use each instance for each step of the process. None of the input fields are required so you can just use it as a straight timer with no end time or as a timer with an end time or an interval timer with no end time etc. Play with it and I think it will do most of what you need.
I'm not running an on demand free programming service. If you want to pay me for carrying out your requests I'm happy to do it. If you don't want to pay, then you get what you pay for...
And besides, developing is not difficult to do if you have a watch with a stop watch built in and a second hand on it. A typical chrongraph watch is all you need and most people don't spend their time at a PC whilst developing. i.e. It's of no real use to me so I'm not going to spend a lot of time on it.
I made a darkroom timer for E-6 in .NET, it's targeted to the Windows Mobile Smartphones but I could re-target as a Windows Application if anyone is interested. Other processes can be defined via an XML file. There is no visual indicator for agitation though.
I made such good use today of the timer you set up that I thought I'd drop a thank you...(You're not set up for private messages so I'm adding it here). I'm editing a magazine for my company and developing a back log of film at the same time today. I was using an awkward sequence that would have required a lot of concentration but the timer made it a no-brainer. It is perfect for my duties and I just wanted to thank you again for taking the time to code it up. A friend is also using it in the same way and appreciates it very much, too.
I have a pretty beat Omega CT40 programmable darkroom timer you can set up with end of time warning, 1 second metronome, 30 second metronome and 15 second warning, complete with instruction manual I'll sell you for $25.00