BTW, an alternative approach is to not use the platform attribute and instead in the code that implements the command check sys.platform and if it's Windows then raise chimerax.core.errors.LimitationError with a message that the command doesn't work / isn't available on Windows. LimitationError will present a dialog to the user with your message and will not produce a traceback / bug-report dialog. --Eric
On Nov 19, 2020, at 9:39 AM, Daniel Esteban Palma Igor <daniel.palma.i@ug.uchile.cl> wrote:
Great, thanks
On Thu, Nov 19, 2020, 14:22 Eric Pettersen <pett@cgl.ucsf.edu <mailto:pett@cgl.ucsf.edu>> wrote: Hi Daniel, Right now you would have to use two ChimeraXClassifiers. As of tomorrow's daily build, you will be able to use a comma-separated list of platform names in the platform attribute.
--Eric
Eric Pettersen UCSF Computer Graphics Lab
On Nov 19, 2020, at 8:08 AM, Daniel Esteban Palma Igor <daniel.palma.i@ug.uchile.cl <mailto:daniel.palma.i@ug.uchile.cl>> wrote:
Hi, I have a command that will work in mac and linux but not in windows, Should I create a separate ChimeraXClassifier for linux and mac with the corresponding platform attribute or there is a way to create only one ChimeraXClassifier for both? Regards, Daniel Palma Igor _______________________________________________ ChimeraX-users mailing list ChimeraX-users@cgl.ucsf.edu <mailto:ChimeraX-users@cgl.ucsf.edu> Manage subscription: https://www.rbvi.ucsf.edu/mailman/listinfo/chimerax-users <https://www.rbvi.ucsf.edu/mailman/listinfo/chimerax-users>
_______________________________________________ ChimeraX-users mailing list ChimeraX-users@cgl.ucsf.edu Manage subscription: https://www.rbvi.ucsf.edu/mailman/listinfo/chimerax-users