All that latex gives me a rash An SDK would be nice but a slightly lower level scripting API would be just as good. Zscripting’s foundation is pretty old now but it does allow you to accomplish most things, even if they sometimes must be done in roundabout ways.Īlthough I have grown fond of the zscripting idiosyncrasies and enjoy writing scripts, much in the same way some people enjoy putting on full body latex suits and whipping each other, I would welcome a change. The problem lies in the varying positions of the Merge Down message which can only reliably be determined when there is no user interaction at all. The interval is required as we want the the external library to return control to zbrush so that our zplugin can press the Merge Down button. Then you would create a dll that calls a function simulating a mouse click, at a specific position (the OK button) after a short time interval. If you can determine that then you can deduct where the OK button is located on the screen. The solution requires that you can reliably determine where the zbrush message appears when Merge Down is pressed. However, if you are creating a zplugin as part of an automation process that runs on a headless machine (i.e no user interaction at all), you might be able to duct tape a solution together. There is no reliable solution to using an external library to dismiss the note window based messages ZBrush displays, AFAIK. If you are creating a user zplugin then, as Dargelos mentioned, it would be best to require the user to press “always yes”.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |