Skip to main content
Inspiring
December 1, 2022
Question

Find color tint range not working in InDesign 2023

  • December 1, 2022
  • 1 reply
  • 3189 views

I never used this feature before but needed it now to change a batch of files. Looks like it's broken. Basically the field for tint range is ignored when searching.

 

I've deleted InDesign preferences and cache. I'm using InDesign 2023 on a Macbook Pro M1 with latest MacOS. I also tried InDesign 2023 on an iMac 2015 with previous MacOS.

 

When it didn't work with my documents I made a new test document and could see the same problem. I add 4 frames with black color fill and then change 3 of them to different tint values. When I search for a tint range and replace all 4 frames are changed.

 

Here's an older thread

 

 

This topic has been closed for replies.

1 reply

Steve Werner
Community Expert
Community Expert
December 1, 2022

I think you should provide more information about your issue. Are you working with the Find this Color feature on the Swatches panel menu? Please provide an example of what you're expecting the feature to do for you.

AtappAuthor
Inspiring
December 1, 2022

Find color in the Swatches panel or Command F for Find and click the color tab. It's the same thing. I don't know of any other way to find a tint range. It's shown here:

https://helpx.adobe.com/indesign/using/find-change.html

AtappAuthor
Inspiring
January 17, 2023

While we are at it, @HARSHIKA_VERMA , there is also a bug with the input field for the Tint Range.

I'll get a warning message that the range must be between 0.0 % and 100.0 % :

What is wrong what I'm doing here?

My guess is that a blank is missing between the number and the percentage character.

But no, I'll get the same message when I add a blank to the input like that:

 

Well, now I get it. I must NOT change just portions of the input field entry, but I must clear it all and type something new. Like "0-100" (without quotes). Bad user experience…

 

Regards,
Uwe Laubender
( Adobe Community Expert )


I struggled with that too. It's clearly not behaving as other inputs.