Jump to content

eluengo

Members
  • Content count

    35
  • Joined

  • Last visited

About eluengo

Profile Information

  • Gender
    Male
  • Location
    Spain

Recent Profile Visitors

98 profile views
  1. space for displaying page numbers is a bit too small (think of if more than 100 pages....)
  2. Sometimes Style Names doesn't correctly update when creating a TOC style duplicating another (screenshot). And the naming - renaming - applying - creating Styles (everywhere) is a bit cumbersome and inconsistent Emilio
  3. little problem with scroll bar when a document has a lot of pages.... it dissapears behind end of window..... see screenshot
  4. with "linked preferred" in document's setup, the app continues to "embed always" the images....
  5. packaging proyects is very interesting..... BUT.... like ID, a package needs that the receiver (self or other) uses a compatible version of the generating app (ID or whatever). for a propietary/personal use..... a good archiving policy is better than packaging for another/printer/typesetter ’s use....... better an interchange format: PDF can be a better solution, or EPS, or SVG, or the like
  6. metric, inches, picas or whatever has to be continuously translated in computer measurements (computer screen size and resolution, printer density and size, typesetter measurements, size and density, etc...) so the translatrion between traditional measurements is really unimportant, are only methods in an object or module or routine in the app. but could be interesting, could be.... for people who use picas.... time passing .... lesser
  7. literals overlapped in this dialog when greater text interface selected in preferences (.... problems in the future when localizations to other languages are ready... german, spanish, etc...????? [longer words])
  8. Probably in a near future, because some indications do exist in the [Text] menu.....
  9. I've identified theTOC ordering problem.... If the frame containing a hierarchical superior (supraordinated) line is created or pasted after a frame with a subordinate text item also compiling for the TOC, the result is that this last frame/text appears before the previous existing frame/text (subordinated, theoretically). Solution is cutting and re-pasting this previous existing text frame, and after recompiling the TOC, the lines order is the correct. (reordering through the [Layers] panel has no effect)
  10. OK all works more or less as I awaited (and lacking any help, I've seen the answers afterwards) BUT... something happens with the order in which the app finds the different frames with the text&styles which should be inserted when the app compiles a TOC (in my case it is not a continuous text, there are different frames with different chunks of text), because it showed initially an erroneus entry order in the TOC frame. The solution was to cut and then paste the text frame that appeared in the bad order in the TOC. Sorry I don't have the screen images, because it happened with a long and repeated trial-error sequence.
  11. .... resolved.... a bit awkward, but resolved
  12. How to create a hierarchical TOC?, similar to the shown in the example I send....
×