Specify output directory for fuze.py

[GoogleCodeExporter]

What steps will reproduce the problem?
n/a

What is the expected output? What do you see instead?
Always outputs to source directory

What version of the product are you using? On what operating system?
r63

Please provide any additional information below.
Maybe specify the output directory as the last command line argument?

Original issue reported on code.google.com by hansonor...@verizon.net on 27 Apr 2010 at 11:04

[GoogleCodeExporter]

Ouch. I recently updated pyrc4 and it might the the culprit of this weird thing 
(the
problem is located in Ui_Mainwindow.py from revision 61 and later, which 
contains
only gui things should not mess up with application logic...)

Original comment by ssorga...@gmail.com on 28 Apr 2010 at 7:35

• Changed state: Started
• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Hopefully fixed now

Original comment by ssorga...@gmail.com on 28 Apr 2010 at 9:09

• Changed state: Fixed

[GoogleCodeExporter]

I'm not sure I explained myself well enough...

I'd like a way where I can call fuze.py directly from the commandline and 
specify a
destination directory for the completed file.  As it stands now, the completed 
file
is placed in the same path as the original file.

Right now,
fuze.py /my_dir/videos/some_file.mpg
results in:
/my_dir/videos/some_file.avi

What I'd like to do is:
fuze.py /my_dir/videos/some_file.mpg -o /my_dir/transfer2fuze/

would result in /my_dir/transfer2fuze/some_file_fuze.avi

Original comment by hansonor...@verizon.net on 28 Apr 2010 at 10:03

[GoogleCodeExporter]

Ok. Mmm it shouldn't be very hard to implement.

BTW, 0.5.1 is coming soon :)

Original comment by ssorga...@gmail.com on 28 Apr 2010 at 10:42

• Changed state: Accepted
• Added labels: Priority-Medium, Type-Enhancement
• Removed labels: Priority-Critical, Type-Defect

[GoogleCodeExporter]

Original comment by ssorga...@gmail.com on 30 Apr 2010 at 3:00

• Changed state: Fixed