- User Since
- Mar 28 2006, 9:01 AM (686 w, 6 d)
Feb 19 2017
Great, thanks for improving the consistency! I remember Ton mentioning the importance of ui consistency in his 2015 conference keynote, it is appreciated.
Feb 18 2017
Let's forget about 2.49, it seems to be distracting to the conversation instead of helping.
Feb 8 2017
Brecht, thank you for your patience I'm back home now.
Feb 1 2017
I am traveling without my laptop until Tuesday but I can assure you the behavior is different with mouse than trackpad. The mouse functions as expected.
FWIW it works in2.49b. I have not tried latest build from buildbot. I am traveling until Tue so I will try it next week. Since there is a work around this is low priority but I am happy to help resolve it upon return, just let me know how I can assist. BTW I agree that it seems reasonable to expect either approach to work.
It works as described in the manual when done with a mouse. It does not work when using a trackpad.
Did you see my video and my subsequent notes? It works if I use a MOUSE, but it does NOT work properly with the MacBook Pro's TRACKPAD.
Jan 31 2017
On a whim I connected a mouse up to my laptop. Using a mouse, the view locking works as expected. Using the trackpad the view locking does not work in 2.78a (but does work in 2.49b).
Attached is a movie showing the behavior.
Please note, in my steps the object is never moved, on the view is translated. Thus not locked according to manual or previous version of blender.
Feb 26 2014
I'll have to find the example and try to attach again, not sure why it didn't stick before.
Jan 9 2014
Dec 26 2013
Cool! I didn't know that @lower case (lowercase) (or I forgot since it appears to be there in 2.49b as well), is there a place in the UI where you could see the amount of kerning? I'm sorry, we're deviating from the topic a little. Feel free to email me if you want to take it offline: firstname.lastname@example.org
Dec 25 2013
That sounds great Campbell! The functionality is useful and it appears all agree that it would be logical to migrate to an addon at some point. It makes sense to keep the functionality in Blender until the APIs are extended to provide a way to allow the creation of an addon.
Dec 23 2013
I'm not sure why one would remove a longstanding useful feature without replacing it, is it the underlying code problematic, preventing Blender to grow in a particular area?
I agree, nobody wants bloat, I was not making an argument for a core feature. It'd be fine if it was migrated to an addon. I'm not sure what's involved with that.
The tutorial example was not intended to as an argument for or against it being a core feature or an addon. Campbell said in his note that he had to refer to source to figure out its functionality, I happened to have released the video yesterday demonstrating its usage (we recorded it last week, totally coincidental that Campbell posted this yesterday unless he was looking into it because someone saw my video and had questions), I thought that might be helpful for him to see it.
Even with the limitation of ASCII only, this is a great feature! The ASCII only is not a big problem when working with small character sets because the whole point of the feature is to substitute an object for a character. Not only is this feature good for typography but also for design to easily create and edit patterns of objects in Blender. Coincidentally, I released a video yesterday showing the object font feature:
John R. Nyquist