- User Since
- Jul 29 2008, 1:46 AM (515 w, 6 d)
Fri, Jun 15
Is there any reason that Object colour can't be added back as an option?
Wed, Jun 13
Compile fix for bmain changes in 2.8
Tue, May 29
Added back bar.
Added back bar and simplified the logic.
Sat, May 26
Added new mute cursor and adjusted the way lines are drawn. This is better for long links and works with the new way that 2.8 draws links, previous 2.7x patch was completely different. Also fixed highlighting when nodes are selected.
Muted links display red at both ends and the normal wire colour in the middle.
Fri, May 25
+ Add custom mute cursor
Thu, May 24
Updated D2807 to Blender 2.8.
Updated patch for Blender 2.8
Apr 26 2018
Could this task be considered for inclusion in 2.8 during one of the CodeQuest UI meetings? I'm wondering if there is anything else that needs to be done for this?
Have you considered colour blindness accessibility especially with the colour coding? Thinking that for the Blender 101 this is going to be important.
Mar 1 2018
Feb 12 2018
Feb 8 2018
Feb 2 2018
Dec 8 2017
The bitmap scaling function seems like a good idea and might be a more efficient way to reduce the steps to a minimum. Scale down to 32 pixels and then run through each pixel in order whilst ignoring any matches.
Dec 6 2017
Sep 14 2017
Sep 11 2017
Sep 10 2017
Sep 9 2017
It's the edit cursor. I couldn't use the cross or knife cursor as they are used by the cut and reroute operators 😆
Sep 8 2017
Minor edits, no functional change.
Sep 7 2017
Sure, I'll take a look at 2.8 branch.
Adding existing api call link.to_socket.is_linked == False enables muted wires in Animation Nodes (limited testing 😄).
#..\tree_info\forest_data.py for link in links: if (link.from_node.bl_idname == "NodeUndefined" or link.to_socket.is_linked == False or link.to_node.bl_idname == "NodeUndefined"): continue originSocket = link.from_socket targetSocket = link.to_socket
Flag target socket as used/unused when muting wires. Enables the use of existing socket.is_linked api method in addition to the link.is_muted method.
Sep 6 2017
@Campbell Barton (campbellbarton) thank you for the code review and commit
It should be noted that the original idea for this feature came from Thomas Heizle, who was using Blender as an example for suggesting new node features to an audio application called Usine, worth checking his original post here: http://www.sensomusic.org/forums/viewtopic.php?id=4918
Change DNA defaults as requested
Changes as requested by @Campbell Barton (campbellbarton).
Draws muted links with a bar accross.
@Campbell Barton (campbellbarton) - Thanks for creating a task.
Sep 5 2017
Aug 29 2017
Tidy up and dedupe shape draw function(s)
I messaged Jacques Lucke on BA about AN/Pynodes, and he suggested that the API description should be changed and that it would be an easy change to support muted wires.
Minor changes, change description of 'is_muted' function
Aug 28 2017
Agree that it is a design task, I think the picker is definitely a very personal choice and there is certainly room for improvements or additional options here.
Aug 25 2017
Now working with Cycles nodes.
Aug 24 2017
Aug 23 2017
Aug 21 2017
This is partly a limitation of how colours are picked and stored in Blender as RGB values. This means that when selecting a red with a Hue of 0 or 1 it is converted to the same RGB value which is what is stored, The hue value used in the ramp is determined from an RGB to HSL/V conversion. A potential fix for this would mean adding the ability to store Hue values when selecting colours which would result in the correct interpolation.
Sep 24 2014
Yes its no longer valid. Its old and stale.
Aug 23 2014
Forgot to attach blend file.
Aug 22 2014
Aug 15 2014
woo, thanks campbell for all your help (work) :)
@campbell -- hopefully this fixes the hue jump. No idea why it doesn't happen here.
- + Add conversion to/from linearrgb_to_srgb_v3_v3
Aug 14 2014
FYI 4.875 is referenced in the following lut -- ...\datafiles\colormanagement\luts\srgb.spi1d
@campbell - Hmm I can't reproduce the glitch here. Maybe a screen shot if you get the chance. Thanks again.
Aug 13 2014
- Remove unused functions
Ooh I thought I'd reverted the color_math file. Will update patch later today.
Aug 12 2014
- Forgot to remove functions from header
- Remove lab, hcl modes. These need to be done correctly with respect to the color management. Remove steps.
In this case it might be best to remove hcl and lab modes from this patch and look at adding them later.
Aug 11 2014
- Dedupe function calls and layout code
Aug 10 2014
Sorry accidental creation
Remove InputFX struct from CurveMapping
@campbell - i've tried once more to get gtests running but I've not had any luck -- sorry!
Aug 8 2014
@campbell - I've got arcanist setup which is good but I've struggled to get the default gtests to compile and run (using windows cmake/vse13). The previous image I uploaded shows pretty good evidence that the conversions are working because they show the same start and end colours for all modes. Tested with image editor color picker.
Aug 7 2014
@campbell - do you need me to do anything else with this patch?
@campbell - thanks for updating the patch.
+ Fixed the colour conversions.
+ Removed the XYZ option as this produces the same ramps as straight RGB
Aug 6 2014
Looking further at the two existing xyz <--> rgb functions, only one of them requires a colour profile. This suggests that they may not be totally compatible with each other.
Thanks, that was more than a minor cleanup ;).
Aug 3 2014
Added references to formulas
Remove the reference to old Blender patch
Removed unused functions, lab_if and rgb_to_xyz_matrix
Aug 2 2014
The colour conversions were taken from an old Blender patch. They are referenced before the functions. The patch is here: https://developer.blender.org/T28386 by fvdsn (Frederic van der Essen)
Aug 1 2014
Changed rgb conversion functions to non compat versions due to weird behaviour in blend texture