Scripts and File Paths

[gmint]

I've recently been getting into the Scripts section of QLC+ lately which really opens up a ton of possibilities. That said I'm having a minor issue and I wonder if anyone might have a workaround. Here's the scenario:

I'm using a script (on startup of QLC+) to open MIDI Patchbay which I use with my Native Instruments Maschine controller. Obviously, it's not hard to manually launch the program, but I figured, hey if I can have QLC+ do it automatically, why not do it. Just one less thing to do before a show. And I can get this to work just fine. However, I don't always run QLC+ on the same machine and I'd like to have it open the MIDI Patchbay file from a dropbox location which is relative to the users folder on a given machine. Doing this at the command line, both of the following scenarios work

Scenario A) /usr/bin/open /Users/myusername/Dropbox/blah.file
Scenario B) path: /usr/bin/open ~/Dropbox/blah.file

However, when doing this with a systemcommand:/ in QLC+ the Scenario A works but Scenario B does not.

Anyone have any ideas why this might be and if there's a workaround?

Like I said, this is hardly a big issue. Just something I was playing around with and got me curious.

[plugz]

QLC+ does not act like a shell, it will not expand ~ or $HOME to /home/username.

Demonstration: in your shell, type

Code: Select all

/usr/bin/open '~/Dropbox/blablabla...'

(with the quotes)

You shell will not expand the ~, and the command won't work.

[gmint]

QLC+ does not act like a shell, it will not expand ~ or $HOME to /home/username.

Demonstration: in your shell, type

Code: Select all

/usr/bin/open '~/Dropbox/blablabla...'

(with the quotes)

You shell will not expand the ~, and the command won't work.

Yes, I understand that, hence the point of my post.

Try something like /bin/sh -c /usr/bin/open ~/Dropbox/blah.file

I gave that a shot but no luck...

[janosvitok]

Try something like /bin/sh -c /usr/bin/open ~/Dropbox/blah.file