Fascinating! Sorry I did not understand before.

So pushing the button loads what Poser thinks is the configured path into the title bar. And we see colons, even though we used slashes. Now I think I understand the bug.

In slash notation, a leading slash indicates an absolute path.

In colon notation, a leading colon indicates a relative path.

When Poser changed the slashes to colons, it completely changed the interpretation of the path! In converting to colon format, it should have REMOVED the leading colon. This is a bad bug.

Now - what do I do about it? Try this as a test.

In your copy, change the code so that the path you stick into the button has the first character removed.  Open up vssui.py. Locate the class Wacros. Look in the show method. At the end of the os.path.join(vssFolder line, put [1:]

It should look like this - with the addition in bold below

 def show(self):
  for i in xrange(10):
   text = self.text[i]
   if text is None:
    text = self.emptyText
   call = self.functions[i]
   if call is None:
    call = ''
   elif not isinstance(call, basestring):
    call = os.path.join(vssFolder, self.pyfileFmt % (i+1))[1:]
   self.applyToPoser(i+1, call, text)

Then see if the buttons work.

---

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)