Jump to content
You must now use your email address to sign in [click for more info] ×

thetasig

Members
 View Profile  See their activity

  • Posts

    272

  • Joined

  • Last visited

 Content Type 

Everything posted by thetasig

  1. thetasig
    Thanks very much @thomaso, I tried your suggestions and the double-click on center does, indeed, center the image. Aspect ratio is maintained when drag the outer handle (I never knew that). And I've always had Lock Children not activated. Using that outer handle all of the images "stay put" inside their frames without shifting - that is going to be a real time-saver for me. Also, now I know I can grab the image borders after double-clicking the image. All in all, very helpful, and I learned a thing or two in the process 🙂
  2. thetasig
    AFPUB 1.8.3, OS X 10.15.3 Configuration: laptop connected to NAS on same network. Resource Manager Collection is on the same NAS. NAS Volume is mounted. The Preferences for AFPUB are set to "Automatically update linked resources when modified externally." Load the program and a document. Now - using an external photo editor, update one of the Images in the Resource Manager Collection (all images are linked). The Resource Manager recognizes that the image has been modified - see screen shot. The auto update of the image itself in the document no longer works. However, you can use the Resource Manager to manually Update (button) the image. Not sure if a networked volume is fair game for AFPUB or not. But since the Resource Manager Collection is recognized and used by AFPUB, I think the auto update should be active and working as well.
  3. thetasig
    Suggestion that the Image Properties Scale to Max Fit actually choose in which dimension the image fits into the Picture Frame and then fit the picture into the frame in that dimension. Often the scale is performed correctly, but currently, the image often ends up partially "out of the picture" and partly invisible and partly in the Picture Frame. The result is that the user must often grab the image center and move it manually into position in that (one) dimension. Often that is all that needs to be done. In some cases one might have to resize and reposition. Three screen shots - one after scaling to max fit and the other after manually dragging the image into the center of the frame, and the third is the original image from the source document (it's just a tad wider). Oh, and just to note, in some cases, the "scale to max fit" to fix the image actually comes out larger in both x and y dimensions than the frame - but that's rare. I haven't been able to capture a screen shot of that yet. And here is a little background. I have two documents open - a source and a target. The images from the source page are copied and pasted to the target as a "group" - then the group has to be moved to a page and made somewhat centered by locking the aspect/relationships and dragging one corner of the group inward to fit a smaller page. During this action (making the group fit a smaller page), any source images that are not already marked with "scale to max fit" will be dragged out of their frames instead of staying intact within their frames (first screen shot shows this). This is why the target images sometimes need to be reset to 'scale to max fit' and centered into their frames. I'm making this a feature request/suggestion, but it may fall into the "bug" category...
  4. thetasig
    If you have File Recovery interval set low enough, when AFPUB offers to recover, you'll will have saved even more recent changes. I use 120 seconds. However, when you have a crash while two documents are open, AFPUB incorrectly says (when you restart AFPUB) that there is only 1 document to recover and it then loads it up. Then it dutifully loads the second document without mentioning it. I would think that the user might want to make a decision about each open document that may be recovered. Or, at least, tell the user that there are "x" number of documents that will be recovered in the session. It's hardly a "bug" per se, but in the interest of being accurate and complete...
  5. thetasig
    Hi Gabe - I tried that copy/paste of the URL of the thread and it came out as plain text - you would have to highlight it, copy it, and then paste it to get to the thread. I'll try it again by referring to that new thread. Well, it worked this time - difference is that I looked at the list of threads, "copy URL" from the blue title, then pasted into here. In the referenced thread, I copied the URL at the top of the browser, then pasted it. Thanks for your help.
  6. thetasig
    Hi Gabe - I was told a few days back that I should just copy the URL for any prior issue when reopening or, as you have requested, to post my feature request in the correct forum. However, I noted that my pasted URL does not seem to be "active" in a recent re-post - so just asking: how do I copy a previous issue reference into a new post - the specific steps - as it is not intuitive to me. Thank you.
  7. thetasig
    Yes, I was using Separated Mode during the testing and the crashes. I have not had any trouble in the "normal" mode. When I am able, I'll try the Merge All Windows option. So far, the normal mode has been satisfactory for my needs.
  8. thetasig
    Please see the referenced issue regarding the built-in spelling and grammar feature that the Mac uses - it's the same, or similar, to what AfPUB is using currently, but without the grammar. https://forum.affinity.serif.com/index.php?/topic/114216-feature-request-grammar/&tab=comments#comment-621349 Thanks for considering using this feature.
  9. thetasig
    Thanks, Walt - I've a lot to learn about etiquette in this forum. Especially that I should not make assumptions about how the forum works. There were just a few older bug reports that had been archived and were still outstanding - so I think I'm finished reporting those. I do appreciate your hint that I should include a link/pointer to the prior report as needed. Cheers!
  10. thetasig
    Well, I certainly can report beta bugs in the bugs forum. I was under the (mistaken?) impression that the beta forum was specifically for reporting beta version-specific bugs. Thanks for pointing it out.
  11. thetasig
    Thank you @carl123 as I had not focused in on those performance tweaks. The settings were at "default" and I've raised them considerably.
  12. thetasig
    AFPUB 1.8.4.648 OS X 10.15.3 I often see the message about excess Persona Disc Usage, especially with two Publisher documents open simultaneously. Is there any way I can control the usage? Is there any way I can observe the usage? I have a large disc drive of 4 TB and 2.77 TB is available. Thank you.
  13. thetasig
    AFPUB 1.8.4.648 OS X 10.15.3 Select text just pasted and sized. Then go to font size and drop down the point list - as you slide up or down the list AFPUB crashes. Repeated on a new document just a few pages long. Text frame with text was copied from another document and then pasted into a new document already open and saved - simple text in a single text frame. Easily repeatable. Note that this only happens when you drop down the slider to select a size. It does not happen if you highlight the current size and type a new size manually.
  14. thetasig
    AFPUB 1.8.4.648 OS X 10.15.3 So that multiple computers can share the same Collections folder, I placed it on a networked volume (NAS). The volume itself has to be mounted, of course, before Affinity Publisher can "see" it. However, AFPUB actually prompts for the first photograph in the Document Resource list - to locate it. You have to navigate to that volume and choose the Collections folder and then the first photo. Now AFPUB prompts for the second file in the Collections. Well, you don't have to identify it, rather, at that point, just cancel. AFPUB then scans the Collections folder and all of the files are now located and synchronized with the document. Suggestion: AFPUB should "know" that the collections folder has gone missing. My suggestion is to prompt to "find the Collections folder" instead of finding the first resource file. This is cleaner and one does not have to figure out that you only need to identify one resource and can cancel the rest. Now - if the Collections folder is found, but resources are missing, then prompt for those files - a two-level check.
  15. thetasig
    AFPUB 1.8.4.648 OS X 10.15.3 Originally posted August 2019. As this is publishing software, it would be extremely helpful to have grammar check built in. Without this feature, one would have to offload the text somehow, check it in some other piece of software, and then manually make the corrections. I'm not sure whether the grammar checking should be "on demand" and/or "as you type." Either way, it's going to be very handy to have built into Affinity Publisher. On the Mac, when you use the Shift-Command-Colon keys it brings up the "Spelling and Grammar" window. The grammar is built into the operating system of the Mac in the user's chosen language. I noted that this is the same window that I see in AFPUB (more or less). See the two screen captures below. I'd suggest that AFPUB be made aware of that for the Mac and be able to invoke the Grammar Check using the check box provided on the Mac Spelling and Grammar window. That means you would not have to create a grammar checker inside AFPUB, just use the operating system's built-in capability. Perhaps there might be something similar in Windows?
  16. thetasig
    I'd like to add to this thread something directly related to the topic. Same beta version and Mac OS X. I've posted three images. The first shows a "breaking hyphen" that is followed on the next line by the range of pages: 133. This should not be happening. Instead the indexing update should insert "non-breaking hyphens". The after image shows the desired result. Considering that the word wrapping should continue to happen as expected (if there was no room for 131-133 a decision is made to break the 133 to the next line but only if using a non-breaking character would move the pair past the right margin). See the third image below for that example of a correctly broken page range (67-69) with a hyphen. The upshot of this bug is three-fold. First, the user must replace the "breaking dash" from the Index update with a standard hyphen (the minus key on a Mac). Then the user has to go back through and replace the en-space with a standard "space bar" space. When all of this is done, the index is proper without dangling or split numbers, and no strange line breaks where they are not needed. An unfortunate result of this is that the Pre-Flight will always report that the Index is not proper and has to be updated. But we know that is not true in this case. Please consider making these changes to AFPUB's indexing update to make publishing life quicker, intuitive, and easier to do. Thank you.
  17. thetasig
    This is a feature request - not a bug. Using AFPUB 1.8.4.648 OS X 10.15.3 Originally posted August 2018, the idea came up with several users that having captions and other metadata for photos for display in AFPUB would be very helpful. Mention was made of AFPhoto that had made use of EXIF data in that regard and hoped that might trickle over to AFPUB. Simply put, use existing, embedded photo metadata to label existing photos with controls for anchoring, positioning, font, style, etc., etc. Here is one concept of how it might be used - you might have to open the publisher document in a non-beta version. https://forum.affinity.serif.com/applications/core/interface/file/attachment.php?id=122448
  18. thetasig
    AFPUB 1.8.4.648 OS X 10.15.3 Originally posted October 2019 in 1.7, the problem still exists. There is a button that controls the vertical positioning of text. Let's say you have your text set to "Center Vertically" - if you pull that menu down you will see that there is a check mark next to "Center Vertically" - if you click "Center Vertically" while it is checked, it changes the positioning to "Top Align" - if you then click "Top Align" it will switch to "Center Vertically". If you select any other positioning: "Bottom Align", "Justify Vertically" and then select it a second time, it switches to "Top Align" - this is silly. What you click should be what you get - always. While the graphic actually shows you what you are getting, if you don't take time to observe the graphic, you may believe that you are getting "what you clicked" - and that is not the case as it keeps toggling ad infinitum. Small bug but easy to screw up your text without knowing. There should be no toggling involved here. See a before - first image. Then Click "Center vertically" and you get "Top align" instead.
  19. thetasig
    AFPUB 1.8.4.648 OS X 10.15.3 First reported in 1.7 in September 2019, this problem still exists. There is one unusual thing about "Spelling Options". I encountered one word that was misspelled and clicked "Learn" and the red line underneath disappeared. I exited the "Spelling Options" and again invoked Spelling Options - it jumps to that same word (last one that was found misspelled) but the word is now NOT underscored. The word is in the Mac English spelling database "en" . The same thing happens after closing the document and quitting AFPUB, then reopening the same document - jumps to that same (not underscored) word. In fact, if you happen to delete the misspelled word (I added a test word "asdfg"), the Spelling Options again jumps to this non-existent word in the text frame where it was originally found (but not after closing and reopening the document). I would think AFPUB should not do any of that and just simply inform the user that there are "no misspelled words" to be found. If there are no misspelled words, the Spelling Options dialogue just sits there quietly showing the last word that was learned - doing nothing. Not very informative.
  20. thetasig
    AFPUB 1.8.4.648 OS X 10.15.3 This continues to happen since October 2019 report. I have a file folder with all the pictures I'm using in the document. They are embedded. Now, when I go to replace a picture with another, AFPUB opens the correct folder but shows that the folder is empty (it's not really empty). You then have to click that folder in the dialogue (normally not necessary) and then you get the list of files in that folder. I have never seen that happen with any other software or when just using the OS X software (Finder). I have only seen that problem with AFPUB and only when replacing a picture. Just wondering if that might be AFPUB or something in OS X (haven't changed OS X version in the past 2 years). I believe that this may only happen the first time you need to replace a picture - and that the whole file list is visible thereafter without having to click the resource folder during the "Open" There isn't much to see - so no screen shot - just opens the folder but doesn't list the files inside - just shows a blank file name column in the "Columns" mode.
  21. thetasig
    AFPUB 1.8.4.648 OS X 10.15.3. I'm not totally sure, but it seems to be the way leading numbers on the names are sorted. Mac and LR sort by the numeric value, then alphabetical, Publisher sorts by, I believe, hex value - or by character value, then alphabetical characters. Thus, "007" comes before "6" in Publisher, whereas it's the reverse on the Mac and in LR. This plays havoc with the user's ability to cross-check and validate Publisher resources against system lists. Can't we have a match of Publisher's sort (everywhere, e.g., Resource Manager, Index, etc.) with the system it's installed on? Thanks! See example screenshot. @walt.farrell replied that LR and the Mac system are using a numeric sort while AFPUB is using an alphabetic sort. I still would love to have my applications match up with the system defaults in that regard. As it is, I can't really change any of them, especially the Resource Manager and Lightroom. Yes, it is possible, though tedious, to capture the system list and then put it into some other application that can sort alphabetically, but having to do that many times over can really eat up a lot of time. The Affinity User Interface should do that by default (system-dependent) IMHO.
  22. thetasig
    Thanks, Walt. You can teach an old dog like me new tricks 🙂 The link to that July 19 topic is:
  23. thetasig
    Glad to hear that - it was an unusual situation. I even checked the two computers' "en" (English) files in the Spelling folder and each had all of the new words in the document to start with. Somehow, the system did not recognize those files during the spelling check. Where those words were recorded internally as they were learned I have no idea. Do you, by chance, know what file AFPUB uses to record new words on a Mac? The only difference between the two computers is that one had a local disk document. The second computer used the same document, but it was moved to a network volume along with a "collection" folder for Resources. Opened the document by dragging it from the network volume to the laptop. Probably nothing special here - I'll report back if I learn anything.
  24. thetasig
    Well, actually, I don't think I have a small document at this point. But I may try to create one when time is available. Also wanted to stress that the software does learn the words if you go all the way through the document. It's just this odd behavior that you have to keep learning the same word over and over and over as you go through the document once. So one might just set up a multi-page document with a repeated misspelled word and check ti.
  25. thetasig
    AFPUB 1.8.4.648, OSX 10.15.3 Catalina Please review this old report - @Pauls had indicated the issue had been logged, but the problem remains in the latest beta version: Text and Index Frames split numbers - have danglers By thetasig, July 9, 2019 in Pre 1.8 Publisher Bugs found on MacOS Thank you.
×
×
  • Create New...

Important Information

Terms of Use | 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.

 Accept Cookies  Reject Cookies