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

thomaso

Members
  • Posts

    11,201
  • Joined

  • Last visited

Everything posted by thomaso

  1. You can't type in Zapf Dingbats like text with the keyboard. If you use the Glyph panel instead the dingbats occur and the ! disappears. It is a quite old issue with Dingbat Fonts on Macs ... 2007: "Apparently in Leopard (os 10.5) fonts with Special Characters (alternate language glyphs like Arabic, "Dingbats" and other symbols, etc) have those Special Characters stored in the correct Unicode group of the font, and NOT in the regular / Latin area. So previously, where I was used to pressing "b" in Zapf Dingbats and getting a certain compass symbol, that symbol is now located elsewhere in the font, and can only be located using the Character Palette." https://discussions.apple.com/thread/1273291 ... and was discussed in AfPub Beta last summer:
  2. @Peeje, you don't need a video: 1. Place the text cursor in a paragraph you want with bullet + indent 2. Click the bullet list button in the context tool bar: Affinity has no such special character "indent to here" like InDesign offers. in Affinity you may assign your own keyboard shortcut (f.i. command+backslash) for this menu command: Text > List > Bullet. So, finally here is a video if you like to learn a bit more about bullet or numbered lists in Affinity: https://affinity.serif.com/en-us/tutorials/publisher/desktop/video/337313778/
  3. 4? It depends what counts ... https://forum.affinity.serif.com/index.php?/search/&q="word count"&type=forums_topic&nodes=5,65,6,56,53,54&sortby=relevancy&search_and_or=and&search_in=titles
  4. ... for Bugs, yes, and for Suggestions & Feature Requests, – but not for Q & A and "How to...". Whereas I guess, the possible learning effect for the user, especially in Q & A / How to..., is larger if they are all together, than it would be in Bugs.
  5. I use a laptop + an external monitor, which is placed not next to but on top of each other. I use AfDesigner in Separated Mode, to be able, to place the tool bar at the lower edge of the upper screen, to have it closer to the panels, which are placed on the lower (laptop) screen. Now it happens occasionally that all these floating windows get mad and are spread somewhere, most of them outside of both screens. It may happen, if I switch persona to afpub and switch back, or if I switch between spaces of macOS. Then the tool bar prefers to hide below the lower edge of the lower monitor and can not – as the other panels - made appear back on screen via setting its visibility on/off in Studio panel but via "Customise Toolbar...". Unfortunately all documents get opened in the lower screen (which has the system menu bar) and there BEHIND all panels. To make such a document window accessible I need to toggle UI off, then move the window to the upper screen, then toggle panel UI on again. My questions: 1. Is it possible, to open documents NOT in the lower screen (which has the system menu bar) and behind the panels – but to force them at their place on the upper screen? 2. Is it possible to use "Merge All Windows" to make a newly opened document take place next to the existing on the upper screen? (instead of make the existing window jump down to the newly opened document window) 3. What does "Clean Up Floating Windows" do in both of its options? (I hazitate using it to avoid a mess and need to rearrange again the bits and pieces) I found this thread from 2017 – 2018. But it seems the UI behavior hasn't changed yet in that issues. – Or do I miss or misuse something? https://forum.affinity.serif.com/index.php?/topic/53744-lost-ability-to-move-tool-panels/
  6. Wow, Thanks a lot, Murfee. – After your initial tutorial above I tried this edit view with the psd, the png and the tif. – Then I gave up! shame on me! Thank you also for the info that it is reported and/or known to the Devs (cause I could not find an according topic in the wide beach of hundreds of sandy topic corns;) Sorry for confusing. I started about AI because it is an Adobe app which is supported quite well in Affinity. That made me wonder, if Adobes clipping paths might possibly not supported in purpose. The connection was simply to be aware of a bandwidth of possible supported features of Adobe apps. But, since you ask: I also had tried a clipping path.ai which was exported from the psd file of my test above: It gets placed in AfPub as a layer named "(Linked document)" but no specific name, as a .psd shows: If I use "Edit Document" I get only one layer named "(Layer") with no content: I assume your explanations about limitations of .ai in Affinity gets visible here. One strange occurrence when editing the .ai: A quite confusing warning about color profiles: It sounds as if I am working in a grayscale document and tried to edit a unprofiled document: Whereas THIS document itself obviously got opened with a grayscale profile by AfPub and confuses AfPub itself by finding content with no profile: The .afpub, where it was pasted in is a CMYK document with cmyk profile. So, the warning is talking about the resource only. I don't know. Haven't you tried? The files are attached in the zip above.
  7. I don't exactly understand what you are asking for. – Two 24" is more area the one 27". So the decision appears not to be a question to me. This sounds like a misunderstanding of you. In both modes, Normal AND Separated, you may arrange the panels on customized positions and sizes on any of the screens. Unfortunately Affinity apps still are a bit buggy if using two monitors. That means you will have to repair your individual panel arrangements occasionally, for instance if you switch to a different app persona and come back or if you switch between "spaces" (as various desktops) within macOS. Then most panels seem to be outside of both screens and hard to get back. It happens not every time but sometimes, I could not detect a rule for this unexpected behavior. I am working with a laptop and have the 2nd screen above the smaller laptop screen. The system menu bar and most panels are on the lower screen, the larger screen above shows the main document window, the tool bar, the tool panel and a few other panels. To be able to place the tool bar at the lower egde of the upper screen I need to work in separated mode. unfortunately every new document opens on the lower screen, behind the panels. Sometimes it does not work to toggle the UI (=hide panels) to gt access to the document window. Then I need to manually move the panels to achieve the window behind and move that onto the screen above. There I have to size it manually to fit to the according area. Meanwhile I use a workaround if the panels get confused: I replace the preferences folder of the app by a copy I had stored somewhere else.
  8. Since Affinity enables me to open an Adobe Illustrator document or even to copy/paste vector objects from a native .ai, I wonder, whether a clipping path, saved by an Adobe app, is read, recognized and supported by Affinity? Or whether it is supposed to support but fails for some reason or bug? A sample with 4 file formats, with transparency (except JPG) + a clipping path: Attached a .zip: 1x .afpub + 4x images with clipping path (from psd) + 1x screenshot of the expected result. Could one shed some light on a general support or non-support of those clipping paths in Affinity? Clipping Path.zip
  9. @R C-R, this is indeed interesting, thank you! – I haven't been aware about this economy in saving a CR2 in the camera. It explains indeed the massive file size increase between CR2 and PNG. Do you know whether still nowadays Canon and/or most brands (RAW file formats) use such a interpolation of 2 colors (R, G and B) and therefore lack of image output sharpness for every single pixel? It reminds me to SIGMA, about 15 years ago, avoiding that need to interpolate because of using a different sensor type, which saved all color information in every sensor pixel: [and resulted in larger RAW file size, f.i. 53 MB (.FX3) towards 26 MB (.CR2)] Experiment: http://www.centralds.net/cam/?p=8561 The color filter layer on a Bayer sensor (as in Canon) was mechanically removed. The result was monochrome (= grayscale) images, but with a clear improvement in sharpness: Back to the topic: this CR2 saving economy means that 1.) a CR2 does not contain optimal information, just by limitations of its sensor and 2.) it is not economic to to archive such a RAW type with a developed / converted (= interpolated) file format like PSD, TIF, PNG, JPG. Since DNG results in smaller files than CR2 I assume it at least does not contain interpolated pixels, and, from this point of view, is a better format for archives. Whereas i don't know yet what makes a DNG smaller than a CR2, I never have read about loss of image quality by DNG. – Did you?
  10. I can use Studiolink with AfPub and AfDesigner retail versions like a charm. – How about Beta? When I try using Designer persona in v420 I get this pop-up window: When I click "Get Beta" then it guides me there: https://forum.affinity.serif.com/index.php?/forum/60-affinity-designer-beta-forums/ – But where do I get the Designer Beta? (I don't see a permanent post on top like for AfPub with the momentary Beta) – and do I really need it? Can't I studiolink to my installed retail AfDesigner from a AfPub Beta?
  11. Now that we have two forums for Bugs on Mac: Should we report issues of v420 again which got already reported for the retail version (v408) ? For instance a reproducible crash on "Save As..." > "Replace" in Separated Mode. Affinity Publisher Beta_2019-07-05-183448_mbp1.crash
  12. This appears to be the answer again: compression. – My post was related to a note that the difference between the 95 MB and the 26 MB might result from different bit depth. Pure bit depth does not result in variable file size, it is clear defined by an amount of pixels and channels. From this point of view, your hints confirm my view that compression is crucial here in this topics question. (... which, by the way, was not at all about the CR2 development process, but about the increase in the developed, exported PNG file size compared to the undeveloped CR2. The content of the output PNG won't contain more relevant data then its input, the CR2.) I don't understand why you compare that with native Affinity documents file size. Of cause such can be much more complex and heavier then one single resource, no question, and I am far away from criticizing Affinities native file size. But since you talk about I wonder why a 26 MB CR2, opened and saved in AfDesigner as native .afdesign, increases to 126 MB, just by saving, no development or any work on it. Interesting: also the 95 MB PNG, opened and saved in AfDesigner, creates an .afpub with same 126 MB. However, it does not disturb me, since I don't plan to use Affinity as a storage container for images. It just makes me curious to understand what's going on inside. – Whereas the apparently uncompressed PNG does disturb me.
  13. Ah, that helps, thank you! – Glad I was in the right of the UI, have been searching in the help for "coordinates" but couldn't find any related to artboards. "300 pixels per inch" Aha again, thank you. This made me finally discover the document settings that I tried to click in the tool bar before, (like in AfPub), while the help did not know DPI or resolution. Actually coordinates are the reason: in graphic computing coordinates are the basic – whereas dimensions are distances between coordinates. This difference counts, especially in AfDesigner, where you may create artboards of various dimensions and place them at free coordinates with free distances to each other. Instead of adding or subtracting relative distances, the system needs only to know absolute coordinates and is, so to say, faster this way because it gets more information by coordinates. Coordinates are unique, distances need to be distinguished. coordinates: 0 10 20 30 distances: | 10 | 10 | 10 |
  14. You can open it in Illustrator and copy/paste its vectors into AfDesigner as vectors. – Quite nice skill of AfDesigner, I guess. The text of your .ps opens in AfDesigner as vectors, and is "read into curves and made to lines" as you requested. The logo part of your .ps opens as vectors, too. More precisely as quite a few vector rectangle layers in the shapes of the pixels in your .ps. – Whereas in Illustrator it opens as simply 1 image layer. Somehow it appears you are neither aware about the content inside your posted files nor what you can get from it in AfDesigner.
  15. I am new to AfDesigner, did only experience AfPub yet. – Do you mean to achieve integers with this button in the middle?: It is useful only with document unit set to pixels, right? For what use is it meant to become deselected if working in pixels? When I toggle the ruler unit from pixel to mm then 1000 px become 84,67 mm. – What is the relation for this calculation?
  16. ShelleyP, can you make your previews appear with these two settings mentioned in the last post: one in Affinity Designer Prefs, the other in Finder (cmd-J)? When you control-(right)-click on a file in finder: what application is on top of the fly-out list in "Open With..." for a AfDesigner document? If it says first Affinity Photo then select an AfDesigner file in Finder > Cmd- i > Open With: in the pull-down menu select your wanted Affinity Designer app version + then click underneath on "Change All". (or similar wordings, because I see it only in my German OS) Restart your mac. Yes! and thanks again. I just changed it in my recent post.
  17. Thank you Bruce, with your 3 parameters I got aware of a 4th condition: Affinity Application Preferences > General > Save thumbnail with documents. Now I can set what I want: – preview in finders list view style: NO – preview w. space (quicklook): YES – preview in finders other view styles: YES
  18. Yes, right. Actually I don't want the finder icon as preview but in quicklook. Remaining in the dark: In my usual finder list I do prefer the Affinity icons: A tiny page preview wouldn't inform me really. With app icon I can distinguish layout files much faster which are stored between exported pdfs. Does for you quicklook show an .afpubs preview in your 10.12. – or in 10.14. only? And if in 10.12., does it show 1 page only (= the preview icon?), or does quicklook for .afpub show more than 1 title picture, like it does for PDFs, emails and movies?
  19. Yes, only export in document color space. – I uploaded 10 jpg + 2 .afpubs (1 RGB, 1 CMYK) (oh, I forgot to add the cmyk .icc profile. Will it be embedded in the afpup? – If not: ECI ISO coated (v2): http://www.eci.org/_media/downloads/icc_profiles_from_eci/eci_offset_2009.zip
  20. Doesn't find any – or not as expected? To me both ^$ and ^\r show quit similar results with this difference: ^$ finds the spot before a break.
  21. Yes, macOS gets confused, kind nasty influenced, by Affinity file types and it needs user action to fix it. I had noticed that all .DNG files and the 2 oldest of .CR2 files want to get opened with Affinity Publisher. Though their file types are neither actually Affinity typical nor do I AfPhoto installed. Also the quicklook preview for real Affinity documents has never worked for me:
  22. Doesn't it make it even more obvious that the PNG file size compared to RAW is not a matter of bit depth? For export, too? – I don't have AfPhoto installed and looked in the AfPub export formats . Which makes me wonder now – in case DNG is in AfPhoto exports – why it isn't in AfPub, where even HDR and EXR are available.
  23. To me on mac it finds only empty paragraphs but only IF they are either at the beginning OR after a line break.
  24. If the CR2 has 26 MB and 12-14 bit per channel, then a file with 16 bit per channel can't increase by its bit depth to 95 MB. Hm? – look: https://rawpedia.rawtherapee.com/Image_file_formats_and_compression This just repeats the initial question. – How about: Affinity doesn't compress natively its PNG exports. Just in case you don't like TIF, mentioned by Walt already: Meanwhile Hasselblad, Leica and even some smartphones support DNG as RAW format, so it might be worth to consider DNG as an archive format to replace CR2. Unfortunately, Affinity doesn't natively support DNG, too. But its HDR appears to result in file sizes between your CR2 and the PNG.
×
×
  • 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.