Re: [Flightgear-devel] AI Jetways broken in 2016.3.1

[James T. <zak...@ma...>]

> On 14 Nov 2016, at 18:44, m.h...@gm... wrote:
> 
> Am 29.09.2016 um 05:18 schrieb James Turner:
>> For the first fix, I read the Nasal file and I’m not sure ‘exports’ is the correct place. 
>> But I also don’t really know the code well, so I would prefer either some explanation of what is truly needed -
> 
> any folder where the nasal script is allowed to write to.
> 
>> can we just disable the writing to disk completely?
> 
> no.
> 
> This is an easy to fix bug and it would be sad, if it stays unfixed in
> the upcoming release.
> 

Hmm, this is not really good. There is no reason for something like jetways to modify anything on this disk. It would be much better to understand the fundamental issue and re-design the system to avoid needing disk-acess, then to simply hack the current code to write to a different location. If I’m misunderstanding and there really is some intrinsic reason why animating a jetway needs to modify files, I would like a clear description of why.

If having them broken in the next release motivates someone to step up and properly fix the system to avoid the disk output entirely, I’d consider that a net win, especially compared to patching the current setup and this bad behaviour remaining until the next time we change Nasal IO setup.

Kind regards,
James