-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2014-09-24 10:14, Nicolas Montgermont wrote:
Hello
Le 24/09/2014 09:05, IOhannes m zmölnig a écrit :
The use-case for this is things like:
I see some other points:
- the output from [keyname], [key], [gemkeyboard], [gemkeyname] is
different * the window in Gem has to be placed (offset) in a different way for OSX for fullscreen * for some specific IP hardware (badly coded), the bit order is different when communicating with TCP/UDP.
so these are mainly bugs in specifc objects we want to work around with such a feature? .
- the [shell] and [popen] object that are a very good connection to
all the other software behave differently * one might want to call different script on different os as well for specific usage
though the script itself already has the possibility to check which OS it's running on, and cold adjust it's behaviour (e.g. by forwarding the request to an OS-specific sub-script)...though probably not easy to run a .bat from a .sh and vice-versa
- the path management can be different (old pix_write object for
example still in last pd-extended)
but if somebody chose to install a newer version of [pix_write] on their outdated Pd-extended, you will still use it the wrong way. in this case you might want to ask the version of [pix_write] instead.
fgamsdr IOhannes