{"action":"created","issue":{"url":"https://api.github.com/repos/JacquesLucke/animation_nodes/issues/145","labels_url":"https://api.github.com/repos/JacquesLucke/animation_nodes/issues/145/labels{/name}","comments_url":"https://api.github.com/repos/JacquesLucke/animation_nodes/issues/145/comments","events_url":"https://api.github.com/repos/JacquesLucke/animation_nodes/issues/145/events","html_url":"https://github.com/JacquesLucke/animation_nodes/issues/145","id":80722398,"number":145,"title":"add cuteness to the tree (my node proposal :D +viewers, reroute, frames and socket tricks)","user":{"login":"og76","id":11709974,"avatar_url":"https://avatars.githubusercontent.com/u/11709974?v=3","gravatar_id":"","url":"https://api.github.com/users/og76","html_url":"https://github.com/og76","followers_url":"https://api.github.com/users/og76/followers","following_url":"https://api.github.com/users/og76/following{/other_user}","gists_url":"https://api.github.com/users/og76/gists{/gist_id}","starred_url":"https://api.github.com/users/og76/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/og76/subscriptions","organizations_url":"https://api.github.com/users/og76/orgs","repos_url":"https://api.github.com/users/og76/repos","events_url":"https://api.github.com/users/og76/events{/privacy}","received_events_url":"https://api.github.com/users/og76/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":18,"created_at":"2015-05-26T00:39:41Z","updated_at":"2015-06-07T21:57:07Z","closed_at":null,"body":"There are some nodes I tried to make (really!) and some tricks I was looking for. \r\n\r\n1. So far I managed to successfully do only on one, with a second variation. Enough to open 2 sides of discussion, plus the debug node / viewer in itself\r\n\r\n**1.1 mini debug and nano debug nodes**\r\nI made 2 variations of debug node to better fit my usage. Used it for a while, no change but in layout:\r\n\r\n![mini and nano debug](https://cloud.githubusercontent.com/assets/11709974/7803262/70bf70a4-0353-11e5-84f7-1ee5f426b8b0.png)\r\n\r\non the original\r\n- I hate that I always hit the print check when I actually wanna drag the node\r\nand I find it too big for only viewing purposes with print button\r\n- I'd like to see the value in the most compact minimized (hide) state\r\n- I'd like to have wider than default width for some values\r\n\r\nthus\r\n- I remove the print button, move on the right panel\r\n- I make the label show the value if no custom label is typed\r\n- I change the default to some 640 width\r\n(+I would have made it wrap the text for some lists, but it's too much)\r\n\r\nbonus extra trick is that in those times when debugs freeze and not update (you know..) this one makes it obvious by changing back the label to bl_label. so at least you can see there's an issue. I guess It's about \"if not input\" that makes it work immediately and not on mouse up, but may not be cool in other respect. Doh, I don't think I have to explain to you any of that...\r\n\r\n**1.2 The nano debug variation** has an extra trick (that is meant to open a second whole discussion here):\r\n- in the right panel I place a check that hides the link (noodle) on th input. So you end up with a little node with no apparent sockets that updates and I usually place very close to the value that it shows\r\n+ it always shows the sock if no link is connected, so that you see\r\n\r\nhere the blend with codes inside:\r\nhttps://drive.google.com/file/d/0BzzAoBwXO8dsSWJSZ3VfeWJBLUU/view?usp=sharing\r\n\r\n\r\n   I'd like to know your thoughts on this. \r\n   Do you think such features can be included? :D (my baby, my first node...!)\r\n\r\n-----\r\n\r\n*And now the 2 topics, Values in Labels and Link hiding (remote nodes)*\r\n**2. on the labels** \r\n**2.1** I tried to show the value in **label for other nodes**, but with no success (no wonder)\r\nI was looking for a convert node, that would also present the value in the label header. Actually a reroute like behavior would be optimal. But did not made it even with float, integer or text input :(\r\n\r\nThat would be interesting if just minimize (hide) respective nodes, and still see something. \r\n\r\n**2.2** as an extra trick, for allowing to minimize and still see whats there:\r\n**math nodes** could have operation in label (not made it, of course :( )\r\nA+B, A-B, sinA etc   \r\n\r\n**2.3** another trick with labels and values would be to have :\r\n- **reroute** node showing the value in the label, usefull for seeing along the noodles what happens, and very descreete label shown directly on the background\r\n- a frame to show the value of it's child, or a certain child , useful cause the font can be bigger so is visible when zoom out. This is a more complicated design logic and may be flawed easely...\r\nBut there are no specific AN reroute and frame, so I did not manage to try anything without a template or so (great excuse!)\r\n\r\nblend script mockup animation nodes reroute and frame, functional \r\nhttps://drive.google.com/file/d/0BzzAoBwXO8dsVmNBRFI4eHpzWDA/view?usp=sharing\r\n\r\nSeeing what you did with the sockets in a general (not only AN) way, made me think that this could be a more general prop panel thing, showing the value in the label. Or maybe not.\r\n\r\nhowever, I really like the reroute discrete label, the rest may be too much\r\n\r\n**3.  Remote connections, like the hide noodle**\r\n\r\nThere are some attempts to this afaiks:\r\n-here is a proposal that hides the links on some reroutes. well, I find that rather confusing for reroutes, but the \"tele\" or \"buss\" node (as they call it ) has basically this idea of a remote hidden connection, some suggestions being for stronger visual indications https://developer.blender.org/T33627\r\n-sverchock does this with the wifi nodes, but they actually set a variable, that you can pick on the other end from a drop down and such\r\n\r\nmy idea is simpler:\r\n**This is just a visual trick, like I did with nano debug. No complications,  just enable or not the respective input socket links!** \r\n(Besides the nano Debug I tried a convert node, to no avail. At least I got a cute name, \"Remote connect\")\r\n\r\n*As design*\r\n- I would use a convert node and *allow hiding the input sock* just like the nano debug + show if no connection. \r\nMaybe a dedicated \"remote connection\" node would do .. (should work rather as reroute, I don't see a more appropriate one)  \r\n- I *only allow hiding the input*. the receiver should be the one to establish this, while the emitter may have n links and not all should hide\r\n- maybe for the output socks, in the emitter, we could have a 1 hit update like button to just  \"show all connections, for receivers\" that will just switch on respective links when confused\r\n\r\n-I would show the value in the node or in the label too, at least to see if something there (miniRemote...)\r\n\r\n   I'd very much like to know your thoughts on these remote and label nodes.\r\n   Does any of this make sense to you?\r\n\r\n-----\r\n\r\n*ps: I just realized I'm posting blends with a changed debug node in it. No data loss, just a debug, but may be confusing. Also, you already messing with sockets show/hide, manage and conversions so I decided not to wait.*\r\nNow that I got that out, I'll keep myself from such long comments :)\r\n\r\n*as for the title, Christmas is far, but cuteness should be in the tree.*"},"comment":{"url":"https://api.github.com/repos/JacquesLucke/animation_nodes/issues/comments/109802794","html_url":"https://github.com/JacquesLucke/animation_nodes/issues/145#issuecomment-109802794","issue_url":"https://api.github.com/repos/JacquesLucke/animation_nodes/issues/145","id":109802794,"user":{"login":"og76","id":11709974,"avatar_url":"https://avatars.githubusercontent.com/u/11709974?v=3","gravatar_id":"","url":"https://api.github.com/users/og76","html_url":"https://github.com/og76","followers_url":"https://api.github.com/users/og76/followers","following_url":"https://api.github.com/users/og76/following{/other_user}","gists_url":"https://api.github.com/users/og76/gists{/gist_id}","starred_url":"https://api.github.com/users/og76/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/og76/subscriptions","organizations_url":"https://api.github.com/users/og76/orgs","repos_url":"https://api.github.com/users/og76/repos","events_url":"https://api.github.com/users/og76/events{/privacy}","received_events_url":"https://api.github.com/users/og76/received_events","type":"User","site_admin":false},"created_at":"2015-06-07T21:57:07Z","updated_at":"2015-06-07T21:57:07Z","body":"huh, that's a lot to dig. not only for linked or not. ok, some comments:\r\n\r\n1. I dear a little comment on the above utils code:\r\nU use **terminology Parent/Child** node. *Maybe use Source and Target* or others if not already widely used and hard to change ... \r\nIt's already used in Blender for frames, as parents to child nodes. I gather you refer to linked to inputs/outputs and so. I know it does not matter and may use whatever names, but if eventually wanna use parent and child for frames or so (self.parent is what I use in op mockup on frames label \r\n\r\n2. **On linked state** I was thinking about workarounds:\r\nmaybe to use the **update area** , \r\n something like\r\n ```\r\nlink = self.getFirstOutputLink()\r\nif link is not None:\r\n\r\nor\r\n\r\nif originSocket is not None\r\n ```\r\n could this be enough to see if something linked there? .. uses the utils code?\r\n\r\n3. So I gather **you don't use is_linked anywhere?** Cause the *enabled* would break that.\r\nAnd I would hate it cause I was doing so well with the Remote... I even got it a personalized pie menu.\r\n![remote pie](https://cloud.githubusercontent.com/assets/11709974/8026198/2029491c-0d76-11e5-8887-73bf433cf07d.PNG)\r\n\r\n\r\n[ I just thought pie menu may need an issue (feature) itself, or to comment in the menu renaming thing. So I made a comment on pie there #146.]"}}