Re: [Maya2osg-users] Discussion of next changes

[Peter W. <pp...@cg...>]

Hi J-S
> Second, I am getting an error when I click Export and the pre-export
> script field contains the default thing you put there (print( "preExp
> $path$file.$type " ) ;)  First of all there seemed to be a newline
> character in there at the end, because it would say:
>
> print( "preExp
> C:/Users/jeang/Documents/maya/projects/default/scenesbox_normalmap_maya2osg.osg
>
> " ) ;
> // Error:  //
> // Error: Unterminated string. //
>
> So just before the closing quote there seems to be a newline. Then when
> I removed the newline, I got this:
>
> print( "preExp
> C:/Users/jeang/Documents/maya/projects/default/scenesbox_normalmap_maya2osg.osg"
> ) ;
> preExp
> C:/Users/jeang/Documents/maya/projects/default/scenesbox_normalmap_maya2osg.osg
> // Error: Too many arguments.  Expected 0, found 1. //

Yes, I noticed something like this error message as well, but the 
problem is that it is not allways. E.g if you just change the filename, 
then the error goes away ... maybe. Unfortunatelly You cannot step into 
melcode, at least I don't know how, so its kind of hard to debug. But 
will take some time to look into this.

> Is the print("preExp ...") supposed to call a function called preExp?
> The error is because this function does not exist? Or is it something else?


Nope, so what I am doing there is just a demonstration what happens with 
$path, $file and $type. "preExp" is nothing, but a possible command that 
you could trigger in there, when you would define it. So I just print 
out the concatenated command string.
In you case, you would write( e.g. ) preExportCommand_JS and if you 
require the values of Filepath, Filename, Filetype ( the textfields 
above ) you can inject those with the given variables. Same is true for 
postExport.


> Sorry for my MEL newb-ness...

HAH, my revenge will be TERRIFFIC ... when we come to the point that 
I'll require osg help ... Javier, this revenge will include you as well 
!!! ;-)

Cheers, PP