Hi Dan,
Sorry I did’nt reply to your email ! Ok I take note of this performance issue, have you been able to identify a specific operator which is causing this. ?
Fantastic op! I just tried it on build 2023.11340 on a Mac and the Refresh menu items were throwing errors. In case anyone else is having the same problems, replacing the Web ops with Web Client seemed to solve the issue for me.
@rasavell same issue here, but I am unable to follow your instructions to fix it. I’m running Mac (ARM). Can you please share the fixed .tox? Thank you!
Hi.
colour_lovers_picker_QuickFix.tox (185.4 KB)
Gotcha! I’ve attached the fixed .tox here, but the quick solution for me was the following:
Step 1:
Go into the .tox: colour_lovers_picker/WEB; right click on the 4 Web DATs (named “hue”, “top”, “new” and "random); choose “Change OP type…” and change them into Web Client DATs.
Step 2:
Go back one layer and edit the “CLPickerEXT” Text DAT.
Line 32 in colour_lovers_picker/CLPickerEXT DAT is usually:
self.web_comp.op(palettePage).par.fetch.pulse()
…but it should be:
self.web_comp.op(palettePage).par.request.pulse()
…because the new Web Client DATs that we made don’t have a “fetch” attribute, but a “request” attribute.
It will still throw an error for half a second before refreshing the list + the Hue tab/function doesn’t seem to be working… But it’s better than nothing! 
Carpe diem
@bordegard.art
1 Like
Hi there, is anyone else having an issue using this with experimental build 2025.30960 (latest as of now) where it won’t let you click the colors you want inside of the component? If you randomly click around, you’ll get one eventually but something with the accuracy of the selection is off for me.
yeah i get this also. don’t know enough about TD to know how to fix it yet
Hey, i’ve just experienced the same issue on experimental build 2025.31310. Although i’m not sure if it works correctly on the stable release.
The issue seems to be related to the mouseclick inside the ‘Viewer active’ and it works correctly when you set the number of colums to 1 inside the ‘Setup’ tab of the Color lover picker component.
I’m not sure if this helps anyone but I made a small change to the UI logic to get around some of the performance issues (I use the oldest PC in my company so this tox tanks my FPS to 30-40). This change seems to coincidentally fix stuff for 2025 (at least I can click on stuff and it seems to work). I haven’t really had time to test properly since I only have tried using this for a few minutes (it looks like something I could use in the future) but I figured I would share it as a starting point for anyone else who still uses this tox.
For anyone interested I just converted the Containers to Bases to remove the rendering, and composited the palletes into a single image that is roughly similar to the original layout. From here I calculate the selected component using the UV coordinates of a mouse click on the image. Unfortunately this means it is restricted to 720p when using a non-commerical license but everything seems to work otherwise, except for deleting favorites (sorry I didn’t have time to look into this but I can try later if anyone is interested) and resizing the UI.
Also, apologize if I changed the base version, I pretty much use 2023.11600 exclusively (I only tested this with 2025.31310 on a whim).
colour_lovers_picker_QuickFix.toe (159.5 KB)
I had a free moment today so I looked into the UI/resizing logic for using TOPs instead of panels and made a few small adjustments to get it working. I think everything should work fine in the latest 2025 release as well. Just keep in mind that the UI becomes unreadable quickly if you are using a Non-commerical lincense due to the 720p top limit.
colour_lovers_picker_QuickFix.tox (171.2 KB)
2 Likes
Not a big deal but I see this a lot so I thought I would correct for others reading. With Non-Commercial you can render 1280x1280, there is no 720p limit. I guess this is often assumed because16:9 aspect ratio is so common, but you can work with a lot more pixels than that in Non-Commercial!
1 Like