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

loukash

Members
  • Posts

    6,101
  • Joined

Reputation Activity

  1. Confused
    loukash got a reaction from Evehne in Add extrusion into Affinity Designer   
    Is it?
    I had extrusion in Illustrator since version CS3, and I haven't used it once.
    Nice to have for sure, but definitely not "essential".
  2. Like
    loukash got a reaction from PaulEC in Add extrusion into Affinity Designer   
    Is it?
    I had extrusion in Illustrator since version CS3, and I haven't used it once.
    Nice to have for sure, but definitely not "essential".
  3. Like
    loukash reacted to Frozen Death Knight in Allow custom macros to be keybinded   
    Title is pretty self-explanatory. Macros would be overall more useful if keybinds were possible.
  4. Like
    loukash reacted to Callum in Just bought Affinity Universal License. Any Adobe Lightroom equivalent?   
    Hi Clarus,
    We don't currently offer a DAM application but its something we would like to consider for the future.
    Thanks
    C
  5. Like
    loukash got a reaction from walt.farrell in How to replace a space in regex?   
    Ah, yes, I missed the "regex" in the title.
    I remember having been involved in a few similar threads in the past: 
    https://forum.affinity.serif.com/index.php?/search/&q=non-breaking space&quick=1&author=loukash&search_and_or=and&sortby=relevancy
  6. Thanks
    loukash got a reaction from Petar Petrenko in How to replace a space in regex?   
    Find: space character Replace: Loupe menu → Special Characters → Non-Breaking Space
  7. Like
    loukash reacted to ShelleyH in Naming new files.   
    Hello.
    This request comes from bouncing between Photoshop and Affinity photo. In Photoshop when you create a new file you can name the file at the same time, which is very convenient. In Affinity having every new file named 'Untitled' is a pain. I know I could 'save as' but, you know, workflow......
    Please think about it....okay?
    Ta.
  8. Like
    loukash reacted to GarryP in Naming new files.   
    It seems like we have opposing views which can’t be reconciled so I’m prepared to end this discussion and ‘agree to disagree’ before it turns into nothing more than a ‘shouting match’.
    -----
    @ShelleyH This sort of ‘back and forth’ discussion/argument goes on all the time in these forums. People have different ideas about what’s ‘best’ and sometimes those differences cannot be resolved in any meaningful way.
    In the end it doesn’t really matter what is discussed between forum members here as Serif have the final say about what they want to do with their software. If they think your suggestion a good idea then they may implement it no matter what any forum member thinks, or they may decide to not implement it no matter what any forum member thinks.
    Serif often listen to what we users say but we don’t have any real agency in what happens, so please don’t let any ‘heated discussions’ deter you from making further suggestions. As to what happens with the software, the only opinions that really matter are those of the Serif staff - it's their party and they choose the music.
  9. Like
    loukash got a reaction from debraspicher in How avoid this with vector shapes in Affinity Photo ? (same sized rectangle in 210x297mm document)   
    Do not use page/artboard/canvas sizes with integer mm values because mm will barely ever match pixel as integer. In fact, you can only make them match if you'd be using non-integer DPI values which is – as far as I recall and likely have already reported it as a bug – broken as of v2.
    E.g. at 300 DPI, to have an ±A4 page with integer pixel dimensions 2480×3508, the mm dimensions must be 209.973333×297.010667. That's precise enough for literally any use. And that's also what you'll get if you create an "A4" canvas at 300 DPI in Photoshop
    But don't worry much, Affinity's New Document dialog can do all the necessary math you need. Just use Pixels as your initial document units and make sure to round the dimensions up or down to integer.
    Caveat:
    Due to a bug in the "absolute pixel grid" concept, if you're using bleed e.g. in Publisher, its initial dimensions also must be integer pixel, e.g. 36 px which is 3.048 mm at 300 DPI. This value must be defined while creating the document, since the potential offset that causes the antialiasing cannot be fixed later. Again, there should be several posts or threads (with my contributions) somewhere in the forum on this very topic.
    You can always seamlessly switch back and forth via File → Edit in Designer/Photo as you see fit.
  10. Like
    loukash got a reaction from Old Bruce in We Need Flexible Font Categories   
    When I got the new MacBookAir running Ventura earlier this year, the first step I did regarding any font management was to figure out which system fonts can I disable right away. Then I put them all into a Font Book Collection which I named "Disable!". It contains a whopping collection of 153 typefaces, from "Adelle Sans Devanagari" down to "Yuppy TC".
    I disabled them all and haven't looked back.
    That has shortened the maddening font list by quite a bit.
    As for Affinity, the first step there was to add my favorite fonts to… wait for it… the  "Favorites" menu!
    Amazingly enough, it helps.  
    As for other custom Font Book collections, I have a few basic ones, but since I don't use Font Book for font management otherwise – and thus 3rd party fonts remain invisible to Font Book – I never spend much time on them.
    Sadly, the FontExplorer X app as we knew it is dead, so on Ventura I have opted for the Typeface app because it allows at least partial import of FontExplorer collections which I have maintained for almost two decades.
  11. Like
    loukash reacted to LondonSquirrel in We Need Flexible Font Categories   
    Maybe because these are graphics programs, not font management programs?  Font management is actually a suitably large subject that commercial applications exist to do that.
    I agree that having a lots of fonts installed needs some sort of management. But this is like the DAM requests for photos. Font management built into the applications is not even on my wish list. YMMV.
  12. Like
    loukash got a reaction from PaoloT in Unexpected Feature: Vectorize a Bitmap Image Directly in Publisher   
    Works perfectly for vectorizing bitmap QR codes:

    If the image doesn't have transparency yet, all you need to do is:
    Place the QR code image in Publisher and select it with the Move tool Context toolbar > Edit Image Switch the opened image to the Photo persona Flood Select tool > Contiguous: off > click the white background Delete (optionally enable Transparent Background to check if all white pixels are gone) Save (if PNG) or export as PNG (if JPEG, then replace the JPEG in the other afpub) proceed with Wrap Outline as above
  13. Like
    loukash got a reaction from handbooklab in Unexpected Feature: Vectorize a Bitmap Image Directly in Publisher   
    Believe it or not, a rudimentary vectorizer has been included with Affinity from the very launch of Publisher 1!
    Before you get too excited though: it only works on images with transparency, for example 1-bit images with alpha channel.
    But hey, better than nothing, right?
    Place your image into a Publisher document, the more pixels the original image has, the better Select the image and click the Edit Wrap Outline button in the main toolbar Copy Paste = Curves object: there's your image (roughly) vectorized, traced based on the transparency outline Apply fill and stroke as you see fit Optionally convert all the sharp nodes to smooth or smart nodes to make it appear less jagged, clean up as you see fit Tested in APu v1.10.6 Mac and APu v2.0.3 iPad.

  14. Like
    loukash got a reaction from thomaso in How avoid this with vector shapes in Affinity Photo ? (same sized rectangle in 210x297mm document)   
    Do not use page/artboard/canvas sizes with integer mm values because mm will barely ever match pixel as integer. In fact, you can only make them match if you'd be using non-integer DPI values which is – as far as I recall and likely have already reported it as a bug – broken as of v2.
    E.g. at 300 DPI, to have an ±A4 page with integer pixel dimensions 2480×3508, the mm dimensions must be 209.973333×297.010667. That's precise enough for literally any use. And that's also what you'll get if you create an "A4" canvas at 300 DPI in Photoshop
    But don't worry much, Affinity's New Document dialog can do all the necessary math you need. Just use Pixels as your initial document units and make sure to round the dimensions up or down to integer.
    Caveat:
    Due to a bug in the "absolute pixel grid" concept, if you're using bleed e.g. in Publisher, its initial dimensions also must be integer pixel, e.g. 36 px which is 3.048 mm at 300 DPI. This value must be defined while creating the document, since the potential offset that causes the antialiasing cannot be fixed later. Again, there should be several posts or threads (with my contributions) somewhere in the forum on this very topic.
    You can always seamlessly switch back and forth via File → Edit in Designer/Photo as you see fit.
  15. Haha
    loukash reacted to carl123 in Naming new files.   
    Software design should minimise the risks involved in its usage
    When you save an untitled document, you are presented with the screen to name that document
    Adding an option to pre-name your document just adds another layer of risk in overwriting an existing document and adds no benefit to workflow as cited by the OP. The workflow is the same time wise, it's just the risks that are different
    It's like the decision to have Hardware Acceleration on as the default. How many users have had their documents crash and lost work because of this being enabled. Only to have to be told to disable it by other users (and even support staff) to stop losing their work. Like it was somehow their mistake to trust the software to make the right decision for them, when we all know hardware acceleration can make you lose a lot of work if it is incompatible with your computer configuration.
    Serif even disabled this setting for all AMD graphic cards in the early days as they knew there was a particular problem with them but then reenabled it (as the default!) even knowing it would still cause crashes on some devices.
    Software changes that introduce another level of risk need to be evaluated carefully and not just willy-nilly to appease someone that previously used Photoshop or some other software.
     
    1. Customer Service: How can I help you

    2. User: I just opened an old document from last month and it now looks like a document I created yesterday.

    3. Customer Service: Did the two documents have the same document name?

    4. User: Yes, they did

    5. Customer Service: Looks like you used our new supa dupa ability to name your document when you created it, not when you first saved it, like you were previously used to doing. You must have misunderstood the warning telling you were going to overwrite a previous document not the one you specifically named at the time you created it

    6. User: WTF. How do I recover from this mess. I need that old document back now!

    7. Customer Service: The only way is to restore it from a backup. If you don't have a backup then I'm afraid you are totally and utterly screwed.

    8. User: I am going to lose my job over this!

    9. Customer Service: Not my problem pal, we introduced that option to save you 0.002 seconds in your workflow. It's not our fault if you just blindly accept the inherent risks involved when you use our software....... Is there anything else I can help you with today?

    10. User: Yes, sometimes when working on documents they crash and I lose all my work

    11. Customer Service: Sir, just switch off the Hardware Acceleration option we enable by default - for Christ's sake don't you users know anything
     
  16. Like
    loukash got a reaction from j3rry in ui font and icon size is really very very tooooooooooo ~~ small !!   
    Nichts für Ungut, aber ich bin mir ehrlich gesagt nicht sicher, ob deine "Wutbürger"-Einstellung der Sache in irgendeiner kleinsten Weise dienlich sein könnte.
  17. Like
    loukash reacted to R C-R in Menue-Beschriftungen nicht lesbar!   
    I had one of those SCSI models too, but I gave it away long ago. I only had the 100MB disks but even (I think) the ones formatted with the old SCSI model are still readable with the USB one I still have. 
  18. Like
    loukash reacted to NotMyFault in Easy Method to Make Seamless Patterns: No Math, Any Canvas Size   
    Nice and simple.
    but it works only with bitmap patterns.
    you can make a preview live by using symbols in Designer, and 2 artboards: one for the pattern definition, one to use it This will allow to use vector content, too you have snapping active with „move by whole pixels“. This is suboptimal as you can introduce fractional positions and cause blurriness and seams. you state that there is no seam caused. At least I see a kind of seam, it is only barely noticeable as you reduce the size of the fill pattern, this will make it unnoticeable. In case you use the fill pattern in original size, you will see a seam. using canvas in inches (or anything else except pixels as units) will always introduce a seam line at the lower and right edge. I mention the seams topics here because we have so many heated discussion in the forum where users complain about seams, thin lines, dark lines, bright lines at edges, and your tutorial in the current form will cause such issues (again, in the chosen example it becomes covered only because you reduce the fill size by factor 10 or more).
    I appreciate your videos, so don’t take my comments as offensive.
  19. Like
    loukash reacted to TrentL in Easy Method to Make Seamless Patterns: No Math, Any Canvas Size   
    Hi all,
    I just posted a video on my channel about a method for making seamless patterns in Affinity Designer (desktop). I have found this to be one of the easiest techniques:
    Pros
    Works on any canvas size No math or calculation Easy to modify as you experiment with the composition Cons
    No live preview method. You need to manually test the graphic as a fill pattern Let me know what you think!
     
  20. Like
    loukash got a reaction from Talisman999 in Please make EXPORT PAGES the default exporting to PDF NOT SPREADS   
    Agreed, this is highly annoying.
  21. Thanks
    loukash got a reaction from smadell in Currency Effect - a FREE macro (NEW VERSION)   
    Brilliant!
  22. Haha
    loukash got a reaction from Westerwälder in Menue-Beschriftungen nicht lesbar!   
    Was heisst da 30? Wäre ich nochmals 45!  
    Da konnte ich noch mit meinen -5.0 Dioptrien – auch in Form von Kontaklinsen – problemlos 9-pt-Texte auf meinem 15" pre-Retina MacBook Pro lesen! Inzwischen trage ich zum Lesen und für die Bildschirmarbeiten die ca. -1.5 Dioptrien-Brille, die ich mit 14 getragen habe. Sieht furchtbar aus – meine Frau lacht mich immer aus – aber auf Distanz von 20 bis 60 cm sehe ich nun endlich wieder alles scharf, und praktisch unverkleinert! Gut hab ich sie seit 42 Jahren sorgfältig aufbewahrt…  
    Aber zurück zum Thema: Ja, auch mir scheint es, dass das Affinity-UI-Team bei Serif etwas unterbesetzt ist, um es sehr milde auszudrücken.
  23. Thanks
    loukash reacted to smadell in Currency Effect - a FREE macro (NEW VERSION)   
    Updated Version Available (December 2023)
    Recently, @christerdk posted in the "Desktop Questions" forum about trying to achieve the engraved look of U.S. currency. He was given a variety of suggestions (including one or two commercial products). Because of this, I am attaching a macro that I created several years ago and have refined a bit more recently. It is meant to approximate the look of engraved currency.
    The macro uses a number of adjustments and filters, all enclosed within a Group. Because of this, the effect can be turned on and off by simply using the Hide/Show checkbox on the group itself.
    The attached .afmacros file is a Macro Category and therefore should be imported from the Library panel. It contains a single macro (called "Currency Effect"). Once imported, the macro can be moved to a different category, if desired. The macro was created in Affinity Photo version 2.2 which probably means that it will not be compatible with AP version 1. However, since it is provided as a category, it can be imported into Affinity Photo 2 for iPad.
    *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *
    Clicking on the macro will bring up a user dialog in which you can set certain parameters:
    1) Set Line Size (default = 20)
    The macro uses a live Halftone filter, and this will vary the width of the lines used. In general, use larger lines for larger images.
    2) Set Line Angle (default = 30 degrees)
    This affects the angle at which the lines are drawn. Try various settings to achieve subtle but important differences in output.
    3) Set Contrast (default = 85)
    This setting also affects the embedded Halftone filter, and can change the contrast between the dark lines and the background.
    4) Adjust Overall Brightness (default = -20)
    This affects a Brightness and Contrast adjustment, and will lighten or darken the final image, to your taste.
    When you hit the Apply button, the effect is added to your image at the top of the layer stack. Note that the effect contains only adjustments and filters; because of that, it is completely non-destructive. You can make changes to the underlying image and this will not adversely affect the result. Also, you can open the individual adjustment and filter layers to make changes even after you have hit the Apply button.
    Here is an example of a Before and After image, with the User Dialog showing the settings used to create this particular variant.

    *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *
    As always, I am one person using one computer and a single iPad. I have tested this macro on both of my devices, but cannot claim that this testing has examined every possible scenario. Nevertheless, I believe that it will work as suggested. Try it and, if you like it, keep it and enjoy it. It is free for you to use in any project you would like – personal or commercial.
    I ask only 2 things. If you've used the macro, please let me know by posting your impressions. Perhaps, even provide a before and after screenshot. Second, please remember that this forum is a wonderful way to learn, and an even better way to share that learning. Pay it forward.
    December 2023 Update
    The .afmacros file attached below is now an updated category. It can still be imported into the Affinity Photo Library panel (or into the iPad version) but it now contains 3 macros. (1) The original version of the Currency Effect is included. (2) An updated version 2 of the macro is also provided. This update adds a live Ripple filter which makes the engraved lines a bit wavy, better simulating true engraving. (3) There is an Instructions macro, which will place on-screen instructions into your Layers panel.
    Please feel free to download the new file, and to replace the previous Currency Effect category with the new one. Have fun!
     
    Currency Effects (v2).afmacros
  24. Haha
    loukash got a reaction from Westerwälder in Menue-Beschriftungen nicht lesbar!   
    Speaking of UI design:
    Seeing commands like "Speichern unter" (Save as) coupled with the symbol of a floppy disc in the year of 2023 makes me want to bang my head against a wall for no reason.
    Yep, even seen that on Mac.
  25. Haha
    loukash got a reaction from Westerwälder in Menue-Beschriftungen nicht lesbar!   
    But that's a known congnitive phenomenon.
    Also, you can still run analog clock faces on a display. It's not something as abstract as a technology that's not in practical use for, say, two decades or more like floppies on Mac. Back in the day I didn't even bother to buy the external floppy drive when I got my first iMac G3 in 2000. Frankly though, I still had an LC475 if desperately needing to load a floppy from a client.
    Same for pushbutton phones: smartphone displays still use the button metaphor to a certain degree. (Unless you're a weirdo talking to some Siri fairies, of course… )
    Anyway. 
    Back on topic, the majority of Affinity icons are not all that bad.
    By which I mean… "majority" = ">50%"…
    There is room for improvement.
×
×
  • 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.