In a nearby thread, some were talking about small annoyances in the design of dialog boxes within InDesign. Some annoyances are longstanding version after version. What small issue would you improve in InDesign?
Recompose stories errors with footnotes and tables. Have been there ever since the introduction of both, and much cause for concern.
I once sent a client a "final" print-ready PDF for his ready-for-pressapproval, and he responded with an e-mail with no less than 14 "!!!" interspersed between incredulous queries of "you can't be kidding" and exasperated shouts of "DO NOT SEND IT TO THE PRESS". Quite impressing stuff, actually.
The mere fact that these errors pop up show that ID's Text Composer, complicated as it is, is still something of a black box even for Adobe.
Thanks for the no-feature-requests clarification, Michael - I had to delete a few actual feature requests before posting. But, that being said:
I would really like Span Columns and Split Columns to not cause massive performance hits.
I would like extensive cross-references to work without a massive performance hit.
It'd be nice if xrefs worked across documents in a Book file.
I'm sure I'm not the only person who sees stuff like this:
It's a graphical bug that I get when I increase the size of the Tabs panel. There are a bunch of panels that do it. It's Windows-only, I think, and it's something about the video drivers, or maybe even the onboard Intel video adapter, that our IT department likes to use. I've been seeing them constantly for years and years at work, and quite often when I look at other people using ID on Windows.
@Michael – I already made one or two suggestions in the other thread.
I will rephrase them:
Pages Panel / Move Pages...
Change the order of options to:
1. Move to:
2. Move Pages:
Pages Panel / Move Pages...
Grey out the option: "Delete Pages after Moving",
if the range defined in "Move Pages:" will theoretically cause an empty document without pages.
If you share the irritation with any of the things posted here, please don't overlook posting an official feature/bug request here: Wishform The more voices, the more chance for seeing results in a future InDesign release.
I wish Table of Contents styles were relabeled as Table of Contents presets, to be consistent with the rest of InDesign's presets schemes. Having a 1 dialog box where the word Styles is used in 3 different contexts is confusing: Save a Style that gathers certain styles so that the result can be styled a certain way is hard to explain to newer users.
My minor irritation: I wish that, when I had my pallets stacked together, opening one would NOT automatically close an open one from the same stack. (I understand that those in the same tab group can't open together). For instance, as below, my Swatches pallet can't be in my stack if I ever want to have it and the Gradient pallet open at the same time. It would be nice to at least have an option to change this behavior.
Yep, it would be nice if that all had a bit more intelligence. My partial work-around there is to employ two or three collapsed docks. One dock is docked onto the edge of the next dock, like double-parking. Each dock has groups of panels in it. When one dock has a panel open, a different dock can also have a panel open. Not ideal, but sometimes workable.
I'm not sure that's any worse than Table Styles or Object Styles, but I could live with calling them presets.
I'd love to see the hanging indents and Step and Repeat errors mentioned in the other thread fixed. Those probably annoy me more often than any other quirk in ID.
I agree. I am forever typing the wrong number in first, and having the thing complain to me.
Here is another one: In preferences, under Composition, you can turn on highlighting for Keeps Violations, H&J Violations, etc. I wish it would simply add a color square beside each one, so that I know what color to expect to associate with each onscreen issue: yellow is what? amber is what? green is what? It could be clearer.
Expanding on that idea, why not have an indicator all throughout the many preferences that tells me whether it is a document preference or an application preference. That would clear up lots of confusion.
Looks like you're right, not sure why it was working differently earlier. Okay, discount 2 (answered already) and 5 from my list (sorry for the noise, I would edit the post but I can't find an edit link, looks like edit is time-limited).
One more: baseline grid settings under "Layout" that, like margins and columns, apply on a per-page or per-master page basis and override preferences where appropriate - it's a) a more intuitive consistent location for what is often used as a layout setting and defined at the same time as margins and columns, b) a more consistent behaviour with margins and columns, and c) solves issues like this one.
Complicated, but here is how that is done:
Build two separate masters; not based on each other. On each master page you build text frames. On each text frame go to Text Frame Options > Baseline Options > Use Custom Baseline Grid. Your leading of master A text frames can be different from master B text frames. You edit your BodyText paragraph style to Align All Lines to Baseline Grid. You can even link a text frame supplied from A to a text frame supplied by B; have text flowing through them; and the leading will change automatically. So it IS possible to have more than one baseline grid system in a document. You essentially ignore the one setup in preferences.
Not sure how I would make that more intuitive, since it involves editing master page text frames, document preferences, the View setting, and (ideally) the paragraph style.
1. Not exactly. I meant that you can't enter the negative first line indent until you have a positive left paragraph indent specified that is big enough to absorb it, which means you have to fill the fields out of order.
2 is solved
4 you can add your voice to the crowd for improved footnotes over in the Feature Requests forum, and check out Peter Kahrel's scripts as a temporary workaround.
Thanks. I'd looked into custom fonts for icon bullets before but discounted it because the people I share InDesign templates with aren't able to install custom fonts (those corporate networks where everything is shared from a tightly controlled central server) - I've added a question about whether that's an issue on that thread.
One more common frustration... Inconsistent interpretation of a Wacom (Intuos/Cintiq) tablet's pan / scroll instruction. If you have a tablet with a pen button set to pan / scroll, you have to either remember that this is essentially broken in Indesign, or, you have to go against an indesign design decision and set it to a 'Space bar' key press only in Indesign and remember to never ever try to pan or scroll while in a text frame. I've added more information to this thread about the issue.
Since the font that IF creates is a regular font it's expected that it be installed. If that's a problem, you can sneak around it by adding a subfolder in the directory where the .indd file is stored named Document Fonts and put a copy of your new bullet font in that. It will be installed in the document for editing (and exporting a PDF), but not anywhere else, when the document is opened in CS5 or later.