>> (even if I don't understand what IIRC means...)
I don't know what it means either :-)

>> To solve it, Chime developpers add a third argument to the
>> messagecallback method, wich is the number of the message.
>> That is to
>> say, with Chime, the function called by messagecallback gets these
>> parameters :
>> - 1st : the plugin name
>> - 2nd : the message itself
>> - 3rd : the message's number as it is adressed by Chime
>>
>> Some applications using Chime implement functions to reorder the
>> messages, using this third parameter.

Well I was thinking of adding a 3rd parameter to MessageCallBack to pass
more detailed/structure information while maintaining backward
compatibility. I guess it may have to be a 4th parameter ... ughh.


>> I think that it's not usefull in Jmol as long as this communication
>> issue doesn't exist...

Jmol will not have this 'ordering' problem.

However, we need to think about how to extend the CallBack functionality
while maintaining some compatibility.

I don't know if the right thing to do is add a 4th parameter, or create an
additional CallBack. What are your thoughts?


Miguel






-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
_______________________________________________
Jmol-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jmol-users

Reply via email to