W_hotbox v1.7


 
This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: Wouter Gilsing
UPDATED v1.7. Hotbox for Nuke, similar to Autodesk Maya's. Selection specific menu that appears underneath your cursor for as long as you press the shortcut. Fully customizable, with interface to easily add and modify buttons on the fly. See the video in the description for a demonstration.
Requirements:
11.0, 10.5, 10.0, 9.0 or later
Linux, Mac, Windows
30 Jun 2017
2054

watch the video Tool Video

W_hotbox


A hotbox for Nuke similar to the one found in Autodesk Maya.

 

Watch the tutorial:

vimeo

 

W_hotbox is basically a fully customisable ‘favourites menu’ that pops up for as long as you press the shortcut and disappears as soon as you release. The buttons that make up the menu represent python scripts and change depending on you selection. The 'Hotbox Manager' offers you an user friendly interface which allows you to add new buttons on the fly. Those buttons are directly accessible via buttons that appear in the menu under your cursor.


You have the option to create buttons that either show up when specific node (combinations) are selected, as well as buttons that will show up no matter what is currently selected.

 

The hotbox while having a Merge node selected:

introHotbox

For me it changed the way I interact with Nuke completely and it sped up my workflow quite a bit. The ability to move any action to a button that appears near your cursor saves you a trip to the other side of your screen and back pretty often.

Besides that I use it a lot to automate repetitive tasks and actions I would otherwise probably not have taken time for at all. (Think of things that make your script more readable, but don't necessarily contribute to the final image, like (color)labeling nodes.).

However, you can add whatever buttons you like, so it's totally up to you how you put the hotbox to use.

 

 The Manager, an interface to add and modify buttons on the fly:

manager new

The download includes a user guide that features an in-depth description of everything there is to know about the hotbox. It also includes an installation guide and some basic python examples. Besides that, the download also comes with a bundle of buttons you can choose to install, so you don't have to start from scratch.

 

manual
Make sure to follow the steps in InstallationGuide.txt to install the tool properly. To upgrade from an older version, simply replace the old ‘W_hotbox.py’ and ‘W_hotboxManager.py’ with their updated versions.

 

If you decide to install the tool in a studio environment I would love to hear which studio! (Just because I think that's a fun thing to know :) )

 

See the change log on page 21 of the user guide for a complete overview of all the added features as well as an overview of the fixed bugs.

 

Highlighted features that were added:

NEW IN V1.1:

  • Added the option to have multiple repositories to store buttons in. To make the tool suitable to be installed in a studio environment. Buttons loaded from an additional repository will appear outlined grey, rather than black. See the chapter called ‘Working in a studio environment’ of the user guide for more information.
  • Option to hide the ‘iconsLocation’ knob from the preference panel so artists won’t be able to change it, when installed facility-wide.
  • When importing an archive of buttons, the buttons will now append the current set, rather than replacing it.

NEW IN V1.2:

  • Improved the way of defining additional repositories (feature added in v1.1). Rather than changing the actual python files the repositories can now be defined by setting environment variables, called ‘W_HOTBOX_REPO_PATHS’ and  ‘W_HOTBOX_REPO_NAMES’ (See page 13 of the user guide for more information)
  • Same applies for hiding the ‘hotboxIconLocation’ knob from the preferences panel (‘W_HOTBOX_HIDE_ICON_LOC’).

NEW IN V1.3:

  • Knob added to the preferences panel to control the hotbox’s font size.
  • License added
  • Knob formerly called ‘iconLocation’ renamed to ‘hotboxIconLocation’.
  • Improved the way archives will get created when none is present.

NEW IN V1.4:

syntaxHighlighting

  • Improved script editor. The script editor of the Manager now includes line numbers, syntax highlighting and auto indentation to make writing code easier. Tab’s will be automatically registered as four spaces.
  • Error catching. Whenever executing a hotbox button causes an error, the problem and it’s corresponding line now will be printed.
  • The Hotbox will now function properly in combination with nodes inside groups.

NEW IN V1.5:

  • In the script editor, the background color of the selected line now reflects the current state of the loaded script (black - unchanged, white - modified, green - just saved).
  • Added the option to launch the hotbox with a single tap, instead of having to keep the shortcut pressed. This mode is available through the ‘Launch Mode’-dropdown in the preferences.
  • Reorganised the preferences panel and assigned tooltips to all its knobs.

NEW IN V1.6:

coloredButtons

  • The option to easily change the colors of the text and background of a button.
  • Templates: The ability to save snippets of code to quickly access at a later point in time.
  • No-click execution: Execute the button underneath the cursor upon closing the Hotbox.
  • New button order system.
  • Auto save. No need to click the 'save' button anymore as changes will be saved automatically.
  • Option to change to Manager’s font size.
  • Tooltips added to Manager.
  • Fixed transparency issues on Linux. 

NEW IN V1.7:

  • Added support for PySide2 (Nuke 11) for Windows and Mac.
Copyright (c) 2016, Wouter Gilsing All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Redistribution of this software in source or binary forms shall be free of all charges or fees to the recipient of this software. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Please login in order to download these files.

Comments   

 
+5 # Frank Rueter 2016-08-23 23:08
Awesome. I have wanted this for years and never had the time to finish my own version to a degree that is production ready.
Thanks heaps!
 
 
+2 # Wouter Gilsing 2016-08-24 00:04
Ah thanks! Glad to hear that you like it:)
 
 
+1 # Erwan Leroy 2016-08-24 01:57
This is great for Developers!

Limited Menu space has always been an issue for small pipeline/node related scripts. I had been stashing this kind of small scripts inside Edit/Nodes for years for lack of better option.

Can the hotbox menus be edited in script directly instead of using the hotbox editor? (I haven't installed your script yet, just watched the video)
 
 
# Wouter Gilsing 2016-08-24 02:06
Glad you like it!

You'll eventually need to put the code in the Hotbox Manager to assign it to the desired nodeclass/butto n.

However, if that works better for you, you can write your code in Nuke's script editor and paste it over when you're done, (as you can still use Nuke while having the Manager open).

Improving the Manager's script editor with basic stuff like line numbers etc, is somewhere on my to-do list for a future release.

Hope that answered your questions.
Cheers
 
 
# Erwan Leroy 2016-08-24 02:24
I meant, the script you put in the editor is eventually being saved somewhere (a .py or other file somewhere on the system).
Can these files be directly edited easily?

This way the code can easily be maintained and pushed facility wide.

It's not a deal-breaker to have to open nuke to find the function and edit it, it's just that I'd rather open the file and edit the code there in any text editor.
 
 
# Erwan Leroy 2016-08-24 02:36
Oh, okay, I installed the hotbox to look into your code.
I found the .py scripts inside the .hotbox tarball, so it's editable but not particularly easy to do so.

Quick question: Why adding a menu option for the icon path instead of making them part of the pluginPath and being directly recognized?
 
 
+1 # Wouter Gilsing 2016-08-24 03:29
You can of course simply call external modules from a button, if that answers your question. That way you don't actually have to put any code (except for an import statement and a function call) in the script of the button. So you can just open your big studio wide module, and edit it in your preferred editor and just link a hotbox button to a function of that module. That's the way I work with studio specific code at work.

Icons:

I added that option so users without any python knowledge won't run into trouble while installing, yet are still able to choose a custom location to store the icons. Not every artist has custom folders added to his/her pluginpath. That leaves two options:

1) Forcing them to add a folder by adding a line of code to init/menu.py to ensure that path is included in the pluginpath.

2) Making them drop everything directly into ~/.nuke.

Option 1 is obviously the preferred option, but can be challenging for artists that are less technical. Option 2 will create a mess.

I think the way it's currently handled is pretty easy and foolproof: Just open the preferences and point to the folder where you decided to store the icons. Done.

I get your question, I just went with this method to make it a bit harder for less technical compers to run into trouble:)
 
 
+2 # Parimal Desai 2016-08-24 04:04
Wow! Good Work :-)
 
 
+3 # Markus Gratl 2016-08-24 12:44
Nice. Used it for 30seconds and I already love it. Thanks for sharing.
 
 
+1 # Daniel Mermelstein 2016-08-24 15:44
That's amazing. Looks like a great time saver tool. Your demo looks great too.
As a feature request, I would suggest a way to export/import buttons and classes among other Hotbox users.
Thanks
 
 
+1 # Wouter Gilsing 2016-08-24 16:01
Hey Daniel, thanks for the compliments.

You actually are able to share sets of buttons between workstations/ar tists. Have a look at the section 'Importing and exporting buttons' in the documentation pdf (I didn't want the video to become to long, so I only included the most important stuff). You can even import/export from your clipboard so you don't have to save out any files to disk. As of right now you can only export all your buttons at once though, so I might look into this to make it easier to share a single button. Thanks!
 
 
# Erwan Leroy 2016-08-25 01:56
Hey Wouter.
Did more testing last night. One feature that could be huge would be the option to append rather than replace when importing buttons.
I can easily see people wanting to share their setups, but if we have to replace our own every time it gets cumbersome.
 
 
# Wouter Gilsing 2016-08-25 02:02
Hey Erwan,

Totally agree, and since multiple people brought this up today, consider it done for v1.1 :-)
 
 
# Wouter Gilsing 2016-08-29 02:10
Hey Erwan and Daniel,

I just made version 1.1 available which appends the current set of buttons rather than replacing it when importing an archive.
 
 
# kire timov 2016-11-18 04:20
Quoting Wouter Gilsing:
Hey Erwan and Daniel,

I just made version 1.1 available which appends the current set of buttons rather than replacing it when importing an archive.

I hope it's possible in the new version (haven't had the chance to try it out yet) to choose, replace or replace. e.g. i sit on other artists pc who is also using w_hotbox, bud i't like to load my buttons only, and not his/hers. - that' be nice
 
 
+1 # Wouter Gilsing 2016-11-18 04:24
If you load an archive, it will append the current button set. However, you can quickly trow out the current set of buttons by going "Edit-W_hotbox- Clear-Clear Everything" (or clear a specific section).
 
 
# Daniel Mermelstein 2016-08-24 16:14
Never mind me... you had that feature already of course.... Great product ! Thanks Again
 
 
+1 # Adrian Sutherland 2016-08-24 16:38
I've been waiting for someone to put one of these together at a production ready level. This is awesome. Thanks for this!
 
 
+1 # Charles Taylor 2016-08-24 18:47
Yes! This looks like a game-changer. Good stuff.
 
 
+1 # jean-luc azzis 2016-08-24 20:07
this is awesome! thanks for sharing

Just a quick word of caution, when I imported the archive, it looks like it created a Python folder in the ./nuke folder and imported the presets there. The problem is that I already had a Python folder in that location and it replaced it. so I lost all the content of that folder (I had a backup so not a big deal, but I think there should be a warning if the folder already exists) .

Also quick question about the hotbox in Nuke Studio, it's not showing up in the timeline, is that a limitation?

I also wanted to use it to switch between workspaces, would that be possible?

Cheers and Thank you for making this!!
 
 
# Donald Strubler 2016-08-24 20:20
We ran into this same issue, where the entire directory was removed.

rmtree should be used with caution if not alerting the user
 
 
# Wouter Gilsing 2016-08-24 20:38
You guys are talking about the contents of the hotbox folder inside the .nuke folder right? As of right now, importing an archive indeed replaces the currently existing archive. I'm sorry if this caused any problems.

I'm planning on implementing a 'merge' archives function in a future release. Also good idea to warn the user. Thanks for the feedback
 
 
# jean-luc azzis 2016-08-24 20:43
No it was this folder : ~/.nuke/Python

It wasn't inside the W_hotbox folder
 
 
# Wouter Gilsing 2016-08-24 20:49
Well that should definitely not have happened. Did you change the 'hotbox location' in the preferences to that Python folder?
 
 
# jean-luc azzis 2016-08-24 20:52
yes I did.
I changed it to that location actually. but after importing the archive, the ~/.nuke/Python content was replaced with 3 folders. All, single, multiple. Even the W_hotbox was gone.
 
 
# Wouter Gilsing 2016-08-24 20:59
Ah I see now... Make sure to point that knob in the preferences to the W_hotbox folder, not just the folder containing that folder. So in your case make sure that knob is set to '~/.nuke/Python /W_hotbox', rather than '~./nuke/Python/').

I'll make sure this will be more clear in future releases. Thanks
 
 
# jean-luc azzis 2016-08-24 21:01
got it.

I have changed it now. Thanks for the quick reply!
 
 
# jean-luc azzis 2016-08-24 21:03
and about the Nuke Studio timeline hotbox and workspace selection? Is it possible?
 
 
# Wouter Gilsing 2016-08-24 21:42
Quoting jean-luc azzis:
and about the Nuke Studio timeline hotbox and workspace selection? Is it possible?


Not sure about the Nuke Studio question, as I never use it. Good idea to look into that though.

"If you can access it through Python, you can wrap it in a hotbox button". Workspaces are a bit more tricky when it comes to accessing them, but it's possible.

Try putting this in a button:

from hiero.ui import findMenuAction

findMenuAction('NameOfYourWorkspace').trigger()

Cheers!
 
 
# jean-luc azzis 2016-08-24 21:46
great! I'll give it a go.

Thanks!
 
 
+1 # jean-luc azzis 2016-08-25 01:49
That works perfectly, thanks!

I love this. Best plugin in a long time!!
 
 
# Indrajeet Sisodiya 2016-08-24 22:21
Cheers! THIS IS AWESOME!
 
 
# kire timov 2016-08-25 02:56
Zomg nice work mate, thank you for sharing!

I found couple of bugs in your archives

first is FilterErode script:

import nuke

for i in nuke.selectedNodes():
i.knob('output').setValue('alpha')

output should be set to "channel" instead.



the second thing is with the merge node

BBox/Union dosent cycle through B/union

I couldn't figure that out..

Again thank you for sharing, such a nice tool to have
 
 
# Wouter Gilsing 2016-08-25 03:05
Ah, nice catch! I'll make sure they get fixed.

If you want to get the bbox one working, you can use the following code:

for i in nuke.selectedNo des():
if i.knob('bbox'). value() == 'union':
i.knob('bbox'). setValue('B')
else:
i.knob('bbox').setValue('union')

Thanks
 
 
# MARK PINHEIRO 2016-08-25 05:25
Blinding. Can't wait to try this. I'm under the bonnet of Nuke and Shotgun atm customising a pipeline and I'd much rather stay in the drivers seat 8)
 
 
# Stefan Müller 2016-08-25 09:26
Breathtaking!

Even for really simple stuff, like creating a node that doesn't have a default shortcut it's super useful and a real timesaver.
I especially liked the +1 and -1 buttons for saturation. I changed it to 0.1 however :)

One thing I noticed: The arrangement/ord er of the buttons seem kinda random. I am able to change the order in the hotbox manager, however it doesn't seem to match with the arrangement in the actual hotbox.
Is this a bug?

Cheers,
Stefan
 
 
# Wouter Gilsing 2016-08-25 12:26
Hey Stefan,

Thanks for the kind words and bringing up the buttons order.

It's not a bug, and I would like to refer the the bottom op page 11 in the pdf userguide :-) (comes with the download).

It basically comes down to this:

By default new buttons will be added left and right of the row alternately (rather than just putting them the the right of the last button).

I did this to take in account any muscle memory.

Imagine working with the hotbox for half a year or so, with only one button added to a nodeclass. That one button will appear right above the center (as there are no other buttons). However, after half a year we decide to add a bunch of new buttons. These buttons would have pushed our first button away. This might take a bit time to get used to, and you might find yourself searching for that one button because it's not in its usual spot anymore.

That's why I decided to make new buttons appear left and right of the row alternately. This way a button barely move when adding new buttons, unless you manually change the order in the Manager (I say 'barely' because the node will move 'half a button' when the amount of buttons in a row switches from odd to even).

Anyway, if you don't like this behavior you can disable it by turning off ‘Add new buttons to the sides’ in the preferences! That way buttons will simple appear to the right of the last button.

Hope that made it more clear,

Cheers
 
 
# Stefan Müller 2016-08-25 15:33
Hey Wouter,

aaah, I should've read your pdf entirely :D

Thank you for your explanation. Pretty clever, the thing with the muscle memory. It's great to have a button to change this behavior, but now it does indeed make more sense the way you intended it to be!

Cheers!
 
 
# Tor Andreassen 2016-08-25 10:58
This is brilliant, great work. Tested it for a few min and love it, will absolutely use this when I have doodled around with it enough to get my most used scripts up running with it. My favorite though is the simple stuff like the pre-shipped buttons you have for shuffle for example, so brilliant. Thanks for sharing this!!

The only thing I found was that it gets cropped off if you try and open it too far down in the node graph.. so you have have to move the mouse pointer a bit further up in the node graph and launch it again to see the whole menu. I'm running it on OSX. Maybe you already know of this? Would be awesome to see an update if the future where it always launches on the center of the screen, or at least don't get cropped off.

Again, absolutely killer work Wouter, thanks for sharing this tool!!
 
 
# Matthieu Cadet 2016-08-25 13:45
Awesome ! something I wanted to code also some years ago, finally you did it :) thanks !
 
 
# Wouter Gilsing 2016-08-25 14:42
Hey Tor

Thanks for the feedback, good idea. I'll add that to my to-do list as well! :)
 
 
# Tor Andreassen 2016-08-25 14:53
Awesome, thanks Wouter :)
 
 
+1 # Matthieu Cadet 2016-08-25 14:50
Also one advise, as your tool is becoming viral :)
put it on Github for easy issue/question/ feature tracking ;)
I would also love participate to its improvements if it's on github.
 
 
# Indrajeet Sisodiya 2016-08-25 15:18
Hey Wouter.

Idk if its a bug or something, but I created a delete node and it appeared at the bottom of the list "ALL" as I wanted to have the functionality to delete selected nodes. Tried to move the entry above existing entries and it seems to glitch out. I accidentally dropped it inside Coding sub menu and now when I dragged it out, it just stays there, inside the sub menu.
It would be great as a feature request if you incorporate two button under the new, delete,copy,pas te buttons, basically two arrow keys, one up and one down so pressing it would push the entry upwards or downwards and hence the button in the hotbox changes its position accordingly.

Thank you wouter for this awesome tool!
 
 
# Ben Warburton 2016-08-25 16:28
Great work!

One thing I noticed from a script i was launching was to do with the shortcut key. I'm planning on leaving it on the ` key but I have a problem. If a text field opens it fills the text boxes with `````````

Would it be possible to eliminate the shortcut key press after you click a hotbox button? even if you are still holding it
 
 
# Thomas Vu 2016-08-26 08:13
great work sir!

the shortcut key not working on nuke 10 sir (tried to change to other key also)
 
 
# Wouter Gilsing 2016-08-26 17:47
Would you mind sharing your operating system? Did you made sure to restart Nuke after changing the shotcut?
 
 
# Thomas Vu 2016-08-27 16:07
im running on win7, but its ok, i will find out some way to fix it, i install it on other computer its work what ever nuke version, reason is i had alot of script runing thats why your script not working. Anyway, thank you so much, again GREATTTT WORRKKKKK
 
 
# Mohan Pugaz 2016-08-26 09:05
Amazing work totally changed the way of working! .. awsome :roll:
 
 
# Michael Habenicht 2016-08-26 14:55
Thank you very much for this great tool and your included buttons!!!

Unfortunately on Centos 6.5 with Gnome and nuke 9.0v7 the transparency is also not working.

Also the box doesn't close any more. If I release the hotkey or click on a menu the hotbox stays. Only clicking outside of it closes it.

For the future it would be very nice to be able to define various hotbox locations through an env variable which get merged together. So there could be a write protected global studio location and a local location where an artist can store overwrites and additional buttons. Each location could also have an icon that is shown at one corner of the button so that you see wether the button comes from.
With this gizmo or plugin creators could also already include a button setup whichs location only needs to be added to the env variable to include it.

I also recommend putting it on github for easy contribution.

Best regards!
 
 
# Wouter Gilsing 2016-08-26 17:47
Hi Michael,

Thanks for the reply! I'm planning on including the option to use multiple locations to draw buttons from in the next release. I've been working on that last night and it seems to work now.

Sorry to hear about the problems you experience with GNOME. I'll see what I can do about that.

Cheers
 
 
# Wouter Gilsing 2016-08-29 02:15
Hi Michael!

I just uploaded a version 1.1 which makes it possible to add multiple repositories to load buttons from, to make the tool more suitable for a facility-wide implementation.

Unfortunately I've not been able to look into the Gnome related issues you mentioned yet.

Cheers
 
 
# Wouter Gilsing 2016-08-30 05:35
Version 1.2 changes to way of adding additional repositories. Rather than editing the actual Python files, you now can add them using environment variables.
 
 
# Michael Habenicht 2016-08-30 09:30
Hi Wouter,
thank you for your fast new versions. Additional repositories works great. I had the env variable already added myself.

The transparency seems to be a known problem simply if the window manager doesn't support it.
The other issue seems to be a problem of combinations of hot key and keyboard layout. So the default key didn't work with the german layout but the space bar and other keys work fine.

I implemented another feature which is that you do not have to click the button to execute it. Simply select it and release the hotkey and it gets executed. I find it more convenient especially when using a tablet. If you are interested in the changes, let me know!

Cheers!
 
 
# kire timov 2016-09-20 00:13
Quoting Michael Habenicht:
Simply select it and release the hotkey and it gets executed. I find it more convenient especially when using a tablet. If you are interested in the changes, let me know!

Cheers!


I am interested, how can i change the behavior to work like that?
 
 
# Claus Steinmassl 2016-08-26 15:25
Super awesome and helpful tool! Thanks very much for sharing! :)

I've got two feature requests:

1: I have a problem with all scripts, that pop up a user input since that input is flooded with the shortcut I'm pressing to open the hotbox. Maybe it's possible to catch that 'key down' event, until the shortcut is released? But maybe this could lead to other problems, when the shortcut is used for something else. e.g. right now I use the space bar as hotkey, which works great for opening the hotbox and toggling the window fullscreen! Maybe you've got a solution for this?

2: Could you add that kind of separated-by-da shes-list-thing to the single mode as well? e.g. I want certain functions to be available for roto & rotopaint nodes. Right now I've got to copy them, since the Multiple-mode would require both to be selected, but I just want to share the same functions across different classes. So maybe instead of defining 'Roto' and 'RotoPaint' with the same functions I wish do something like 'Roto-RotoPaint ' in Single-mode. I hope this makes sense. :)
 
 
# Wouter Gilsing 2016-08-27 05:49
Heey Claus,

Thanks for the reply. I totally agree with you about point 1. I'm using the hotbox myself a lot, and this is one of the annoying things that could use a bit of polishing. I'm currently working on a v1.1 release (should be online around the end of the weekend/monday) . I'll see what I can do, but can't guarantee this will make it into it.

2) I actually 've though about this a long time, and at one point this was the way it worked. However I found it starting to get a little messy, because you got so many different classes.

For example we have node A,B and C. There's a button I'd like to have shown when any of those are selected, so I add a class called ABC. However I want to add buttons that show up for them individually as well, so I add class A, class B and class C separately. Then I get this idea for a button that is really cool for A and C but doesn't really make sense for B, so I add another class called AC. Now after working with the buttons for a while I get an idea of how to improve one of the existing buttons assigned to class A. Rather than simply going to class A and changing the button, I now have to go look for it as it might be stored in A, AC, ABC, AG or AZ etc. You see what I'm getting at? I felt it started to get messy, and it kinda lost it's nice overview. Besides that the code got more complex and I was afraid the hotbox might lose speed. Therefore I decided to go with an 'one class only' approach for the single mode.

I hope you do understand, thanks for sharing ideas though, much appreciated!
 
 
# Claus Steinmassl 2016-08-28 10:18
1) Looking forward to a solution for this, but no hurry! ;)

2) Yeah, I get it. Your decision makes totally sense, to avoid a big mess.
 
 
# Tor Andreassen 2016-08-27 11:13
Hi Wouter,

Had another spin with this to test it on linux and ran into a few issues.

Running this on OSX worked perfectly fine and did not give these problems.

CENTOS 6.2, gnome 2.28.2, Nuke8.0v6 gave these issues:

1) it seems to overwrite the nuke preferences, or delete them. You can add them back but every new session when the W_hotbox is installed, nuke does not seem to want to pick up the saved preferences (like node colors, pipe thickness, dot size and so on).
I tried to save out the preference file and copy it back into the .nuke location after installing your tool, but that did not work.

2) on removing the tool, it leave the icons path still in its own tab in the preferences (the tab is renamed to the default name 'User') No error messages show up, but its still there even if the 'delete preferences' button is clicked and all hotboxfiles is removed from the .nuke location. It seems like the uninstall process removes everything besides the icon path, and therefore creates a default tab called ('User') where the icon path remains since it was not fully removed. (my guess)

3) Transparency issues. When checking the button called 'disable transparency' it turns on the transparency, the opposite of what I would expect. On OSX is does the inverted right action.
Also another issue on linux is that it does not seem to remember the transparency checkbox value, so for every new session of nuke, I have to go and check the box again.

Would be great to hear if you have had similar issues and possibly have a fix for it. Would love to be able to use this at work, and absolutely will if you have a fix for the preference problems.

Thanks again for sharing your work on nukepedia :)
 
 
# Wouter Gilsing 2016-08-27 16:17
Hmmm, that doens't sound very good at all... I'm not sure how well the tool works on Nuke 8 btw, (I'm actually kinda surprised it didnt trow an error at startup in the first place).

Thanks for the detailed description, I'll definitely have a look at it! I'm planning on releasing a v1.1 later this weekend/earlier next week, but I can't promise anything regarding the Gnome related bugs (so far I've only been able to test the tool in KDE environments).
 
 
# Tor Andreassen 2016-08-28 03:18
Alright, good to know. Was it developed to work on 10 also? We currently don't use 10 yet, but good to know for when we do switch over. I'll see if I'm maybe able to change environments to KDE.

That could explain why the script was not acting up on OSX, as I'm running Nuke9 there.

Thanks for the quick reply.
 
 
# Wouter Gilsing 2016-08-28 03:23
Yep, tested and working on both 9 and 10:) I'll include that in the User Guide as well, as that is currently missing. Cheers

You are right about the 'iconLocation' knob remaining after clicking 'delete' preferences though. That will be fixed in v1.1.
 
 
# Tor Andreassen 2016-08-28 03:26
Great, thanks :)
 
 
# Wouter Gilsing 2016-08-29 02:54
Just uploaded v1.1. Should be fixed now!
 
 
# Tor Andreassen 2016-08-29 12:16
Awesome, thanks Wouter!
 
 
# Tor Andreassen 2016-08-29 13:56
Quoting Wouter Gilsing:
Should be fixed now!


Tried installing and removing the tool again, to test it. (on OSX nuke9).

Seems that it removes the icon path. but the Other tab stll has an empty User tab there.

Any way you could fix it so it removes the tab as well, so that it restores it to the vanilla nuke state before the tool was installed?

Thanks!
 
 
# Wouter Gilsing 2016-08-29 14:25
Ah the thing is that User tab was never really an (intended) part of the hotbox. It gets created by default by Nuke when you try too add something to the preferences without creating a new tab first.

There's quite a possibility that people are actually using a tab called User in their preferences to store custom knobs, so forcing it to delete is risky as it might cause problems for some.

Since the source of the problem is fixed (no new User tab will be created when deleting the preferences) I think it's easiest/safest to manually clean up the (harmless) mess that was caused by it.

With Nuke closed, open your preference file in a text editor (~/.nuke/prefer ences10.0.nk or 9 ofc) and look for this line:

addUserKnob {20 User}

Remove it, save, start Nuke.

Sorry for the inconvenience and as always thanks for reporting back to me:)
 
 
# Tor Andreassen 2016-08-29 14:50
Yes you are right, better leave it be then. I was not aware that it was stored in the preference file - that's an easy enough fix. Thanks for that!

Also, very minor thing; for your tools-bundle. Had a look at the shuffle python scripts. You might want to add this on the following: alpha, solid alpha, red, green, and blue:

i.knob('in').setValue('rgba')

If you push the Depth shuffle option, the 'in' value gets changed to 'depth', and pressing your current red shuffle or any of the other's mentioned above, after having pressed depth, leaves the 'in' value to depth, so you might want to change it back to rgba so the shuffle works as intended if you jump between depth and other shuffle types.

As said, very minor, but though I'd mention it.

Cheers for your quick updates. Exited to start using this in production when we swap over to nuke10.
 
 
# Wouter Gilsing 2016-08-30 05:33
Hey, I improved some stuff concerning adding extra repositories (which work with environment variables now, yay). I just uploaded this as v1.2.

While on it, I decided to change the shuffle scripts you mentioned as well, good catch!
 
 
# Tor Andreassen 2016-08-30 12:16
Awesome, more studio friendly!
 
 
# Adrian Pueyo 2016-08-27 20:49
This is great!!!!!
 
 
# Claus Steinmassl 2016-08-29 12:26
I think, I got just another feature request... :)

Could you add a global setting for font size, family etc. to the nuke prefs? I know I can adjust individual buttons, but it would be nice to have a global setting for all buttons, so I can adjust it independent of my current global nuke settings.
 
 
# Wouter Gilsing 2016-09-02 20:28
Hey Claus,

I used to have this built in for quite some time before I released the tool. However, every now and then, the font knob would randomly glitch out, throw an error and reset. So I decided just to remove it completely.

However, now I've seen the hotbox in action on a variety of operating systems, resolutions etc, I definitely see the need for a font controller.

I played around with it a little bit and added a knob that allows you to change the font size. The font family will be matched to the rest of the Nuke interface.

It will be available when I release version 1.3! Thanks for the input.
 
 
# Claus Steinmassl 2016-09-05 12:03
Great! Thank you very much for your effort!
 
 
# Wouter Gilsing 2016-09-06 15:41
No worries! I just uploaded v1.3, which has the font size controller.
 
 
# li zhaohui 2016-08-30 15:59
How to add the existing script button? For example: roto_to_track ()
 
 
# Wouter Gilsing 2016-08-30 16:03
Well you could do this two ways.

1) Copy the whole script into a new button. Make sure to put the function call at the end.

2) put an import statement at the top of your button to import that module, and call the function at the end. For example:

import roto_to_track
roto_to_track.roto_to_track ()
 
 
# li zhaohui 2016-08-30 17:39
Thank you
So a new repository Adding, windows how to operate it? Whether there are specific instructions?
 
 
# li zhaohui 2016-08-30 17:54
First methods are feasible.
The second method is not successful! Do not know why? I don't want to put the whole script in!
 
 
# Wouter Gilsing 2016-08-30 18:18
Try running the code from the script editor and look at the error it returns. Also make sure the script is part of the your nuke plugin path.
 
 
# li zhaohui 2016-08-30 18:22
All right!
But I don't know how (a new repository Adding)
 
 
# Wouter Gilsing 2016-08-30 18:25
Have a look at page 13 of the user guide.
 
 
# li zhaohui 2016-08-30 18:38
Specific how to do it? In the windows system? I added the environment variable as follows:
C:\tmp\n2; NUKE_HOTBOX_REPO_NAME=C:\tmp\n1
C:\tmp\p2; NUKE_HOTBOX_REPO_PATHS=C:\tmp\p1
I created these folders, but still don't display the menu?
 
 
# Wouter Gilsing 2016-08-30 19:25
Add them like this:

W_HOTBOX_REPO_NAME=name1;name2
W_HOTBOX_REPO_PATHS=C:\tmp\p1;C:\tmp\p2

Instead of name1 and name2 use description of your repositories you want to add. Like SHOW or FACILITY.
 
 
# Vadim Samusenko 2016-09-05 12:20
Hey, great tool, seems to work perfectly for everyone.

But in my case, neither any of the buttons in the hotbox manager related to adding a class or a button, not the import feature doesn't work. The buttons are just not leading to any action after being pushed, import feature opens up the file browser, I navigate to the .hotbox bundle, click import and nothing happens, browser closes and finale.

any ideas ?

OS X El Capitan, NukeX 10.1
 
 
# li zhaohui 2016-09-05 15:23
This version does not automatically create a Library folder. So import library is not successful. To manually set up before you can.
 
 
# Vadim Samusenko 2016-09-05 16:36
Can you please explain what should I do step by step ? I don't really get what additional stuff and where should I create
 
 
# Wouter Gilsing 2016-09-06 15:08
Hey, I just uploaded v1.3. Let me now if that fixes the problem for you!
 
 
# Vadim Samusenko 2016-09-09 10:05
Quoting Wouter Gilsing:
Hey, I just uploaded v1.3. Let me now if that fixes the problem for you!

Yeah, everything works great! Thank you
 
 
# li zhaohui 2016-09-06 18:11
After the establishment of the repository in Explorwr reveal does not play a role
 
 
# Wouter Gilsing 2016-09-07 00:49
Meh, on some very rare occasions it can come in handy though. I originally used it a lot while I was building the tool. Since I did not really have something better to put in its place I just left it there.
 
 
# li zhaohui 2016-09-06 18:14
In addition, I think for the average user can hide in reveal Explorwr and Manager hotbox button
 
 
# Jung Keun Kim 2016-09-07 07:02
need help here~ i want to add a button (Cache -> Localization -> Force Update -> Selected) in read node.
i don't know what python code i add to hotbox manager..
could you help me?

by the way you are super awesome!!
 
 
# Wouter Gilsing 2016-09-07 14:01
Heey! Have a go with this code:

nuke.localization.forceUpdateSelectedNodes()

I agree that whole new localization section is not really the best documented part of Nuke 10 when it comes to python...
 
 
# li zhaohui 2016-09-07 15:29
W_HOTBOX_REPO_NAME=name1;name2
W_HOTBOX_REPO_PATHS=C:\tmp\p1;C:\tmp\p2
 
 
# Wouter Gilsing 2016-09-07 17:30
These are the environment variables you can use to define additional repositories...
 
 
# li zhaohui 2016-09-07 18:07
W_HOTBOX_REPO_NAME=name1;name2
W_HOTBOX_REPO_PATHS=C:\tmp\name1;C:\tmp\name2
 
 
# Wouter Gilsing 2016-09-07 18:09
Not too sure what you are trying to say here...
 
 
# li zhaohui 2016-09-07 18:28
W_HOTBOX_REPO_N AME = name 1, name 2
W_HOTBOX_REPO_PATHS = TMP C:\ \ name 1; TMP C:\ directory \ NAME2
Variable names are not (NUKE_HOTBOX_RE PO_NAME) and (NUKE_HOTBOX_RE PO_PATHS) but (W_HOTBOX_REPO_N AME) and (W_HOTBOX_REPO_ PATHS)
 
 
# Wouter Gilsing 2016-09-07 18:32
Ah you are right. I see I put both in the userguide. Ill correct that for the next release, thanks.
 
 
# Siva S 2016-09-07 13:00
Thanks Wouter Gilsin! I think this tool will hit the maximum downloads soon... Great job!
 
 
# Simon Jokuschies 2016-09-09 06:08
W_Hotbox seems to overwrite the preferences.nk file in the nuke home dir. Whenever I change something in my settings and restart nuke the changes won't be applied. As soon as I uninstall W_Hotbox everything works fine. My main operating system is MacOSX using Nuke8,9 and 10. Has anyone noticed this behaviour on Windows and Linux as well?
 
 
# Wouter Gilsing 2016-09-09 06:15
Interesting. I know the tool isn't working with Nuke 8.

However, I haven't heard of any problems considering the preferences on Nuke 9 or 10 in combination with OSX. What version of OSX are you running?
 
 
# Simon Jokuschies 2016-09-09 09:45
I'm running Maverics. When I hit the ok button to save the current settings they don't get written to the preferences.nk file. Does W_Hotbox maybe overwrite some nuke internal functionality?
 
 
# Wouter Gilsing 2016-09-09 15:35
It does not overwrite any internal functionality. I'll have a look at this ASAP though! Thanks for reporting.
 
 
# Andrew Mumford 2016-09-15 19:03
Has anyone had this working using the Wacom Remote puck or the Radial Menu ?
 
 
# Wouter Gilsing 2016-09-17 14:08
Hey Andrew.

I'm not to familiar with the Wacom Radial Menu nor the remote puck you mentioned. Would you like the hotbox to launch when clicking one of your Wacom buttons? Or do you want the option to have a 'launch hotbox' entry in your radial menu?

I'm still using my Intuos3 so I dont have access to any of those features, however, it was fairly easy to just bind the shortcut used for the hotbox as a keystroke to one of the wacoms physical buttons. A expected, the hotbox would now appear every time I push that button.
 
 
# kire timov 2016-09-27 09:07
Hey mate now when my script is working: http://www.nukepedia.com/python/misc/bugsbunny_motionblur_toggle_v1/finishdown?miv=2&mjv=1

i tried running it in the hotbox.
I couldn't make it work in there..

First i tried at the end of the script to call the main function.. than nothing happens (that was the case with other scripts i had where they had functions inside) - the code is not being called

Secondly , i removed the main function and run the code directly. (but i still have other functions that are being called from the main function)..The code acts strange, not doing what is expected.. on the contrary i tested the very same cody (copy/paste) from hotbox to the script edditor and run my script from there.. it works...
but not as expected in the hotbox. Why is that?
Is it because that hotbox cannot call functions like that?

Thanks
I am using v1 hotbox at work though, on CentOS
 
 
# Wouter Gilsing 2016-09-30 03:30
Just had a quick look. Since it's quite a big script, the cleanest/easies t way is to store the script somewhere on disk and to call a method from that module in the button (rather than copy/pasting the whole script into a button).

Seems to work fine for me:

Code:
import smartMotionblurSwitch
smartMotionblurSwitch.smartMotionblurSwitch()
 
 
# kire timov 2016-10-01 20:35
Quoting Wouter Gilsing:
Just had a quick look. Since it's quite a big script, the cleanest/easiest way is to store the script somewhere on disk and to call a method from that module in the button (rather than copy/pasting the whole script into a button).

Seems to work fine for me:
Code:
import smartMotionblurSwitch
smartMotionblurSwitch.smartMotionblurSwitch()


It works for me too, thanks. Just thought to let you know, whenever i try to call definitions directly from the hotbox they don't work, try something like getValue or something, and call that definition in the hotbox...

Btw is there anyway to customize the positions of the buttons?
 
 
# Juha Takabe 2016-09-28 07:29
Very cool!

Would be great to have some guidance how to create Backdrop around selected nodes as usual, but with custom Label on it with big font size and custom color. Some kind of backdrop preset to keep consistent colors for specific tasks.

Cheers!
 
 
# Wouter Gilsing 2016-09-28 14:06
Backdrop are a little bit special, as they use some extra scripts to make sure they end up wrapped nicely around your selection. That code is already set up though, and stored in a python module called 'nukescipts'.

This script creates a green backdrop, with the text 'Key' and a slightly bigger font.

Code:
import nukescripts

backdropNode = nukescripts.autoBackdrop()

backdropNode.knob('label').setValue('Key')
backdropNode.knob('note_font_size').setValue(50)
backdropNode.knob('tile_color').setValue(8323327)
 
 
# Serhat Baykal 2017-03-02 10:28
Hello,a really good job you have done with that tool !
But I have some trouble with 'import nukescripts'.

I try to make a script to get a command for launch a render through a console.

here my script ( it works through script editor ) :

###

import nukescripts

class MakeRenderLine(nukescripts.PythonPanel):
def __init__(self): nukescripts.Pyt honPanel.__init __(self, 'Render multi job')
self.SCRIPT = nuke.Root().nam e()
self.NUKEXE = nuke.env['Execu tablePath']

self.fRange = nuke.String_Kno b('fRange', 'Render Range', '%s-%s' % (nuke.root().fi rstFrame(), nuke.root().las tFrame())) self.addKnob(self.fRange)

def main(self):
nukeToRender = nuke.selectedNo de()['name'].ge tValue() first_frame = int(self.fRange.getValue().split('-')[0])
last_frame = int(self.fRange.getValue().split('-')[1])
cmd = r'"{0}" -t -V -x -F {1}-{2} -X {RN} {3}'.format(sel f.NUKEXE, first_frame, last_frame, self.SCRIPT, RN=nukeToRender)
print cmd nuke.message("\ n %s \n" % cmd)
def knobChanged(sel f, knob): if knob.name() == "OK": self.main()

MRL = MakeRenderLine()
MRL.showModalDialog()

###

When I try to use it I get :
Quote:
W_HOTBOX ERROR: Single/Write/Get render line - line 6: NameError: global name 'nukescripts' is not defined
 
 
# Wouter Gilsing 2017-03-08 10:38
Hi Serhat,

Would you mind emailing me the code? Looks like the indentation got lost, so its a bit hard to read at the moment.

Two things yoy could try in the mean time:

- save the script as a module, and try importing and calling that module from the hotbox button

- try added the 'import nukescript' statement right before you need it (instead of at the top of the script)
 
 
# Sri kanth 2016-10-03 10:06
Awesome! Really Great job!
 
 
# Vik Roni 2016-10-11 11:28
Could you please change the behavior of hotbox script so it could append its preferences in nuke's preference file instead of replacing contents of preference file on each startup?
 
 
# Wouter Gilsing 2016-10-11 11:31
Hi Vik,

The preference file shouldn't be replaced on every start up. Could you specify which version of Nuke and which OS you're running?
 
 
# Vik Roni 2016-10-13 09:52
Nuke 8.0v6, OS Windows 7
 
 
# Wouter Gilsing 2016-10-14 12:16
Yea, as stated earlier v8 is not supported, so I can't guarantee it will run without problem using that version.
 
 
# sridharan K 2016-10-24 08:52
Superrrr Awesome man! Wouter Gilsing
You've brought tool set thinking to scripts and menus. :D :lol:
 
 
# Tamás Szabó 2016-11-10 11:50
It's fantastic, very helpful and it's working! Thank You so much!
 
 
# jiwoong park 2016-11-16 14:11
How can I use in Group? 'nuke.selectedN odes' not working
 
 
# Wouter Gilsing 2016-11-16 14:17
Hey, I was actually working on that while you posted this comment! So yea, that's not yet working at the moment unfortunately.. . I hope to have it fixed for version 1.5.
 
 
+2 # Wouter Gilsing 2016-11-16 14:33
Nevermind, looks like it was easier than expected! So the fix will most likely make it into v1.4 which I will release later today.

EDIT:

v1.4 is available for download now!
 
 
# jiwoong park 2016-11-16 15:22
Wow! Awesome!! thank you
 
 
# PAUL FLANAGAN 2016-11-23 21:27
very cool! thank you.
 
 
# Sokratis Synitos 2016-12-01 11:23
Hello,

I am using NukeX 9.0v7 but I can't get the shortcut key to work.
I tried to change it as well but didn't get anything.
It also made File and Edit menu items switch places for some reason. I can see hotbox under edit menu
 
 
# Wouter Gilsing 2016-12-01 11:37
Hey Sokratis,

Could you specify which OS + version you're running and what keyboard layout you're using? Thanks
 
 
# Sokratis Synitos 2016-12-01 11:42
Hi Wouter,

I am on NukeX 9.0v7 on a CentOS 6.5 . My keyboard has a UK layout.

Thanks
 
 
# Wouter Gilsing 2016-12-01 11:46
Did you try changing the shortcut to something else and then restarting Nuke?
 
 
# Sokratis Synitos 2016-12-01 11:49
I did change to three different keys and restarted everytime but it didn't do anything
 
 
# Claus Steinmassl 2016-12-07 10:53
Hey Wouter,

I've got a strange problem: The buttons inside the hotbox manager are gone. See the screenshot here:
https://s11.postimg.org/ee9csc36r/hotbox.jpg

I was on vacation for one week. A freelancer used my machine in that time. Don't know what happend during that week. Since then I'm missing those buttons.... :(

I did a fresh install of the latest version, but that didn't help. Any ideas why this is happening?

I'm running NukeX10.0v5 on Win7.

Thanks!
 
 
# Wouter Gilsing 2016-12-07 11:00
Hey Claus,

this happens when the hotbox manager fails to locate the icon files. Have a look in the preferences (preferences - W_hotbox) and make sure the 'icon location'-knob is pointing to the folder containing the hotbox icons. By default this is set to '~/.nuke/icons/W_hotbox/'.

Hope that fixes it for you
 
 
# Claus Steinmassl 2016-12-07 11:15
Thanks very much, that solved the issue! :)

I think the freelancer hit the 'restore defaults' button on the nuke preferences. That caused another problem with hotbox: Nuke wouldn't start anymore due to an error in the prefs. See the screenshot:
https://s18.postimg.org/afwcya949/hotbox2.jpg

Therefore I deleted all hotbox prefes from the nuke preference file. That fixed the start up issue, since hotbox recreated the prefs. But I think I then forgot to set the icons path right agin, since it's located in a custom path here.

Thanks very much for your help! :)
 
 
# Wouter Gilsing 2016-12-07 11:59
Ah good catch. I wasnt aware of that error. I'll make sure that's fixed in the next version!

Thanks

EDIT:

This should be fixed in v1.5
 
 
# Daniel Mellitz 2016-12-07 20:32
Hot Box looks pretty cool but there's a bit of an issue related to the trigger key. Currently you have it set up to hold the key to make the menus appear and they disappear upon release.

The issue is that if you select an option that has a dialogue box with text entry you end up typing a bunch of tildas into the text field on selection because you are likely still holding in the tilda key.

Is there a reason not to have the option to make the hot key a toggle trigger rather than a hold do reveal? For me I think I'd rather tap the key and then make a selection and have it go away at that point.

I realize others would prefer the original behavior. Can you add that as a preference?

Dan
 
 
# Wouter Gilsing 2016-12-07 20:56
Hey Dan,

I can totally see why some people would prefer it that way. I'll look into it.

Thanks
 
 
# Wouter Gilsing 2016-12-12 12:18
Hey Dan,

I just made v1.5 available. This version has an option to launch the Hotbox with a single tap, rather than having to press and hold the hotkey.

You can switch to this mode by setting the 'Launch mode' knob in the preferences to 'Single Tap'.

Let me know how if you run into any problems!
 
 
# Daniel Mellitz 2016-12-13 01:58
Sweet! Thanks for that. I'll let you know if I see any issues.
 
 
# Tor Andreassen 2016-12-12 13:19
Hey Wouter,
Just started using nuke 10, so I can finally start using the hotbox.
Loving it, it saves so much time! I have a question though..

I was trying to find a way to change where the buttons show up in the hotbox menu, dragging them up or down in the list didn't seem to do it. is there a way to change the order of the buttons?

Thanks!
 
 
# Wouter Gilsing 2016-12-12 13:29
Hey Tor,
glad to hear that:D

Hmm yea, the drag/drop functionality definitively needs some work, I already spend quite a fair amount of time on it but it still only works occasionally, unfortunately. So that's on the to-do list.

In the mean time... Nasty work around: you could order your buttons by hand. Open the folder containing the button files (open an instance of the Hotbox and choose 'Open in Explorer/Finder /File Browser'). Then just rename the files as you like them to be ordered (001.py for the first button, 002.py for the second etc etc).

Cheers
 
 
# Tor Andreassen 2016-12-12 22:14
Hey Wouter,

Awesome, thanks for the update and workaround, I will give that a go,

Thanks
 
 
# Adrian Pueyo 2016-12-13 02:02
Hey Wouter,

Thanks for the updates, this gets better and better.

With the new Launch Mode dropdown I would still suggest a 'no-click mode' feature, where without any mouse click the script would be launched on tap release while hovering the mouse over a button; that would make navigation faster, especially on laptop touchpads. On that mode submenus could be accesed after a moment holding the mouse over a button or something. Also with that mode there wouldn't be any key or mouse button being pressed in the moment of the script execution which could be useful for some scripts.

Thanks!
Adrian
 
 
# Wouter Gilsing 2016-12-13 12:11
Good point, hadn't thought of that.Thanks for bringing it up, I'll look into it,

Cheers
 
 
# M Frank 2016-12-14 18:23
Hi Wouter,

Have you run into any issues calling outside modules/dialogs ? We are trying to call a module that pops open another dialog and it closes immediately. Not sure if there is a threading issue with how the class was written.

Thanks,
Mike
 
 
# Wouter Gilsing 2016-12-14 20:34
Hi Mike,

I've not experienced any problems with external modules nor dialogs. Actually, the 'Hotbox Manager' is quite a good example of a (Qt) dialog saved as an external module, called from a hotbox button.

which version of Nuke and what kind of OS? Also, what kind of panels are you using (Simple Nuke Panes, Python Panels or Qt Widgets)?

Obviously make sure to import the external modules at the top of the button-script.

If you want me to have a look (and you're allowed to), you can email me a sample script so I can help you troubleshoot.

Thanks
 
 
# sam alessandri 2016-12-19 12:19
Hi Wouter

Had this running fine..then did a system rebuild. Mac os 10/9/5.
I installed all good and can see the hotbox manager come up when i press it. I cant import my old library..or your one that is supplied...it just remains empty the library...any ideas?

ty
 
 
+1 # Wouter Gilsing 2016-12-19 12:26
Hi Sam,

That's unfortunate... Does Nuke print any error messages upon importing an archive?

Make sure your 'Hotbox location' knob in the preferences is pointing to the Hotbox folder containing the 'Single', 'Multiple' and 'All'-folders. By default this is set to '~/.nuke/W_hotbox/'.

If that's not the case and the archive is still not importing, you can restore the archive manually. Rename your archive file for somithing.hotbo x to something.tar and unpack the tar. This should give you three folders ('Single', 'Multiple' and 'All'). Place those in the W_hotbox folder and you should be good to go.
 
 
# sam alessandri 2016-12-21 07:33
Ill check all these and get back :) thanks for following up.
 
 
# sam alessandri 2016-12-21 11:35
Hi all up and running again :) thanks Wouter
 
 
# Fabian Jimenez 2017-01-13 20:00
Hi Wouter! Love your tool. It's an incredible time saver and I've been using it every day for the last month on production. Just need some advice...I'm trying create a shortcut in the hotbox "All" menu for popping the color picker("tile_co lor") window for any node. The shortcut is Ctrl+Shift+C and the code that works in the script editor is "nukescripts.co lor.nodes(). When adding to hotbox script editor...doesn' t seem to work. I get this error msg: W_HOTBOX ERROR: W_hotbox/ALL/Co lorPicker - line 2:
NameError: name 'nukescripts' is not defined. I have this same error w/other basic shortcuts as well from time to time. I'm a newbie when it comes to python so when you get a chance would love to know the way around this. THanks again for your awesome tool.
 
 
# Fabian Jimenez 2017-01-13 20:04
forgot to mention I'm currently on nuke10.0 v1 on windows
 
 
# jean-luc azzis 2017-01-13 21:08
you need to add an extra line at the beginning. so it should looks like that:

import nukescripts

nukescripts.color.nodes()
 
 
# Wouter Gilsing 2017-01-13 21:43
Hi Fabian, thanks for the compliments, glad you like it:)

As Jean-Luc just pointed out correctly you have to import the module first, whenever you use an external module (like nukescripts).

Cheers
 
 
# Fabian Jimenez 2017-01-13 23:33
Thanks guys! Worked like a charm ;)
 
 
# Peter Jansen 2017-01-18 04:08
I love this! Works perfectly here, just spent an hour playing with it and writing little scripts for it.

Coming from Maya I was wondering if the Maya interaction could be replicated closer? I never use right click in the node graph, so I'd happily replace the node menu that comes up with the hotbox. And ideally a mode where the action is taken upon release of the key/right click.

Cheers
 
 
+1 # Wouter Gilsing 2017-01-18 07:12
Hi Peter, thanks!:)

I actually got the 'execute without click'-thing working, so that will definitely make it's way into the next version.

As for the right-click, that's currently not possible unfortunately. Alternatively, you can map the shortcut to the spacebar though, to mimic Maya closer (use 'space' in the shortcut entry of the preferences)?

Cheers
 
 
+3 # Paul Boots 2017-02-04 14:32
Wow Wouter!
Just discovered you made this, really cool
Go Wouter Go!
 
 
# Wouter Gilsing 2017-02-05 18:31
Haha, thanks Paul! Good to see you here btw :-)
 
 
# Claus Steinmassl 2017-02-15 14:20
Hey Wouter,

I would like to request a feature for something that I just came across:
I have a script, which I would like to appear whenever I have a ParticleEmitter and ANY other class selected. Right now I can't do this, since I must specify the other classes. So I would like to do something like ParticleEmitter -* instead of ParticleEmitter -Class1-Class2 etc.
When I tried it that way, an error occured saying the syntax for the filename was wrong.
Would be great to have this option! :)

PS: I know I can have scripts appear for EVERY class, but I would like to limit this so they only appear when those classes named are within the selection.
 
 
# Wouter Gilsing 2017-02-15 14:26
Hi Claus,

I'm actually working on something like this! So I hope to get this out in the next update (it's taking a bit longer this time, but 1.6 will be a pretty big upgrade).

Cheers
 
 
# Claus Steinmassl 2017-02-15 15:42
Awesome! Looking forward to the next version! :)
 
 
# Andrew Mumford 2017-02-15 20:37
Hi Wouter thx againg for this awesome tool,

I'm stuck in the situation where,

I have a 4K UHD Monitor = Good
I'm using Nuke which relies on an old versio of QT = Bad

Consequently I'm upping my UI font size so I don't go blind from suinting in the first hour of the day and a lot of W_Hotbox's font labels get cutoff.

Is there a way I can "tweak" W_Hotbox to either/or scale the default Button size or the font size ?

Thx again
 
 
# Wouter Gilsing 2017-02-15 21:04
Hi Andrew,

There's an option in Nuke's preferences that allows you to change the font size of the hotbox buttons ('hotboxFontSiz e'). V1.6 will feature a similar function for the manager's scripteditor.

Hope that helps!
 
 
# Sven Akelian 2017-02-20 14:09
Really great idea.
For some reason I'm having errors while making categories where it deletes other buttons.
Maybe it's because I'm trying to style them HTML way (which works). Do you think that is the reason I'm having strange behaviour ? What would you suggest to style menu items then (mainly adding text colors)?

Thanks a lot
 
 
# Wouter Gilsing 2017-02-20 14:14
Hi Sven,

Would you be able to write a little description of which buttons you have, what there styling is, and when exactly the error occures? That way I can try to replicate and fix it. Also, which version of Nuke + operating system are you using?

If you feel it's easier, you could drop me an email as well.

Cheers
 
 
# Sven Akelian 2017-02-20 14:20
Edti>W_Hotbox>Repair
Seems to fix the problem
 
 
# Wouter Gilsing 2017-02-20 15:42
Haha, great to hear that repair function actually got rid of a problem:)
 
 
# Siddharth Saxena 2017-02-26 08:12
Hey Wouter,

Thanks for the updates, this gets better and better.

Can u please tell me how can i write a python code for all the selected read nodes to be changed to "start at 1001"
 
 
+1 # Wouter Gilsing 2017-02-26 08:24
Hi Siddharth,

In order to change the read node to start on frame 1001, you will have to change two knobs:

- frame_mode: the dropdown that should be changed from its default 'Expression' to 'Start at'
- frame: the text field next to the dropwdown, that should be set to 1001. (Note that its a textfield, so it requires a string, not an integer. Some make sure to put some ' ' around the framenumber)

Since you want the to affect all the selected reads nodes (rather than just one) you need to put it in a loop:

for node in nuke.selectedNodes():
----node.knob('frame_mode').setValue('start at')
----node.knob('frame').setValue('1001')

(Hmm, looks like the indentation was stripped from my comment. So I used - (instead of spaces). Make sure the replace those in order to get the code working)

Simply add that as a button to your read class, and you should be good to go!

Hope that helped
 
 
# Siddharth Saxena 2017-02-26 08:52
It Worked, many many thanks for ur help.
In addition to this please tell me what if i have to write if i want nuke to ask for which frame no. i want to start at.

Thanks. :-)
 
 
+1 # Wouter Gilsing 2017-02-26 09:12
You could use nuke.getInput() to generate a popup menu asking for a value.

In that case the code would be something like this:

#ask for start frame
startFrame = nuke.getInput(' Start at frame...')

#set knobs
if startFrame:
----for node in nuke.selectedNodes():
--------node.knob('frame_mode').setValue('start at')
--------node.knob('frame').setValue(startFrame)


Note that, if keep pressing the hotbox shortcut, this might float the textfield of the popup. I'm working on that.
 
 
# Tor Andreassen 2017-04-18 03:20
Hi Wouter,

Love this tool, but I've come across a potential bug that makes it hard to add buttons.

Running nuke on linux, Nuke version: 10.0v4

The buttons in the hotbox manager (the ones allow you to add more custom buttons), the plus icon button and all that is gone. there should be 3 icons on the left side of the class list, and 6 buttons on the right side of that. They are not present anymore.

I tried removing the tool to reinstall it, but the same issue is still present.. Have you had this problem? or could you possibly run a test on that nuke version to see if you're getting the same issue? Would appreciate it if you had some time to look into that. Thanks again for the awesome work you're sharing.
 
 
# Wouter Gilsing 2017-04-18 06:39
Hi Tor,

Sounds like the manager is unable to find the icons. Can you double check that the 'icons location' (Preferences/Ot her/W_hotbox) is pointing to the correct folder, and that the icons are actually present?

Have you tried clearing the (hotbox related) preferences? There's a button in the preferences labeled 'delete preferences'. If you click that, exit the preferences panel by clicking the 'cancel' button and than restarting Nuke that should reset the hotbox related preferences.

This will reset to default, so make sure your 'icon location' knob is pointing to the right folder after restarting again.

Hope that solved it!
 
 
# Tor Andreassen 2017-04-18 09:58
Hah, thanks, that was it. sorry for bothering you with such a simple fix, should have checked that first.

Thanks Wouter!
 
 
# Wouter Gilsing 2017-04-18 13:15
Hehe, no worries, I quite prefer the simpler fixes;)
 
 
# Simon Lawson 2017-04-27 12:30
Hi Wouter
Hotbox is a great tool, node contextual commands is very innovative and useful.
Any news on when your going to release a new iteration and what changes to expect?
I personally think Maya has the best pop-up menu's in terms of set-up and functionality, any chance the w-hotbox is going to move closer towards it?
 
 
# Wouter Gilsing 2017-04-27 13:36
Hi Simon,

Thanks for the kind words, glad you like it:)

I'm currently finishing up 1.6 (took me a lot longer than expected, blame crunch time at work I guess haha). I'm pretty confident to say this will be the biggest update since the release though. I'm currently in the progress of documenting all the changes and updating the User Guide.

Some of it's features:

- Color swatches in the manager to colorize buttons/text.
- Templates (Quickly store/access template code).
- Auto save.
- Tooltips in the manager.
- Fixed transparency issues on Linux.
- Rewrote several parts of the core to improve stability.
- Several bugs/tiding up.
- Several things I'm currently forgetting (dont have my todo list in front of me atm)

For 1.7 I'm planning to mainly focus on making the tool compatible with Nuke11/Qt5 (fun times, yay). Besides that I've been looking into 'wildcards' : improving the way you can assign buttons to a Group node by name (I improved this already a lot in v1.6 when it comes to the 'multiple'-sect ion when having a selection of different groups and nodes selected). But it could improved a bit more;)

If you could provide me with some concrete functionalities you like about the Maya hotbox and feel are missing in W_hotbox, I'm of course very willing to look into that!

Hope that answered your question!

Oh about when to expect 1.6: Probably next week, maybe the week after that (definitely May!). As I said, I'm just updating the User Guide and it should be good to go.
 
 
# Simon Lawson 2017-05-04 13:11
Hi
Colorized buttons sounds like a great addition, I think that could be a very effective feature.

What do I like about Maya's Hotbox?
Firstly it is quite easy to set up and gives a lot of control over how exactly you want it to function. That said it still has it's limitations.
I like the circular style of Maya's Hotbox and find the quick swiping motion to be faster then using a large amount of keyboard shortcuts. Say you use 10 to 20 different commands during a session, it's unlikely your going to be able to hit the right key without looking down at the keyboard which is ultimately inefficient, hence why Hotboxes can give you the fastest and most enjoyable workflow.
Maya lets you assign a total of eight commands to the circular function, with the option of sub-circular menu's as well as having a listed menu below.
The circular menu is fast to use but limits you to eight commands, for some tasks this may work fine but others it certainly wouldn't. One of the few ways that Maya's Hotbox could be improved upon would be by having the ability to add more then just one command to one of the eight available spaces without having to go into a sub-menu.
So a section (floating menu) could hold any number of commands related to each other. A section could hold your favourite Keying nodes, while the next section holds your favourite Color Correction nodes and adjustments. The different sections could have a different color assigned to them to catch the eye, Green-Keying, Blue-Color Correction, Transforms-Purp le and so on.
Basically a circular hotbox can be as big or as little as you choose, one command or ten assigned to each section.

Another nice feature Maya has is the ability to have multiple Hotbox menu's. So you can have a menu for your Index finger, and a different one for your Middle finger. The Middle takes the A key, while the Index takes the X key, this gives you a natural hand position while easy access to Alt, Ctrl, Shift without having to look down at the keyboard ever. The A key to control widely used functions and Nodes, while the X key can be task specific, this is where Node contextual commands could come into play, or an option to have the ability to quickly assign a custom hotbox specific to the task you are working on. For example a roto hotbox for the viewer area could speed up workflow(if someone wanted to roto in Nuke that is!!!). :-*

As far as things that could be easily be changed, let the Left (Reveal in Explorer) and Right (Hotbox Manager) side buttons be available to have assignments of ones choice, to make more of the space for regularly used commands.
Maybe also the ability to have "All" commands placed above the center of the menu.

Hope all this makes sense?
 
 
# Wouter Gilsing 2017-05-05 15:59
Awesome, thanks for taking the time to write down that reply! Will definitely keep the things you mentioned in mind for future releases!
 
 
# Thomas Vu 2017-05-17 06:52
is possible to add shortcut key to active some custom button ?
 
 
# Wouter Gilsing 2017-05-17 08:05
You mean to invoke a button by pushing a shortcut while having the hotbox open?
 
 
# Thomas Vu 2017-05-17 13:10
close, i mean while selecting the node. but combine with hotbox opening are also great.
 
 
# Marc Mantei 2017-05-23 08:38
Thanks for sharing! I just replaced my own little hotbox setuo with your one and customized on the go. keep it up! best regards. Marc :)
 
 
# Wouter Gilsing 2017-05-23 13:04
Thanks, glad you like it! Any features you're missing compared to your own version?
 
 
# Gautama Murcho 2017-05-31 22:13
Hi Wouter,

I just want to say thank you for writing this. I have used W_hotbox since you released it here, and can't imagine using Nuke without it now - especially since I can easily turn any script that pops into my head into a button. Great work!

-G
 
 
# Wouter Gilsing 2017-06-01 09:00
Hi Gautama,

That's awesome to hear:)

Thanks!
 
 
# Matthieu Cadet 2017-06-22 10:01
Hi Wouter!

Have you planned to add support for PySide2 in your awesome W_Hotbox ? :)

thanks!
 
 
# Wouter Gilsing 2017-06-22 10:11
Hi Matthieu,

Yep, just got a version up and running with Nuke 11, so expect an update soon!
 
 
# Matthieu Cadet 2017-06-22 10:23
:lol: Yes thanks!
 
 
# Wouter Gilsing 2017-06-26 07:26
Just uploaded v1.7!
 
 
# Matthieu Cadet 2017-06-26 08:02
Thanks! but it's not working :P

I see the menu of W_hotbox, but when I trigger the shortcut to open the tools I only see this in the terminal window and the tool UI is not showing :-| :

QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QPainter::begin: Paint device returned engine == 0, type: 1
QPainter::save: Painter not active
QPainter::translate: Painter not active
QPainter::setClipRect: Painter not active
QPainter::save: Painter not active
QPainter::pen: Painter not active
QPainter::setPen: Painter not active
QPainter::pen: Painter not active
QPainter::setPen: Painter not active
QPainter::pen: Painter not active
QPainter::setPen: Painter not active
QPainter::setPen: Painter not active
QPainter::pen: Painter not active
QPainter::setPen: Painter not active
QPainter::pen: Painter not active
QPainter::setPen: Painter not active
QPainter::setPen: Painter not active
QPainter::setPen: Painter not active
QPainter::restore: Unbalanced save/restore
QPainter::restore: Unbalanced save/restore
 
 
# Wouter Gilsing 2017-06-26 08:14
Ah, great... Thanks for sending the error messages though. Which OS are you using? As for me it worked just fine on OSX.
 
 
# Matthieu Cadet 2017-06-26 08:35
I'm on Linux Fedora 21, tested with the last beta version of Nuke 11
 
 
# Wouter Gilsing 2017-06-26 08:46
Thanks, I'll jump on it. For the time being you might wanna try to replace line 82 with the following:

if operatingSystem not in ['Darwin','Wind ows'] and nuke.NUKE_VERSI ON_MAJOR > 10:

This will disable the transparency on Nuke 11 Linux. It will probably look ugly, but a least it will stop throwing errors. (Or I hope so at least... All hypothetical)

Worth a try
 
 
# Matthieu Cadet 2017-06-27 09:26
Mmm no, changing this line don't fix the problem, same error, and no UI showing :(
 
 
# Erik Johansson 2017-08-11 08:18
Same here on Centos 7. Probably Qt5 related but can be both W_hotbox and Nuke11 that is the cause.
 
 
# Wouter Gilsing 2017-08-11 08:23
Hi Erik,

It's a Qt5 (on Linux) thing indeed. This is definitely the no.1 on the priority list, I just haven't had much time to look into the matter as of just yet unfortunately.. . Will update asap.
 
 
# Wouter Gilsing 2017-08-20 13:27
Hi Eric and Matthieu,

Ive finally managed to find some time and a copy of Nuke11 on linux to do some test with.

Althoguh, I'ven't produced a proper fix yet, I found a quick work around.

Turns out my previous comment was pretty close, except for a typo...

replace line 82 with the following should work:

if operatingSystem not in ['Darwin','Wind ows'] and nuke.NUKE_VERSI ON_MAJOR < 11:

As stated before, this will introduce some transparency problems. However, the hotbox will (or should) work fine otherwise.

Hopefully this workaround will suffice for now.

Cheers
 
 
# Erik Johansson 2017-08-29 15:19
Works here!

Thanks!
 
 
# Matthieu Cadet 2017-06-30 12:46
Hi Wouter!

I think you should refactor your code related to Nuke Preferences save/load/delet e,I have some problem with my own custom preferences knob and yours.
I think its because you are writing directly to the preference file ) instead of let Nuke do this job.

Maybe by following this example is enough for refactoring:

https://github.com/NateScarlet/My-Personal-Scripts/blob/782981ad10bf1d1164966761f4c3104baaa06916/Comp/nuke/wlf/py/wlf/pref.py

or

https://github.com/robmoggach/python-dotnuke/blob/master/mynk/prefs.py

The problem I've seen is that my custom pref knobs suddenly appears in your nuke.Tab_Knob(' hotboxLabel','W _hotbox') :(
 
 
# Wouter Gilsing 2017-06-30 13:22
Hi Matthieu,

Thanks for providing those links, always nice when people think along and to have some sort of starting point. :)

By looking quickly at their code, it seems like they use the same method as I currently do. However, after having added the knobs to the preferences panel, I indeed force write the updated preferences to the preference file (usually this 'writing to file' happens when you open and close the preferences panel).

If I wouldn't do this, nothing will get saved unless the user manually opens and closes the preferences panel (So in order to 'let Nuke do the job', the user has to 'do the job' first) ;) .

Ten, upon start-up the hotbox checks whether the necessary knobs are already presents in order to decide whether or not it's relevant to add them.

That being said, the hotbox preferences should definitely not mixup with any custom knobs. So I'll look into that! Thanks for reporting the issue:)

The first hotbox knob that gets added to the preferences should always be a tabknob, in order to separate the knobs from any custom knobs you already might have.

So I assume your custom knob appears at the end of the hotbox tab? If that is indeed the case so, you might need to add a new tabknob yourself first, in order to separate the knobs from mixing up.

I'll look into the possibility of closing the tab from the bottom anyway though.

Thanks

Wouter
 
 
# Juha Takabe 2017-07-13 19:46
As some have already mentioned, I also can't get shortcut to work. I have tested different keys + restart. I'm on latest macOS and NukeSrudio/X 10.5v5

Best,
Juha
 
 
# Wouter Gilsing 2017-07-13 19:51
Hi Juha,

What kind of keyboard layout are you using?
 
 
# Juha Takabe 2017-07-13 20:05
I'm using Finnish keyboard.
 
 
# Juha Takabe 2017-07-17 13:04
Not sure what happened, but now it's working just fine! Sorry for a false alarm.
 
 
# Wouter Gilsing 2017-07-17 13:06
Ah great, glad to hear that
 
 
# Anais Torreblanca 2017-08-11 14:45
Thank you Wouter! It's so helpful. Just one question, will it work for Nuke 11 on Linux?

Thanks a lot
 
 
# Wouter Gilsing 2017-08-11 15:09
Hi Anais,

Currently it's not working on Nuke 11 on linux (yet) (Windows and OSX are fine though).

This is definitely the no.1 on the priority list, I just haven't had much time to look into the matter as of just yet unfortunately.. . However, I'll try to look into and update asap.

Cheers
 
 
# Anais Torreblanca 2017-08-14 12:41
Thanks for the info. I will use Nuke 11 on Windows and Nuke 10 on Linux. :)
 
 
# Wouter Gilsing 2017-08-20 13:29
Hi Anais,

As posted in another comment, I've found a quick work around to get the hotbox up and running on linux Nuke 11.

replace line 82 of W_hotbox.py with the following:

if operatingSystem not in ['Darwin','Wind ows'] and nuke.NUKE_VERSI ON_MAJOR < 11:

This will introduce some transparence problems, but the hotbox will work as expected.

I'll upload a new version once I've found a proper fix.

Cheers
 
 
# Anais Torreblanca 2017-08-20 13:37
Thank you so much, I will try it :)

Cheers
 
 
# Anais Torreblanca 2017-09-06 15:32
Hi Wouder, Thank you so much!

It works perfectly beside the transparency.
 
 
# karthick efx 2017-08-22 18:32
any video for this Installation
 
 
# Wouter Gilsing 2017-08-22 18:36
The download ships with a pdf with a detailed step by step description of how to install the tool.

At what point did you get stuck?
 
 
# karthick efx 2017-08-22 18:45
first point
i paste in nuke user W_hotbox.py & W_hotboxManager.py

Second point
already in nuke user menu.py that i edit & paste this
import W_hotbox, W_hotboxManager

3 point i paste icons with help of downloads

4 point nuke open but some error coming ?
 
 
# Wouter Gilsing 2017-08-22 18:47
Whats the error?
 
 
# karthick efx 2017-08-22 18:53
thanks now working
i restart my system than i open nuke working
 
 
# karthick efx 2017-08-22 19:00
any preset option
 
 
# Wouter Gilsing 2017-08-22 19:05
Not sure what you mean. Preset buttons?

If you open the hotbox manager (edit - W_hotbox - Open Hotbox Manager) and click 'import Archive', then browse to 'buttonBundle.h otbox' you get a bunch of useful example buttons.
 
 
# karthick efx 2017-08-22 19:32
super tool this its very help for us

hotbox i s great

any Templates
single
Multiple
All

its great help us
 
 
# karthick efx 2017-08-22 19:40
tks
 
 
# Adrien Valembois 2017-09-03 09:41
Hello Wouter

Thank you for this useful script, it is a real time saver.

I have just one issue : I work with an azerty keyboard and the key ' ` ' is not same, it's this one ' ² ' instead. I'm use to this key to call your script but the "excute button without click" option doesn't work. Nothing happens when I release the key, so I have to click on a button and click outside the hotbox to close it.

W_hotbox.py:230 : UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal
if event.text() == shortcut:
W_hotbox.py:241: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal
if event.text() == shortcut:

if I change the shortcut or if I use my keyboard in qwerty mode it work properly, but I would love to use this damn key in azerty
the 'single tap' and 'close on button click' work also

is there any solution ?
 
 
# Wouter Gilsing 2017-09-07 07:16
Hi Adrien,

thanks for reporting! I'll look into this when I've got some time on my hands.

cheers
 
 
# Pranav Gangapurkar 2017-09-05 10:19
Hi,
This is a great tool and I am using it for a while.
But nuke is giving some error today and is not opening.

Traceback (most recent call last):
File "/u/xyz/.nuke/m enu.py", line 3, in
import W_hotbox, W_hotboxManager
File "/u/xyz/.nuke/p ython/W_hotbox. py", line 1194, in
if hotboxLocationP ath[-1] != '/':
IndexError: string index out of range


It was working fine before. I am almost addicted to using this . Any help is appreciated. Thanks.
 
 
+1 # Wouter Gilsing 2017-09-07 07:19
Hi Pranav,

Sounds like a problem caused by the path you defined (I assume it's empty). Make sure the 'location' knb in the preferences (Nuke preferences - W_hotbox) is pointing to a valid folder.

Hope that helps!
 
 
# Pranav Gangapurkar 2017-09-07 11:05
Thanks Wouter. That indeed was the problem. It started working after pointing to the correct path. Cheers.
 
 
# Michael De Caria 2017-10-16 23:19
Hey Wouter,

Long time user of hotbox. small thing.

line 729 of W_hotbox.py which runs self.invokeButton()

If invoking the command raises an exception the undo().end() is never called causing your undo stack to be neverending and problematic.

On my end I've locally patched it to try: except: finally:

The finally always runs the undo().end()

Cheers,
Michael
 
 
# Wouter Gilsing 2017-10-20 20:34
Thanks for the headsup!
 

You have no rights to post comments

We have 2501 guests and 134 members online