getAvailable() assignment. about duetimer

[ivanseidel]

Hi Bill,

I'm glad you liked it. getAvailable method is pretty dumb actually... but,
you can fell free to change it! It would be really good to have it
improved. If it works well we can update the repository!

Can you try to fix/improve it?

Ivan
Em 27/06/2014 13:32, "SwarfEye" [email protected] escreveu:

Hi,

I've been using your library a lot! Thanks so much.

I have recently encountered an issue with the library.

I have a project that involves a bunch of different objects and libraries.
Several of the different objects need to make use of timers. I need to be
able to get a timer, name it, and hold on to it for a period of time, and I
need to have a number of different objects do so that they all have access
to their assigned timer.

Currently, the getAvailable() function will keep returning the same timer
until that timer is started, so it is not possible to reserve a timer for
use later. Also, if you run out of timers, then getAvailable() doesn't
notify you of the error... it just returns timer0... which is a possible
source of big trouble if timer0 is already in use.

My current solution is simply to hard-code timer numbers into each
instance... but it would be much nicer to be able to pickup a timer when
needed/as needed and then release them again without having to assign
specific timers to each object.

Thanks,

Bill

—
Reply to this email directly or view it on GitHub
#28.

[SwarfEye]

Thanks again for making this library available.

I'll let you know if I implement a fix here. At this point I think I'll be
able to hack around the limitations, and so I likely will... but maybe it
won't work for some reason and then I'll have to dig in.

Thanks again.

Bill

On Fri, Jun 27, 2014 at 4:55 PM, Ivan Seidel [email protected]
wrote:

Hi Bill,

I'm glad you liked it. getAvailable method is pretty dumb actually... but,
you can fell free to change it! It would be really good to have it
improved. If it works well we can update the repository!

Can you try to fix/improve it?

Ivan
Em 27/06/2014 13:32, "SwarfEye" [email protected] escreveu:

Hi,

I've been using your library a lot! Thanks so much.

I have recently encountered an issue with the library.

I have a project that involves a bunch of different objects and
libraries.
Several of the different objects need to make use of timers. I need to
be
able to get a timer, name it, and hold on to it for a period of time,
and I
need to have a number of different objects do so that they all have
access
to their assigned timer.

Currently, the getAvailable() function will keep returning the same
timer
until that timer is started, so it is not possible to reserve a timer
for
use later. Also, if you run out of timers, then getAvailable() doesn't
notify you of the error... it just returns timer0... which is a possible
source of big trouble if timer0 is already in use.

My current solution is simply to hard-code timer numbers into each
instance... but it would be much nicer to be able to pickup a timer when
needed/as needed and then release them again without having to assign
specific timers to each object.

Thanks,

Bill

—
Reply to this email directly or view it on GitHub
#28.

—
Reply to this email directly or view it on GitHub
#28 (comment).

Bill Gray
Velkess
415 407 7356