> What do you think of the CopySourceAction I've added (see [1])? Doing 
> the equivalent of your saveToFile.flow should be pretty trivial, no?

It's not a bad idea, except that I still will need to use flowscript to fire 
off a .vbs script that prints the document....or need to write a custom 
action to do that, which I would rather not do at the moment, deadlines 
looming and all that.

> Congrats for your project. But I really think this unspecified behaviour
> you're using is not the good way to go. So let's keep it as is in the upcoming
> 2.1.3 and forbid it in 2.1.4.

Why forbid it?  I see no reason to elminate such a useful feature, 
unspecified or otherwise.

Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com

Reply via email to