NewCommandTimeout ignored when autoLaunch=False

Hi all,

I am running Appium 1.3.6 and noticed that capability NewCommandTimeout is ignored when autoLaunch is set to False (thus Appium will use the default timeout or the one set at startup with --command-timeout).

Is there a particular reason for this?