"content", overlaps other icons if it is squeezed, making it impossible to use it enlarging the size of the thumbnaili using ctrl + scroll does not work, and the magnifying icon under the panel, e.g. I tried to change the color spaces of the monitors, but it only introduced chaos and I don't know how to go back to the previous settings preview colors of photos (all types of files) are completely different than displayed in PS. ![]() Enter works like a cursor in the content panel instead of opening files Non-technical users who don't know where Bridge stores User-Data are likely to lose keyword databases or other preferences in this technically needless process.Hi, I have installed a new Bridge and unfortunately the changes made to it make my earlier workflow very difficult compared to the previous version: Required actions, just to call the batch command from Bridge again, when not shown ('PS pick up an external selection and do something with it') are ridiculous - seemingly even the sequence of app-installations plays a role here. Customers see expected actions fail and receive neither meaningful error messages, nor actionable guidance. ![]() Adobe is super unhelpful with this product version mismatch. ![]() The latest ACR version installed could determine which RAW files can get shown and processed (that's not a Bridge thing). Just to display file thumbnails and write metadata Bridge does not have to know any of Photoshops latest AI features - in fact it totally doesn't. Linking Photoshop version an Bridge versions is not necessary for technical reasons - it is just your business convention.You stick to this hostile strategy, even in a situation where many paying customers struggle with the most recent Bridge versions. Association of Bridge version and Photoshop / ACR version is extremely customer unfriendly.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |