06-26-2018, 10:34 PM
Hi there and sorry for jumping on an old thread...
I've run into the same question and was wondering if there is any more direct information than to read through the code (in a language I'm not familiar with).
Just to give a reason for why this is of interest, what I would like to do is to use the Wings3D application as an external CAD program so that my application can write the data it currently has to a .wing file in a temporary location, open the file using its default application (Wings3D hopefully) and then -once the user clicks save (rather than save-as for which I don't know what file name/location they may enter), have the calling application re-read the updated file back in (keeping an eye on when the file becomes updated or the newly created process being closed). There might be a way to do this by modifying the code - but that would mean I would need to support a separate fork, not at all what I want to get into.
So... has anyone got some ideas on how I should approach this? I'm using .NET so some of the compression/decompression should already be provided (assuming I'm correctly understanding this that the wings format is a compressed file with a header slapped onto the beginning {why?})
Thanks in advance for any feedback.
B
I've run into the same question and was wondering if there is any more direct information than to read through the code (in a language I'm not familiar with).
Just to give a reason for why this is of interest, what I would like to do is to use the Wings3D application as an external CAD program so that my application can write the data it currently has to a .wing file in a temporary location, open the file using its default application (Wings3D hopefully) and then -once the user clicks save (rather than save-as for which I don't know what file name/location they may enter), have the calling application re-read the updated file back in (keeping an eye on when the file becomes updated or the newly created process being closed). There might be a way to do this by modifying the code - but that would mean I would need to support a separate fork, not at all what I want to get into.
So... has anyone got some ideas on how I should approach this? I'm using .NET so some of the compression/decompression should already be provided (assuming I'm correctly understanding this that the wings format is a compressed file with a header slapped onto the beginning {why?})
Thanks in advance for any feedback.
B