This is not my first post. Supposedly the second patch fixed this non working part of 2019. It only sort of did. Sometimes I can get it to work. Once. After it maybe works once, it won't find anything on the next find and replace. I had to open a file in x8 to work with a client's file, so I could group similar colors and replace the fills/outlines. There were 8000 little pieces of objects in that file, and 2019 was absolutely of no use trying to clean this file up. I'm so frustrated that this just doesn't work right. I know others have no problem with it, but again, it'll only work once or twice, and then I get no objects found. Do better Corel.
I also have the same problem, and it happens intermittently with 4 of my 5 other coworkers who use it commonly. Mine behaves similarly, but some days even after exiting Corel and opening it again, my find and replace will still not even find a color palette or specific color value or hue. I've basically stopped using it and have been trying to run with just scanning my objects docker.
I was wondering if this could be due to an upgrade that picked up historical or previous information from my X8 setup that I had customized.
Did you upgrade or is your X9 a clean install without any previous installs on your machine?Do you have a customized workspace for your corel? Did you import an exported X8 workspace into x9?
Do you have any other theories or issues with your corel that you've noticed with 2019? For instance I don't have the "Common Shapes" tool in my workspace at all and I can't find even a way to find it
I use Find and Replace text a lot. Or used. Until it completely stopped working about a couple of weeks ago. Find object etc works fine, but with text it won't do anything. Yesterday I tried to uninstall the whole program and then reinstalled it. Didn't help. Luckily I have the X8 that I can use for text replacing purposes.
What you're describing is EXACTLY what I'm enduring. It's an "upgrade", but a clean install in completely different directory from my prior installations, which happily, are still intact. I can open my difficult files and fix all the messed up colors from my clients and then import it into 2019. I started using 2019 with a saved workspace, but was told the incredible amount of trouble I was having was due to that workspace. I built a new workspace from scratch, which helped a lot of the problems, but not the find and replace. I also have exited the program, hoping that restarting it would make it work. Nope. The only theory I have is that 2019 sucks, and is the buggiest, most unstable, unreliable release to date, and I've been using CorelDraw since version 4.
kben said:The only theory I have is that 2019 sucks, and is the buggiest, most unstable, unreliable release to date, and I've been using CorelDraw since version 4.
YOU GOT THAT RIGHT! I guess the main software developers got fired or QUIT.
After asking our IT to do a clean install of 2019 on my computer and STILL having the find and replace not finding or replacing, I may have found a workaround. This is by no means a fix but it may help. I tested with my coworker who has also been having problems with hers as well and it has worked successfully as a smidgeon of a workaround.
in Find and Replace > Replace Objects > Color
OR Color Model or Paletteif you are getting but you know and can see in the color picker or property bar that the color is there in an object, we have been able to make Corel's Find and Replace re-consider the search by going to Find Objects:Add Query > (I just use a simple query like Fills > Uniform color fill > color)Find All or <, or > (I haven't observed that it matters whether the Query is successful in finding anything or not)and Reset the querythen go back and recreate the Replace Objects query and either find all or replace all
and that has usually corrected my find and replace issues. Sometimes when I've left the same session of Corel running for more than a day, sometimes it hs to be restarted if this method doesn't correct it.
I'm interested to know if this helps anyone else, maybe let us know?