Hi all,
I'd also like to share my experiences as a user learning the new Python API. I
had the same difficulties as Damir, finding where is what in the greater
context of the hierarchy.
I'll try to explain how I see it:
I believe there are at least two kinds of people who learn in a different
> We can have both menu items or a for submenu for Relative/Full data paths
> (ok by me, annoying it takes more room in the menu though).
Maybe always copy full path, on CTRL+V paste relative path and on
CTRL+SHIFT+V (paste special?) paste full path?
> As for docs, would be good if you could be m
> shift-alt drag button into text editor or console -> full path
> shift-alt drag button into driver area -> appropriately truncated path
Alternatively, we could have it always copy the full path, but when
pasting (full over-write) into the driver path, it truncates it up to
the matching datablock
We can have both menu items or a for submenu for Relative/Full data paths
(ok by me, annoying it takes more room in the menu though).
As for docs, would be good if you could be more specific about whats
wrong with them to give insight into making improvements.
On Thu, May 19, 2011 at 4:44 PM, Dam
But couldn't be there something like Copy Data Path -> Full | Truncated?
Regarding tooltips, I didn't say that in them should be visible full
path, I'm just saying that under the tooltip is displayed something
completely different then you actually get when you copy data path.
I didn't know any p
On Thu, 2011-05-19 at 09:31 +0200, Damir Prebeg wrote:
> Hi there,
>
> It would be much more useful if we could copy full data path and not
> just the last part of it. For instance, If I copy data path of x
> render resolution, all I get is "render.resolution_x". And under witch
> module or class
On Thu, 2011-05-19 at 09:31 +0200, Damir Prebeg wrote:
> Hi there,
>
> It would be much more useful if we could copy full data path and not
> just the last part of it. For instance, If I copy data path of x
> render resolution, all I get is "render.resolution_x".
The primary use for this is in
Hi,
Well, I wouldn’t see me as a « hard core master of Blender », but I find
the bpy doc quite understandable, once you have grasped the basics of
bpy (and learned how to read API doc?)…
As the page shown when clicking on the “view doc” states, resolution_x
is a property of RenderSetting class
Hi there,
It would be much more useful if we could copy full data path and not
just the last part of it. For instance, If I copy data path of x
render resolution, all I get is "render.resolution_x". And under witch
module or class lives that render? It's like you are giving me a
street name with a
