m1b
My feedback
31 results found
-
3 votesm1b
supported this idea
·
-
1 vote
An error occurred while saving the comment -
265 votes
Thank you all for the votes.
Can you help us understand the key problems that you face in the absence of ability to send an anchored image backwards?
What’s the current workaround that you have to follow?
What are the use cases wherein you need that the text appears specifically on top of inline anchored image?
This information will help us evaluate the functionality better.
An error occurred while saving the comment m1b
commented
@Abhinav Kaushik my simple use case example is this:
I have a table of numbers. Some numbers have a coloured oval background behind them (different colours). I currently use custom (not inline) anchoring and it works fine for stroked (not filled) ovals. But for coloured, filled ovals it just hides the number that the oval is supposed to highlight!
My workaround is to (painstakingly) cut and paste the number text into the anchored Oval (which is converted to Text Frame).
If we had this feature of drawing the anchored object *behind the text* I could just paste in the coloured oval and—with an appriopriate Object Style—would work perfectly.
(Note: make sure the scripting API has access to the "draw behind" flag, too!)
m1b
supported this idea
·
-
1 votem1b
shared this idea
·
-
4 votesm1b
supported this idea
·
-
2 votes
An error occurred while saving the comment m1b
commented
Sure. Besides, that’s the part that works. Did you try the script Maik? What result did you get?
m1b
shared this idea
·
-
5 votesm1b
supported this idea
·
-
Ability to add color labels to individual styles to better organize and manage large lists of styles
81 votesm1b
supported this idea
·
-
32 votes
The fix of the issue is now available in the latest InDesign 2025(v20.4.1.004). We recommend you upgrade to the latest version for the fix.
If you are unable to see the update, go to the Creative Cloud application click on the context menu on the top right, and click on Check for App Updates.
—
Adobe InDesign Team
An error occurred while saving the comment m1b
commented
I can confirm this issue is fixed in Indesign 20.4.1. Thanks!
m1b
shared this idea
·
-
3 votes
An error occurred while saving the comment m1b
commented
Agreed! I find this dialog difficult to use without zooming in temporarily, which is awkward. Remember this dialog is often used to craft complex greps. (ID 20.3.1, MacOS 15.5)
m1b
supported this idea
·
-
11 votes
Thanks for reporting
We are reviewing the issue-InDesign Team
m1b
supported this idea
·
-
1 vote
Fix for this issue is available in the latest InDesign Release version 20.2, available via Adobe CCD app.
--
Adobe InDesign team
An error occurred while saving the comment m1b
commented
I confirm that this bug is fixed for me in Indesign 20.2. Thanks!
- Markm1b
shared this idea
·
-
2 votesm1b
shared this idea
·
-
7 votesm1b
supported this idea
·
-
7 votes
An error occurred while saving the comment m1b
commented
Yes Paul, that would definitely be the way to go, especially as it would then make it easy for Adobe to add more properties and methods, such as error-correction level and various visual options such as those offered by many other QR Code generators.
m1b
shared this idea
·
-
167 votes
We have made some Performance Improvements in the latest InDesign Release 2025 (Version 20.1), available via Creative Cloud Desktop application. This issue has also been fixed as part of performance improvements.
Please let us know if you still face slowdown while doing basic operations in this latest InDesign release.
--
Adobe InDesign team
m1b
supported this idea
·
-
4 votes
An error occurred while saving the comment m1b
commented
I can confirm that this bug still exists. I'm running MacOS 15.2 ID 20.0.1.
My test code:
```
//@targetengine "mySession"
var myEventListener = app.eventListeners.item("mAfSave");
if (myEventListener.isValid)
myEventListener.remove();myEventListener = app.addEventListener("afterSave", testQRCodeCrash);
// myEventListener = app.addEventListener("afterOpen", testQRCodeCrash);
myEventListener.name = "mAfSave";function testQRCodeCrash() {
alert('Test started');
if (!app.documents.length) return;
app.scriptPreferences.measurementUnit = MeasurementUnits.POINTS;
// any of these cause Indesign to crash:
app.activeDocument.rectangles.add({ geometricBounds: [0, 0, 40, 40] }).createPlainTextQRCode('test');
// app.activeDocument.rectangles.add({ geometricBounds: [0, 0, 100, 100] }).createTextMsgQRCode('1234567890', 'test');
// app.activeDocument.rectangles.add({ geometricBounds: [0, 0, 100, 100] }).createEmailQRCode('foo@bar.com', 'test', 'test');
// app.activeDocument.rectangles.add({ geometricBounds: [0, 0, 100, 100] }).createHyperlinkQRCode('https://foo-bar.com/test');alert('Test completed');
};
```
See this [discussion on the forum](https://community.adobe.com/t5/indesign-discussions/function-createplaintextqrcode-crashes-adobe-indesign-without-any-reason-provided/m-p/15036478#M601870), too.
- Markm1b
supported this idea
·
-
28 votesm1b
supported this idea
·
-
5 votes
An error occurred while saving the comment m1b
commented
This seems like a good idea to me. I guess it could be similar to the Object Style "Size and Position" sizing feature, off by default, but available if you want it.
m1b
supported this idea
·
-
3 votesm1b
supported this idea
·
An error occurred while saving the comment m1b
commented
I found the same issue just now. The problem occurs in the normal Find Text and Find Grep UI also.
I think it is because the UI has no way to distinguish between changeTo === "" and changeTo === undefined.
So my guess is Adobe decided to just disable changeTo in cases where you are changing other properties, eg. Paragraph Style. It's a shame that it is also disabled in the scripting API, where we can explicitly set changeTo to undefined if we want it ignored.
I would like this fixed too. The UI should have an "Ignore" option for changeTo similar to the way styles' properties can sometimes be set to "ignore".
Both the attached screenshots, showing a search for a number with a tab should remove the number and apply the new paragraph style, but both fail because the changeTo is ignored.
Moderators: this feature exists now.