Thanks for replying, Peter. Here are some responses…
> On May 29, 2015, at 10:08 AM, Peter Crossley <[email protected]> > wrote: > > Hi Rich, > > A few comments below that might help you understand it a little more: > > On 29/05/2015 14:51, Rich Bobo wrote: >> Hi, >> >> Does anyone else find the new Text node to be completely unintuitive? Up is >> down, left is right, pixel box and layout sizes are backwards. I can’t seem >> to get anything to work the way I think it should! If I want to justify >> left, it goes to the right. WTF?!? > > There are two ways you can use the text node - you can create your own bbox > and limit the text area to this (as with the old text node), or you can free > type - where the bounding box automatically resizes to the text you are > typing. The justify controls have different behaviour depending on the > context. I suspect this is what's causing you confusion. > > When you've defined your own bbox, justify will (as you would expect) justify > the text within that box. My guess is that you're in free type mode. In this > case, you are justifying the text relative to the position where you placed > your first character. If I free type a short sentence, it starts at the left of the screen, as expected. Then I select justify right and the whole sentence moves offscreen to the left. Not what I expected. If I choose bottom, it all goes up and off the screen. In my mind, in free type mode, I would expect the bounding box to default to the image raster size and then changing any justify settings would keep the text on the screen. In other words, if I haven’t defined a bounding box, I would expect the visible image boundaries to be the box. > > So imaging you set justify to right before you started typing, then click in > the viewer somewhere and begin typing. Each new character will cause the > characters to the left of it to be moved to the left. If, after typing > several characters, you click left justify, all the text will move to the > right so that the left-most character is at the first position. Essentially > you are justifying the text bbox in this mode. Does that make sense? > > Note that you can switch from freetype mode to bbox mode either by initially > dragging out a box at the start, or by resizing your text box at any time. If I drag the box - which toggles out of free type mode - then the justify settings do exactly what I would expect. So, the key to avoiding all the non-intuitive and wonky behavior seems to be initializing the bounding box and getting it out of free type mode… Personally, I would love it if there was a preference default to just use the image size as a bounding box, until you change it. The current behavior seems like it adds an additional step and only confuses the new (and old) user. What was the thinking behind the way the free type mode works…? I asked one of my nearby co-workers what he thought of the new Text node. He said he hated it and had finally decided to do all of his titles in After Effects! So, I’m guessing that having to set the bounding box first, to get predictable justification behavior sets a very high barrier for usability! (8^\ > >> And, the fact that it remains active any time it’s open — so you >> inadvertently type characters when using hotkeys drives me bonkers! > > Yes, there is a long standing feature request raised for this. One idea, for > example, is that we use a hotkey (e.g. esc) to toggle between text entry and > non text entry mode. Would you find something like this less frustrating? That would probably help. As it is, I have to remember to close and open the property panel to avoid the problem. I’m not sure what else could be done, though. The way the new Text node works kind of breaks the Nuke UI paradigm that we’ve gotten used to… > > Hope that helps. Yes, I think that knowing that I have to set the bounding box first, to get things to work “right”, is a huge tip! ;^) Thanks! Rich > > Peter. > >> >> Guess I’ll have to RTFM to figure out how it works… Does anyone think this >> is an improvement? Am I the only one having trouble figuring it out? ~(8^P >> >> >> Rich >> >> >> Rich Bobo >> Senior VFX Compositor >> Armstrong White >> Email: [email protected] <mailto:[email protected]> >> http://armstrong-white.com/ <http://armstrong-white.com/> >> >> Email: [email protected] <mailto:[email protected]> >> Mobile: (248) 840-2665 >> Web: http://richbobo.com/ <http://richbobo.com/> >> >> >> _______________________________________________ >> Nuke-users mailing list >> [email protected] >> <mailto:[email protected]>, >> http://forums.thefoundry.co.uk/ <http://forums.thefoundry.co.uk/> >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >> <http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users> > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
