tag:blogger.com,1999:blog-1978356510587112308.post8242921873629845642..comments2024-03-29T20:04:17.419+13:00Comments on Aligorith's Lair: GSoC11 - Playing with the mute/visibility toggles...Unknownnoreply@blogger.comBlogger10125tag:blogger.com,1999:blog-1978356510587112308.post-18003175380153770442011-07-12T18:44:02.115+12:002011-07-12T18:44:02.115+12:00Antti: turn on the "Show Sliders" option...Antti: turn on the "Show Sliders" optionAligorithhttps://www.blogger.com/profile/11379156223939123157noreply@blogger.comtag:blogger.com,1999:blog-1978356510587112308.post-31081637528678681852011-07-12T17:29:12.760+12:002011-07-12T17:29:12.760+12:00Hi!
Thanks for all the great improvements done to...Hi!<br /><br />Thanks for all the great improvements done to the Blender animation system.<br /><br />I have a small feature request that would really help in some situations:<br /><br />When a scene has hundreds of keyframes, it is often better to work in dopesheet since the overview there is less cluttered.<br /><br />What would be really awesome would be the ability to edit the keyframe values directly in the dopesheet, simply by clicking on a keyframe. If someone uses After Effects, then you might know how clicking on a keyframe brings up a small dialogue box displaying its value and you can edit the value in that same box.<br /><br />At the moment I have about 50 animated lamps in my scene and I realize that I need to change the end keyframe value of them all to be brighter. Currently I have to position the playhead on the exact keyframe location in order to edit it (without going to graph editor) and this is a major PITA. It would be so nice if I could just double-click on a keyframe to change its value regardles of my current playhead position.Anttihttps://www.blogger.com/profile/10359332592653081168noreply@blogger.comtag:blogger.com,1999:blog-1978356510587112308.post-54296683899097358542011-06-30T23:53:49.204+12:002011-06-30T23:53:49.204+12:00Personally I found 2 to be the most intuitive. Ev...Personally I found 2 to be the most intuitive. Even if the colour box can't be underneath the eye.<br /><br />As for the NLA, I'm with Matt in that those ActAction bits can be removed. I understand they're used to show the non-NLA data, but can't that be pushed up to the same level as the Object itself?Mikehttp://www.watchmike.canoreply@blogger.comtag:blogger.com,1999:blog-1978356510587112308.post-41604411881877588682011-06-30T22:55:17.196+12:002011-06-30T22:55:17.196+12:00Nice one, that was quick!Nice one, that was quick!Matthttp://mke3.netnoreply@blogger.comtag:blogger.com,1999:blog-1978356510587112308.post-51625016226045581032011-06-30T21:53:49.249+12:002011-06-30T21:53:49.249+12:00Here's what i thought would be simpler. For vi...Here's what i thought would be simpler. For visibility, remove the checkbox, and let user decide which one is visible by simply selecting it. they can use 'a' shortcut for viewing all, ctrl+click for multiple selection, using 'b' shortcut for blocking it, and just deselect it to hide it.. So we don't have to select it, and then press 'v' to make it visible anymore. it's just too much clicking at the moment.<br /><br />for mute and lock button, i like it just the way it is right now :)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1978356510587112308.post-25972390349200666002011-06-30T13:20:50.506+12:002011-06-30T13:20:50.506+12:00Matt: Thanks. Taken into account and committed twe...Matt: Thanks. Taken into account and committed tweaks :)<br /><br />Glenn: I've been thinking over that option too. It's just a bit more work (doing pixel-art and dealing with some difficult to merge files - i.e. icon file).Aligorithhttps://www.blogger.com/profile/11379156223939123157noreply@blogger.comtag:blogger.com,1999:blog-1978356510587112308.post-74264201277569581842011-06-30T11:42:37.926+12:002011-06-30T11:42:37.926+12:00You know a mute icon in most music programs (and a...You know a mute icon in most music programs (and almost everything else) is a speaker with a strikethrough. I wonder if that would be better than a tick, so we would have 3 icons that make visual sense, an eye for visible, a speaker for mute and a lock for lock.<br /><br />~GlennGlenn Melenhorsthttps://www.blogger.com/profile/01783245998834421413noreply@blogger.comtag:blogger.com,1999:blog-1978356510587112308.post-43245255825784816092011-06-30T11:01:23.162+12:002011-06-30T11:01:23.162+12:00I like option 2 :)I like option 2 :)Dread Knighthttps://www.blogger.com/profile/08142529873301282454noreply@blogger.comtag:blogger.com,1999:blog-1978356510587112308.post-89172227076542622022011-06-30T10:57:56.264+12:002011-06-30T10:57:56.264+12:00Looking at Gimp's layer dialogue the checkable...Looking at Gimp's layer dialogue the checkable icons are on the left- not saying this is better, but more standard. Considering Photoshop has layer groups, Gimp 2.7 may? it may be a good place to look as well. Glad to see the eye will represent visibility finally!-jayhttps://www.blogger.com/profile/18355102386904975480noreply@blogger.comtag:blogger.com,1999:blog-1978356510587112308.post-75480130152868084562011-06-30T10:29:19.751+12:002011-06-30T10:29:19.751+12:00One thing that might help readability/clutter here...One thing that might help readability/clutter here is to remove the names of the id blocks from the name of the fcurve - you can see this above where it says (world), (world), (world), and (cube), (cube), (cube).<br /><br />This is pretty useless information since you can see what the object is right about it. Perhaps if it's a situation where fcurves are coming from multiple bits of data (or non-ID data, like the subsurf) it might be handy but in most cases it's not, and just adds to the visual mess. It might be good to try removing this text in those cases (and/or putting it in a tooltip).<br /><br />While you're at it, I'd suggest taking a look at the naming in the NLA editor too - I think you could easily get rid of those superflous 'ActAction' bits and the < > as well. Those actions are easily identified by the action icon and line colour, and don't need that text. This would also make it much easier to scan-read: in left-to-right languages people generally scan through lists of text with the eye scanning down the left edge of the list.<br /><br />cheersMatthttp://mke3.netnoreply@blogger.com