Jump to content

Aleksandar Kovač

  • Posts

  • Joined

  • Last visited

Everything posted by Aleksandar Kovač

  1. Thank you @prophet for taking your time to try this approach. I have been testing more. There is an elegant and trivial workaround for preserving layout on the Publication page when using additional masters. Simply put: do not resize Master page. 🤔 😂 As long as Master page is not resized, one can move about objects on it as much as desired. Master layout will be preserved on Publication page. Objects can even be positioned outside the Master page. And still everything will be displayed, editable, snap-able... In case one feels queasy about objects positioned outside the Master page, one can make an oversized Master page that will comfily contain all future resizing. Just make sure that, when adding this master as an additional Master, to click 'No' to publication page resizing query. With this workaround, additional masters are quite a sturdy and snappy tool. And, I believe, in some scenarios, superior to assets and symbols.
  2. Hi @Callum and thank you for replying. Please take a look at the attached file... And try to do some of the actions suggested inside if you can. I believe you will quickly see that, compared to symbols, using additional masters in a publication page is another thing entirely. Here, User modifies the content freely, per instance, while keeping the layout from Master. additional masters.afpub
  3. Also, I am unable to successfully assign (⌃⌥;) or (⌃⌥') in Publisher/View shortcuts to trigger Guides manager or Grid/Axis manager. Minus brackets, of course. The shortcuts are displayed fine in the input box but, once in the workspace they ignore ⌃ and act like (⌥;) or (⌥'). Shortcuts like (⌃⌥S ) (⌃⌥. ) work. No shortcut conflict registered. Ignore modifier checkbox off. Tested after clicking 'Reset' on Preferences panel AND after clearing using CTRL while starting the app. Publisher Beta
  4. Thinking along... Perhaps the proper concept would be: partial masters? Sub constructs of sorts? I hope I am not alone in thinking this is incredibly useful?
  5. Yes. A multi-page Publisher file and not Designer multi artboard file. For example, work in Publisher on a multi-page file, hit 'Edit in Designer' (not Designer persona) ... use those arrows in the bottom left corner to switch between pages in Designer. You should be able to add discrete slices to each page. When done, hit 'Edit in Publisher'. Edit some more. When you go back to Designer, the slices should be where you left them, per page. Hm, come to think of it... I have never tried to put slices on Master pages in Designer 🤔 ... maybe that would lead to some beautiful solution/destruction?
  6. Thanks @Old Bruce and @prophet for your replies. Symbols are reasonable path to consider, but symbols have two-way synchronization which includes content. In effect, prohibiting customization of each symbol AND retaining master layout control. Once broken, synchronization will not be active anymore. Assets are not good either, they have no synchronization. On the other hand, adding additional master pages (as described in Help documentation) allows for customization of content (image frames, text frames with styles, etc.) while keeping the layout. Masters are synchronized one-way. I.e. modifying master page objects will change the publication page objects but not the other way around. And it will not replace content user placed on the publication side. This use case makes it quite different from symbols. To put this in ice-cream packaging series scenario: Adding multiple individual masters to one publication page allows for placing a different image to each of the image frames for each master applied onto a huge publication page (e.g. place a Chocolate image in 'main-image' frame, then Vanilla cream image to 'main-image' frame next to it, and so on... ) AND having a continuous ability to e.g. widen 'main-image' frame in master page and see that all of the frames have been widened accordingly with discrete images! That (I believe) is powerful.
  7. Yes, please try ... I have been using slices in a multi-page context for a quite some time to my advantage. One example being exporting in one click: custom-sized/custom-named bitmap slices for 3D texturing, PDF for prepress and trimmed JPGs for client preview. From my experience, slices behave fine and reliably in a multi-page context. One small inconvenience perhaps 'Continuous export' option being applied per-page rather than file-wide and user should go through pages and check 'Continuous export' for each page. This is an inconvenience in a relative sense, really. Rather a control feature. Since a file-wide 'Continuous export' in a file with a lot of pages could hypothetically produce an immense amount of unwanted files. Somehow I expected slices to be propagated on newly generated pages since I consider slice definitions to be a part of the original page definition just like margins, guidelines, baselines or bleed. And there is a reasonable purpose for propagation: slices on newly generated files would help me achieve multiple exports described above much faster. ... I might be wrong in thinking this. It is only my expectation.
  8. Yes, @Old Bruce thank you. That indeed would be the quickest way to re-construct lost work and, following your idea, I did use it. However, it is my expectation (belief?) that unnecessary, and perhaps workflow ruining, loss of user work should not happen to begin with.
  9. ...And I really feel that disappearing column guides when adding a master page to a publication page could be a bug.
  10. Case 2 would be something like the ice-cream packaging series workflow mentioned above where this: ...once a slight master spread adjustment is made, turns into this: While I am expecting something like below, instead... Akin to what I would get with any placed page or graphics.
  11. I am using it because it is there 😃. But, above all, it is a very convenient way to work, really. When working on 10 ice-cream packages (vanilla, strawberry, chocolate, stracciatella, etc.) all 10 packages are displayed in front of me. Seeing the whole series at once helps me in achieving design consistency overall, spotting gnarly layout spots. If any master adjustments are made, the effect is visible at the same time. No page scrolling. Add to that a layer of Data Merge Layout and it becomes ... amazing. Masters provide editable structure, data merge variables... Export via Designer slices for print, for preview... @prophet splitting each ice-cream in it's file (or per page) is a valid way to go, but it implies file hopping when adjusting master. Using assets is also not an option. InDesign allows multiple pages per spread, which can be used for ice-cream packaging series scenario. @Old Bruce, regarding expectations when using mismatching spread sizes between master and publication page: Since a master (layer set) once applied on a publication page can be: positioned (X,Y), rotated, scaled, skewed on a publication page using conventional Transform methods, like any other object. assigned an Anchor point, like any other object, renamed, scaled, hidden and locked as any other object, I would expect it to behave like any other object. User operations should be preserved. Just like position, scale (in relation to anchor point) etc. are preserved when we are working with symbols or placed graphic. Imagine this case: 1) One master is applied across pages, but positioned differently on each page (gray). Corrections made to objects within the master propagate across pages but do not disturb positioning and rotation. This is entirely doable and works beautifully. 2) Now, let's add one more master to this publication's pages (reddish). This works beautifully, too. One can even flow text between masters on one page. 3) Master is changed, a detail was added that requires a slight spread size adjustment (green). Now, this happens. The content is moved to the center of the publication page. Some user work is lost (and Undo does not work): 4) I feel the above should not happen. Instead I would expect this: I am aware anchor points are not object-level persistant.
  12. To be able to put multiple additional masters on a publication page is pure genius. (Look in Help for: 'To apply an additional master page to a publication page' in 'Applying master pages' article). This superbly useful feature has saved days of my time by now. Example: Put 10 instances of individual packaging master pages on a huge publication page next to each other, see it all at the same time, and then place graphic variables into master frames is gobsmacking. Moreover, using Data merge layout on that huge publication page and seeing the content move synchroniously and being populated automatically with nutritional data and other packaging related content using Data merge it is pure magic. Now, that 'but' part... Problem 1: User layout is not preserved context: Add several individual master pages to a huge publication page. Position them next to each other. Edit individual master spread dimensions. Click 'no' to 'Target pages differ in size to the master. Would you like to resize them to match?' And... problem: Ugh. Back on huge publication page your nice distribution of individual master pages is gone. Individual masters are moved to center. Stacked over each other. Must be moved back by hand. Locking individual master pages on the huge page does not work either. expected behaviour: Individual master pages placed on a huge publication page observe Transform X,Y position and Anchor Points as defined in huge publication page's Transform panel. That is why user defined them. Ignoring user's work is never cool. Zero/origin for dimensioning master page's spread is center. But, once placed on a publication page, individual master X and Y position and Transform Anchor Point can be defined. Why are they not observed and layout preserved? Problem 2: User column guides' settings are not preserved context: Define column guides on your huge publication page. They will help you layout additional multiple individual master pages. Alt-drag individual master page onto your huge publication page. And... problem: Where are my huge publication page's column guides? Deleted. Shucks. You have to make them again and they will work fine until one attempts applying additional master page. Why were column guides deleted in the first place? expected behaviour: Noli tangere ... column guides... meos! Leave my column guides alone. Deleting user data is never cool. Now, if huge publication page was applied e.g. huge master page with column guides, those master column guides would have been preserved. Are these issues a result of a bug or a feature? An example with instructions is attached... Additional masters issues.afpub
  13. Thank you @Old Bruce for this workaround. I have done so and will see how it goes. I cannot find a reference for this behaviour except a case on Windows a few years ago. There, the problem was caused by certain PDF elements and the behaviour was accompanied by high CPU usage. Here this is not the case. This could still be a bug.
  14. On all 1.10.5 Affinity betas, almost each time when I am closing the file with imported-placed images I get a warning: "At least one file is currently being opened. Please wait for files to load before quitting the application." Nothing is loading as far as I can see. And it never stops. Nothing untoward visible in the Activity monitor. Is it something others see, too? Or, am I embarassing myself again with a lapse of patience/punctiliousness/common sense/ and so forth... On mac OS Monterey 12.2.1 and Mac Mini M1.
  15. @garrettm30 You are right. I was not patient enough. Preflight dictionary error disappears after a moment or two if I switch text language to "None". I will correct my post and go rest.
  16. Yes, @garrettm30, the starting point is a bit of a conundrum. We do have to start from somewhere, and it is likely going to be an incorrect starting point. I vote for 'Prefer None' as well as application default (and no guessing shenenigans!) and of course ability to change that to a preferred language. To add to your proposals, improved documentation would help a lot already. Or, that Assistant notification thingy (the name escapes me) could be used to direct user attention to this. Or, my preference would be, just not engage spell checker until User defines language for some text. Logic here being 'I'd rather see no errors than irrelevant/wrong errors', and 'how dare you detect errors against None language based on misconstrued language variant, you cheeky software!' <- edit: see the following posts.
  17. (did experiments with fresh eyes) Oh. I see. Oh... All of the language dictionaries are available all the time and utilized depending on Character's language definition and pertinent options used. That is exactly what I desired. How... unexpected (?) 😲. Then, the source of (my) confusion was: Language dropdown under 'Replace text while typing' in 'Preferences/Auto correct' is not following the convention established by the rest of the 'Preferences' panel. Every other dropdown element is used to set a preference. Dropdown here does not set any preference. It is only a shortcut to a specific list of custom auto-correction/text-expanding entries that are added to the language selected in the same dropdown. I.e. selection here does not matter while working. All of the entries are available if language needs it. If that is right,this is a bit 'on the edge' case for a dropdown. Some extra explanation could make it easier to understand, like this?: Actually, if on, AP auto-replaces only the entries listed here. Misspelt words will be underlined red. At least, this is what I am getting on Mac. 'Main menu/Text/Spelling/Check spelling while typing' is on, as is 'System preferences/Correct spelling automatically' +Croatian spelling dictionary is present and active system-wide. But, it does not show up here (it does show up for 'Typography language' and 'Typography script'). Maybe that dictionary is not up to the mark needed here... That leaves only awkwardly named 'None' list for my puny little language. Custom named list would be nice... ... To everyone, sorry for attempting to expound on this, entire official documentation on this topic is: "Use these options to control how auto-correction intelligently and automatically replaces or formats your art and frame text". The issue with Preflight 'Missing dictionary for language en-XX' still exists.
  18. An old thread, but still very, very relevant. @thomaso condenses it very well: and... App should not assume OS or Affinity GUI languages have any relation or relevance to document's content and full separation here is justified. In language-specific markets, that assumption would mostly be wrong since UIs are seldomly translated in smaller languages; pro users prefer English UI (my observation); the content created is rarely in any of the languages Affinity offers, and frequently multi-language. Additional argument against assuming language on document level is that you have already given us the finest language control imaginable: on character level; which is also a part of Paragraph style's definiton. And finally, an assumption that is incorrect and malformed (e.g. en-PT, en-HR, en-DE, etc.) is worse than no assumption at all. I believe that ideally a new document should not be language-specific - 'None'. ... Now, that Auto-correction in Preferences is another thing completely. I cannot grasp where is it positioned in the context of language control and language tools. I believe that Auto-correction should be more like: WHEN 'French' THEN 'Auto-correct: French', and not a specific, application-level preference. Especially not one that does not (or does it?) have effect on other language settings in Publisher. ... For fun (and perhaps for an indication that something is broken) look what I see for spelling language: a separator 😆. So symbolic, considering my location, Croatia.
  19. I can see you have done this before :).. Thank you! The curse might have been be lifted... Yup. Turned the thing off/on. My generation still does that first... 😉 I just cleared ALL user data (thanks!) and the crash above cannot be reproduced! Yay! Good tidings. Now, this one is interesting. Preflight says: Missing dictionary for language 'en-HR'. I am in Croatia (Hrvatska, ISO code: HR), but I am not aware of ISO language code 'en-HR'. Then again, I do not know much. My mac OS is using US English (with local preset formats for currency, decimal points, etc.). AP Preferences/Auto correct is set to 'English'. Perhaps some unfortunate hybridisation? @Old Bruce, I really appreciate your guidance, experience and spending your valuable time on this. Oh, on a side note... triple 'Toggle Full Screen' shortcut disappeared, it seems... Spoke too soon. Tripple 'Toggle Full screen' is here even after clearing all of user data.
  20. @Old BruceThank you for replying and providing a valid path for investigation... Since I am training myself in font scarcity I only have system fonts plus <10 added fonts. No font managers. Furthermore, no user swatch palettes, assets, styles etc. have been imported. The only background app I am using is Syncthing, but AP crashes even without it running. Pretty vanilla mac OS: SIP enabled, no hacky tricks, no helpers, no background apps, no kexts, no external devices beside Bluetooth Logitech keyboard and an Apple mouse (no Logitech 'Options' software installed); I own Wacom Intuos, but I disconnected it for testing this. I can reproduce the crash consistently. Start Publisher Beta. It starts in separated window mode. Cmd+N — New document... I choose A4. Hit 'T' to get Text frame tool and paste some text in it. Like this: Click on 'Text frame pane' button in the main bar -> Crash. I have gathered a few after-crash Problem reports in txt format.
  21. I find this Beta to be extremely unstable on Mini M1, mac OS Monterey v12.2.1. start a new file, paste 3 lines of simple text into a Text frame, click Text Frame button in the bar -> beachballing. start a new file, click menu item: Toggle Full Screen -> beachballing. add a text frame to a new file, edit text frame's baseline grid (on pane, this time) -> ball! edit tables -> beach time! look at that ball go! data merge, update -> spin, spin, spin.. and many others. It takes a while until it properly crashes and Mac generates a report. Still, I have a report copied (the one that usually goes to Apple)... let me know if it would be alright to post here. The key question here is: Am I cursed? 🙃
  22. 'Edit in Publisher' and 'Edit in Photo' commands are not present in Designer's 'Export persona'. Quite often I am in a workflow where I am using Publisher layouting goodies and 'Edit in Designer' to setup slices for that work. Many times I need to pop back to Publisher to make a correction. Muscle memory hits 'Edit in Publisher' shortcut, but my ears are met with an error ping. Argh, click back to Designer persona, hit the shortcut again... Needy git aren't I? Still, this little stumble could be polished by adding these commands, no? Perhaps there is a deeper reason why these commands are not included in Export persona that I am not aware of. Well, they do exist in Pixel persona.
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.