Switch Selection concept for v13.5

[chucky]

Woah, that looks pretty awesome.

[chucky]

Woah, that looks pretty awesome.

Thanks to the above help from Alexandra and a break in my other work, I should be able to release this this week. It's very close. I just need to fix some image file management.

[Lukas]

Wow, amazing work Wes!

Edit: I've built and have been using a custom tool for switches within a rig too that I never got around to sharing. It has some nice buttons per switch:

• go to switchlayer (and back to bone layer)
• toggle timeline visiblity
• go to prev/next key
• see if there's a key at the current frame and if its step or smooth
• clean switch keys

If you want to implement any of that I can share the code and/or icons. My main problem ended up being limited toolbar space (especially on smaller screens). But its nice to control stuff from the bone layer without having to set up smartbones for everything (which also loses interpolation options). I've noticed having many layers visible on the timeline slows Moho down a lot, that's why I started experimenting with this, but it's also why I still sometimes wonder if its ever a good idea to rig with switch layers at all because I prefer seeing all of a characters keys on the top layer.

[gilcartunista]

Fantástico!!!Maravilhoso!!!Wes !!!Estou ansioso para experimentar!!!

[synthsin75]

Here it is: http://www.lostmarble.com/forum/viewtop ... 12&t=34078

[gilcartunista]

Estou tão contente que esta ferramenta foi lançada! mas no momento não tenho dinheiro para comprar moho13, tem alguma possibilidade de eu usar em minha versão 11, pois esta eu comprei e tenho número serial. Grato

[gilcartunista]

I am so glad that this tool has been launched! but at the moment I don't have the money to buy moho13, there is some possibility that I can use it in my version 11, because this one I bought and I have a serial number. Grateful

[kungfudork]

Holy Smokes! Thank you Wes! I've been in LA for a few months working nonstop and totally forgot about starting this thread. I can't wait to dive and use this. THANK YOU!

[rocky53204]

Quite interesting... will give it a try with an existing character.

[synthsin75]

While it's easy enough to pass arguments from Moho Lua to external apps/scripts, it's not as easy to get data back. I think the only way is to write the data to a file, so Lua can read it.

It can be done with:

Code: Select all

			function capture(cmd)
				local f = assert(io.popen(cmd, 'r'))
				local s = assert(f:read('*a'))
				f:close()
				return s
			end

This will return text, external command (script) outputs with its "print" calls

Apparently AutoHotkey can't output to the same command prompt Lua reads.

[SimplSam]

The other option would be to pass a filename to external app, which it populates, then read/delete the contents of that file after the call.

[synthsin75]

The other option would be to pass a filename to external app, which it populates, then read/delete the contents of that file after the call.

That's my current plan.

[hayasidist]

this (windows) example works without the intermediate file

Code: Select all

	local sOut = io.popen( "dir /B " .. path .. "*.png", "r" )
	local sData = sOut:read "*a"

IOW the output of cmd>dir ... is delivered in the fcb:read ... call (and in this instance provides a simple list of all the .pngs in path)

[synthsin75]

this (windows) example works (worked in Lua 5.2 - not tried in 5.4) without the intermediate file

Code: Select all

	local sOut = io.popen( "dir /B " .. path .. "*.png", "r" )
	local sData = sOut:read "*a"

IOW the output of cmd>dir ... is delivered in the fcb:read ... call (and in this instance provides a simple list of all the .pngs in path)

The problem is outputting from AutoHotkey, not reading with Lua.

[hayasidist]

ah! sorry. my misunderstanding