Page 1 of 1
Vetala Beta 0.2.00
Posted: Sat Jun 03, 2017 2:43 pm
by louisVottero

- vetala_shotgun.PNG (16.89 KiB) Viewed 1354 times
You need to create a script in Shotgun and take note of the script name and key.

- vetala_shotgun2.PNG (9.88 KiB) Viewed 1354 times
After you need to put the script name and key into shotgun.
Whats new in the release:
- Shogun Link Data added - need to create a shotgun api script to connect in the settings.
- util_file.get_latest_file_at_path(path) added
- Changed settings tab to a gear
- Clicking on a script in the manifest will now focus on its tab or window if open.
- Added setting to define what double clicking on a manifest item does. Open tab, open new window or open in external.
Re: Vetala Beta 0.2.00
Posted: Tue Jun 06, 2017 11:54 am
by louisVottero
There is a ugly bug with 0.2.00 where the icons and breakpoints are not showing up in the code editor. Also the shogun integration needs to be improved slightly.
I will have a new version up tonight. Sorry for the weird bugs.
Re: Vetala Beta 0.2.00
Posted: Tue Jun 06, 2017 10:13 pm
by louisVottero
The downloads above have been updated with the following. They should be golden now.
- A bitter better feedback when shotgun fails.
- Locator position mirroring fix
- Code editor was not displaying its status. And breakpoints were broken.
Re: Vetala Beta 0.2.00 (Code view not stable!)
Posted: Wed Jun 07, 2017 2:59 pm
by louisVottero
Code doesn't parent properly in this release. Please hold off on using this release!
Re: Vetala Beta 0.2.00 (Code view not stable!)
Posted: Wed Jun 07, 2017 4:10 pm
by louisVottero
The files above have been updated and fixed, including
- code ui can now parent again
- script focus no longer gives an error when no code found
- The function that was changed that caused the issue was reverted back to 0.1.18. A new function was created for the new functionality. Should be stable.