
zkarj
Members-
Posts
58 -
Joined
-
Last visited
Recent Profile Visitors
1,324 profile views
-
Literally what I said. Not at all my point. We both know how it works. My issue was with the implication that Lightroom intrinsically leaves things in place, when it actually gives you a choice. The difference between library files and "free" folders is a different thing. So let's leave it there... Eagle does not have the option to leave in place and does not have "free" folders. If that's a problem, it's not the answer for you.
-
It's a common misconception that Lightroom leaves files in place. It can do, but it can also move or copy them to a folder as they are added to the catalogue. But in any case, Eagle is not the solution for you if you need in-place ingestion, and I can understand why with that kind of volume of assets.
-
Juhani reacted to a post in a topic: Affinity, we need clarification: are you or aren’t you working on a DAM?
-
Yes, it's pretty simple and intuitive, and it looks nice, too. A picture is worth a thousand words. As you can see, nice coloured folders — not real folders, they are stored in a library (a macOS package it appears) — but you can export entire folders as raw content or a separate library. Where it says Design Assets at top left, that's where I can switch between libraries. My one other library is for scans of family history items. Any file can be dragged out of Eagle into any other app as you would from Finder, and you can drag stuff in too. You can see across the top the various types of automatic organisation available, and on the right is information for the currently selected file.
-
Juhani reacted to a post in a topic: Affinity, we need clarification: are you or aren’t you working on a DAM?
-
I've given up wanting this. If something does materialise, I will certainly give it a look, but I find it increasingly unlikely anything produced under the Affinity brand will be for me. I don't have a ton of assets that I need to store for Affinity products. I have two main use cases for an asset manager. First... my photos. I use Lightroom, and if Affinity can produce a DAM of equal quality, I will be very interested. I doubt they will, as they will, arguably should, focus on cross-domain asset management. I suspect you don't need a keyword hierarchy when managing graphical assets. I need it for my photos. Also, my photos very rarely go via any Affinity product. Second is general graphic assets. I've purchased Eagle for this, and it works with anything, including Affinity products. It's only advance over Finder, for me, is a nicer interface that is built for assets, rather than just files. I started out wanting to have an Affinity DAM because I didn't want to pay for Lightroom for just that task. Now I've made peace with that cost in my life. So... too late for Affinity as far as I am concerned.
-
This happened again, but while trying to capture the file state, I seem to have stopped the problem again. To recap: I duplicated an old .afpub file, changed the name, and edited. I exported as PDF, which included all pages (only 2 present). I closed the document. I re-opened the document and made a change. I re-exported as PDF, only the first page was exported. On noticing this in the PDF, I returned to Publisher where the document was still open. The export window showed only one page and re-exporting still only gave one page. I did a Save-as to another location then immediately exported. The window and resulting PDF had both pages. I closed Publisher and re-opened the original document. I exported and the window and output PDF contained both pages. So it seems it will be impossible to supply a file that is exhibiting this behaviour. It appears it is only happening when a document has been edited twice in the same instance of Publisher. Short of dumping the memory state of the application, I don't see how we can get to the bottom of this, but I do at least have multiple workarounds.
- 5 replies
-
- affinity publisher
- export
-
(and 1 more)
Tagged with:
-
Publisher hung, now won't open recovery file
zkarj replied to zkarj's topic in V2 Bugs found on macOS
Thanks. I also forgot to add that I think I know what upset Publisher in the first place. I had thought right-clicking a page thumbnail in Preview and selecting Export would export just that page, but in fact it exports the whole PDF. As such, my TIFF file was a multi-page TIFF. I've had mixed results with such files in various software. -
Publisher hung, now won't open recovery file
zkarj replied to zkarj's topic in V2 Bugs found on macOS
Oh, that's not the complete story. I went off and left it for a couple of hours to watch TV and do the dishes and on return, I see it has finally loaded the file, complete with all my changes, except the PNG file is not there. So I have now managed to save the file in a different (visible) folder in this form. -
What Application are you using? [Designer/Photo/Publisher] Publisher 2 Are you using the latest release version? Yes, v2.2.1, I checked for updates before embarking on the work described below. Can you reproduce it? Yes. Does it happen for a new document? If not can you upload a document that shows the problem? It's a problem with an existing document. Other documents are fine. Steps taken: Opened an older, v1-created publisher document. Responded yes to convert it to v2. Did considerable work on it, including Add new pages (initially 20, later a total of 50) Pasted rich text into a text frame Linked the series of text frames across the 50 pages Applied pre-defined styles to all pasted text Added an image frame, placed an image, and added a shadow All of this went fine and I left it for open for a while. I then came back and created a new PNG file (from a PDF page, using Preview) and dragged it onto one of my added pages. Publisher then froze. The beachball appeared, but it wasn't spinning as it should, rather just 'jittering' repeatedly. I could not do anything at all with Publisher other than Force Quit it. Upon re-launching Publisher, it tried to automatically open my file and again asked if I wanted to convert it to v2. Again I allowed it. It then offered to open the Recovery File and I said yes. At this point, at the top of the window it says "Loading 1 document" but it has been saying that for 10 minutes now and nothing is actually happening. I checked Activity Monitor and Publisher is barely registering CPU usage. I can show menus, switch between palettes and the like, but the document is not appearing in any form. If I try to Quit Publisher, it complains "At least one file is currently being opened" and refuses to quit. If I again Force Quit it, then it goes through the same process again. Convert from v1, yes, open Recovery File, yes, Loading 1 document... except it just isn't. I could replicate all the work I did without too much trouble, as it was basically a simple, repetitive process, but I'd really like Publisher to sort itself out. I can't provide the file for two reasons: It has not been saved in the form it is failing to load, as it is only a Recovery File (I don't even know where that is). Even the original file is in an 'undefined' location, as the "Affinity Publisher" folder in iCloud is empty. I had to find it with Spotlight (in fact via Alfred file search) where it appears in "~/Library/Mobile Documents/iCloud~com~seriflabs~affinitypublisher 2/Documents/My Story.afpub". If I put that path in Finder's Go to folder field, it just leaves me in the iCloud folder. Oh, and the PNG file was 5.4 MB.
-
Annoyingly I cannot reproduce the issue currently. I did just install 2.2.1 which may have a bearing. It should rear its head next time I do a full product cycle which won't be far away. Either 2.2.1 has cured it, or there is some subtlety about the series of actions that result in the issue.
- 5 replies
-
- affinity publisher
- export
-
(and 1 more)
Tagged with:
-
- 5 replies
-
- affinity publisher
- export
-
(and 1 more)
Tagged with:
-
I've had this issue many times in recent months. Here's my workflow. 1. Copy an existing document and rename it, both in Finder. 2. Edit the contents and save. 3. Export to "PDF Print" This gets me a 3 page PDF file — exactly what I expect. 4. Close the document. A short time later, after some proofreading of the PDF... 5. Re-open the document. 6. Make a minor edit and save. 7. Export to "PDF Print" I now get a 1 page PDF. I cannot make it output all 3 pages. The document comprises of: Page 1: Native Publisher content — multiple text frames and tables with text and some small images. All the images are embedded. Page 2: An embedded page from another Publisher 2 document. Page 3: Another embedded page from the same Publisher 2 document. While recreating the steps for this forum post, I discovered how to get it working again. 8. Select the last page. 9. Export "Current page". 10. Export "All pages". That final export does include all 3 pages. I have changed nothing about the document since step 6 so I know it's not me!
- 5 replies
-
- affinity publisher
- export
-
(and 1 more)
Tagged with:
-
zkarj reacted to a post in a topic: Shared content, smaller than a document
-
I think there may be a misunderstanding here, as I cannot get the pinned content to behave as I want. I would like the content of the placed document to be treated as if it's local text, and thus wrapped to the width of the text frame in which it is inserted. It seems that pinning lets the insertion point move with the surrounding text, but the inserted document retains its original flow. All I can do is squash it to fit, deforming the font. In other words I want one document with the wider text frame to show... The quick brown fox jumps over the lazy dog. ...and the other document with the narrower text frame to show... The quick brown fox jumps over the lazy dog. I.e. same font metrics, but different wrap point.