Jump to content

Search the Community

Showing results for tags 'index'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support Forums
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Feedback
    • Bugs in Affinity Designer & Affinity Photo
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Affinity Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 13 results

  1. I have last 2 pages with 6 text frames (3 each) - tall and narrow-ish. I see the full index in frame #1 on the left. It is so long that i cannot see the end. So, one by one, I link the index to each frame going left to right (only clicking the red arrows on the frames to the next frame in sequence). In the 5th frame - in the middle, the index starts all over again (starts with the first letter of alphabet). So, the index repeats itself just twice. Then it ends in the ninth frame and does not repeat again. I have tried deleting all of the text frames and updating the index, linking them again and again, and the result is consistent - always a doubling of the index list. Is this a bug - or is there some simple explanation of how to prevent the index from duplicating the A-Z words twice?
  2. I think this is a bug, at least unexpected. I have these words (and others) in a document: 23rd Regiment 19th Mercantile The index lists 23rd Regiment under the alphabetical letter "R" taken from the "rd" ordinal ending. I would expect it to be listed alphabetically under the characters "23". The index lists 19th Mercantile under the alphabetical letter "T" taken from the "th" ordinal ending. I would expect it to be listed alphabetically under the characters "19". The indexed words are, however, sorted before the alphabetical letter "A" - so it's sorting by the two numbers "19" and "23" but listing them under the ordinal's first letter instead of the numbers. copied from index: T 19th Mercantile 225 R 23rd Regiment 225 A Air 225 B Bird 225
  3. Looking at the "default" style/formatting for the index entries (inside a text frame) I would like to see the following: 1. Page numbers always starting on the same line as the indexed item. This has the advantage of saving space (extra lines) in the index. 2. Page numbers that wrap around to the second and subsequent lines, should be indented from the indexed item itself. Also helps the viewer to scan for index items easily. Example (ignore empty lines - they are an artifact of this forum's format): P Parts 11, 12, 16, 21, 22 Photo 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 100 Plano 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 200, 201, 202, 203, 204, 250, 251, 300 I could not find a way to do any of this with the existing UI. Are there some specific settings that would accomplish it?
  4. I have noted that both text frames and index frames will wrap around entire words and will not split a word into two lines and will not put a dangling comma starting a next line (keeps the word and the comma together always) and will not allow a dangling space to start a next line. However, numbers are being split across two lines both in text frames and in index frames and a comma or a single space (such as found between index page numbers) may end up starting a next line both in text frames and index frames. I believe that these are bugs or broken features; that numbers (with commas and spaces) that wrap around to another line should be treated the same as alphabetic characters (and not split between lines ever) and commas and spaces should not be starting a line that has wrapped around. I have not found any way to control this from the UI. Here is one example that I have in an index (and confirmed that it has a similar problem when formatted separately in a text frame with the default "body" style). (Example shows the split page number "60" on the first line of page numbers, and the dangling space starting the next to last line and a dangling comma starting the last line of page numbers). Photo ii, 5, 18, 20, 21, 22, 29–31, 34, 40–42, 44, 45, 56, 6 0, 66, 67, 70, 71, 73, 78, 98, 99, 115–117, 119, 123, 126, 155, 173, 189, 190, 191, 193–195, 197, 200, 206 , 207, 212, 221 A quirk that is unusual to me: if the number of pages for an indexed item are few, then the item and the page numbers are all on the same line. If the number of pages is larger than will fit on the first line, then all of the page numbers start on the line after the indexed item (as shown above). I would think it more efficient and consistent-looking to always start the page numbers on the same line as the indexed item (as is possible if the indexed item itself is not too long) and then wrap around to the second and subsequent lines as needed. Is there a compelling reason for this inconsistency between a short page number list and a long page number list? Thanks for any information on how to control the formatting or confirm if these are bugs.
  5. Suggestion: When you have the Studio/Index panel open, and when you use it to add an indexed word(s), it would save a lot of clicking/dragging the Studio/Index panel list up and down IF the software would immediately "jump" to the newly added item in the Studio/Index panel. The next step, usually, is to find the word(s) and check-mark each one you wish to include in the index. I find that I'm constantly scrolling back and forth to find the newly added word(s).
  6. Hi I am used to using PagePlus 9 and use the book feature to stitch together many articles with photos from different authors and sources to make a school publication which is photo rich and can run to 90 pages plus at times. The articles arrive randomly over time and the ability to create chapters and then re-order and re-index is invaluable. Is the chapter feature available on Infinity Publisher?
  7. Are there any plans to create an auto-index feature? I swear ID can do this - but all I see in the Publisher Beta is the tedious 'insert index marker' by hand, page by page, for each and every topic you want to index. Surely when you're laying out a reference book or other large publication, there's a more automated way to do this then searching for each instance of a word and then inserting a marker? Or, like Table of Contents, could there be a way to have words with special formatting automatically flagged to be included in the index? As it is, indexing currently feels incredibly clunky and incomplete. I do realize this is still in Beta though, so curiosity prompts me to ask if polishing up the index feature is something slated for future releases? On a positive note, I found the TOC very easy to set up, format, and create - quickly and effectively. Great job!
  8. I just created an index but the page numbers are out of order (see screenshot below). I've read the Help doc and searched the forum for 'index AND page AND number" but don't see anything addressing this problem. I've certainly done something wrong but can't imagine what or how to tell Publisher to sort the page numbers. Any suggestions would be most appreciated. Thanks Doug Running Affinity Beta Publisher 1.7.0.238 on macOS Mojave
  9. Hey affinity team, a while ago there had been existing an index of common feature requests which gave the users some ideas about which features might be expected in future releases. https://forum.affinity.serif.com/index.php?/topic/10410-common-feature-requests-index/ Could you please make such a sticky post again? Thank you very much. Benny
  10. I wish that Publisher will have support for multiple indices (Index of subjects, index of passages, index of authors, index of ancient authors, index of tables, index of figures etc)
  11. The ability to tag text elements and generate an index (automatically like the Table of Contents) is one thing I would use in larger projects. Likewise, the ability to build cross references that automatically update the page number (to avoid 'see page XX' errors) is something else that I use regularly, but indexing is a higher priority. This looks really good and I'm looking forward to trying it out properly.
  12. First of all, AP is a great app. It may well be the equal too, and in some ways, superior to Photoshop. The problem isn't the tool but in the interface. Or more precisely, learning the interface. Choosing to appeal to PS users, disaffected or otherwise, I believe the Serif team made two incorrect assumptions about those users in development, including: 1. That changing terminology from the gold standard Photoshop wouldn't be a problem. The words we call things matter. Example, if common usage (the base term) is that A is a process that uses tool B, changing the base term to C means that user has to learn that C now redefines the process, renames it and so moves it into a different indexed space, just to find, and use, tool B. That is further complicated if the assignment of A to C using tool B is changed to assign it to tool D without a reference , e.g., "if you used B in Photoshop to do A, to do the same thing in Affinity you should use D to do C." Without that guide, a digital Rosetta Stone, the learning curve becomes much more difficult. 2. That everybody who used Photoshop used the tools in the same way. This may be the greater mistaken: PS users do not use PS the same way. The many-ways approach isn't just a marketing term for PS, it was integral to how many long-term users learned and applied the program. Like many other PS users, I've been at it through several generations of the app, and learned which of the myriad PS ways to completing a task worked best for me. Not the best ways, perhaps, but my ways. In fact, these two assumptions are why I'm struggling with AP and may have to switch back to PS.
  13. I dont't know if this feature has already been requested, but posting this wish here anyway :\ I'd like to see browse / index persona (or ui add on), that I can throw away Microsoft Photo and Corel AfterShot Pro as photo browser and indexer. So what I'm looking after; feature that I can maintain picture library/index of photos in Affinity Photo/Designer (and perhaps kind of version control of edits).
×