At 5:46 PM -0800 1/14/06, Buzz Kettles wrote:
At 10:36 AM -0500 1/13/06, you wrote:
At 6:30 PM -0500 1/12/06, Cole Tierney wrote:
At 2:35 PM -0800 1/12/06, Buzz Kettles wrote:
or if the #dialog is really the issue why not make it invisible,
change it's type & then forget it?
I didn't think o
At 10:36 AM -0500 1/13/06, you wrote:
At 6:30 PM -0500 1/12/06, Cole Tierney wrote:
At 2:35 PM -0800 1/12/06, Buzz Kettles wrote:
or if the #dialog is really the issue why not make it invisible,
change it's type & then forget it?
I didn't think of changing the type on the fly. I'll give that
At 7:09 PM +0100 1/14/06, you wrote:
although the topic is a bit old, i'd like to add the following command;
for a project that involves many cpu-intensive tasks, mainly in
graphics manipulation/-analysing, after alot of testing i finally
ended-up splitting-up different tasks between two seper
although the topic is a bit old, i'd like to add the following command;
for a project that involves many cpu-intensive tasks, mainly in
graphics manipulation/-analysing, after alot of testing i finally
ended-up splitting-up different tasks between two seperate projectors
that communicate wi
