Jump to content

WhiteX

Members
  • Content Count

    98
  • Joined

  • Last visited


Reputation Activity

  1. Like
    WhiteX reacted to Oval in Slightly messy Expand Stroke   
    Please, is there hope, an answer for retrograde after one month and what is exactly meant by “soon”?
  2. Like
    WhiteX reacted to evtonic3 in Slightly messy Expand Stroke   
    Maybe you can do it like iDraw?? Just trying to help. looks like they are copies of the original path, inset and outset.


  3. Like
    WhiteX reacted to Dziggolo in Expand Stroke Needs Work   
    Any clues when this bug will be fixed? This is something that prevents me from moving to Affinity from IL...
  4. Thanks
    WhiteX got a reaction from RGerhart in Remove Artboards Gray Border (Option ?)   
    That's the exact same problem I had / have, just with the A4 print size. Either of the provided print templates convert to whole pixel units unfortunately. What I do in such a case is, I create an artboard with a print template (A4, Letter, etc), then I change the document units to pixels, change any values to whole numbers (coordinates and sizes), and that's it. The document will have virtually the same physical size. Any printshop should accept them.... but this is still a workaround.
    In your case you can create the artboard in the desired size in inch or other units, and before exporting, just switch to pixel units and correct the numbers.
    I'm not sure why can't be this done automatically during the export, but it would be great if we could just take care of the design work. In an ideal world we would not have to deal with pixel peeping / tweaking in a VECTOR app...
  5. Like
    WhiteX reacted to RGerhart in Remove Artboards Gray Border (Option ?)   
    Thank you so much @WhiteX
    That explains why one artboard line is not as strongly visible as the rest.
    But I am not sure exactly how to avoid this issue, because I need a certain exact inch-size for my artboards to be accepted for print. So I form the artboards by entering the exact measurements I need for my final results.
    I had not been aware that entering an inch-measurement does not result in full pixel-artboards and causes such a strange issue.
    Thank you very much for your help and I agree with you, a fix for this is urgently needed!
     
  6. Like
    WhiteX got a reaction from RGerhart in Remove Artboards Gray Border (Option ?)   
    @RGerhart I complained about this too. There's no fix, there are only workarounds...
    You need to have your artboards positioned at whole pixel coordinates and they need to have whole pixel sizes. This "fixes" the issue.
     
    Serif, we still need a real fix to this. Thanks.
  7. Like
    WhiteX got a reaction from waveman777 in How do I warp text in Affinity Designer?   
    Come on, it's been two years since we wait for this feature  It's really important! Any news?
  8. Like
    WhiteX reacted to AffinityAppMan in Real Perspetive Mockup with AD   
    Yes, what we need is a VECTOR based perspective filter in AD that doesn't rasterize the objects. Where we can also apply the perspective filter on a GROUP of vector objects at the same time.
  9. Like
    WhiteX reacted to mandisa222 in Envelope warping, object-distort, perspective tool or fisheye tool?   
    Hey, it's 2018 now, this topic was started in 2015. Can you guys at least give an estimated time as to when the warp text will be a feature? This tool is extremely important when designing logos for clients. 
  10. Like
    WhiteX got a reaction from CartoonMike in Compatibility with Suitcase Fusion...   
    Sorry for resurrecting this topic, but now it's more relevant than ever.
    I think this is a great idea, so anyone who is an Extensis customer or is thinking about purchasing Suitcase Fusion, please contact them: https://www.extensis.com/contact/ and let them know that we really need font auto activation for Affinity Designer / Photo / Publisher (and the rest that comes). Using Application Sets is not a viable option.
    I just did that. Let's create some momentum.
  11. Like
    WhiteX reacted to juliantentori in How to edit smart object mockup in affinity photo?   
    Hi! I just purchased affinity photo and designer, using Place embedded document works alright for doing what I want in my mock-ups, but I want to apply a pattern to a MUG, but the warp Mesh Warp Tool rasterizes the whole embedded document, is there a way to warp the embedded document without rasterizing it? That would enable us to apply a design to circular objects and have instant results as how is going to be.

  12. Like
    WhiteX reacted to CartoonMike in Compatibility with Suitcase Fusion...   
    After an exchange with support from Extensis, I got word that if enough people ask for Affinity Designer support, they'll consider it. So consider this a call to action. Because to truly make cracks in the Mudhouse's (i.e. the big red A) monopoly, those of us who dare to ... ahem... work different, need to make a wee bit o' noise. 
     
    I think that if enough of us AD/AP users politely ask Extensis about supporting Affinity products, we just may get it. Then when Affinity Publisher (or whatever it ends up being called) rolls out, the trinity of Affinity products could very well have some nifty font support. Not having auto-activation for fonts via Suitcase Fusion is a bit of a drag (have to manually turn on the fonts...you know that drill), so this does engender a bit of hope.
     
    Considering the Windows version of AD is a-coming, the time could be right to make some fuss about getting Suitcase support in AD. 
     
    What do you think?
  13. Like
    WhiteX reacted to SarahMills in Embedded font not exporting correctly to pdf [Affinity Designer]   
    Hi Mike, 
     
    I deleted and installed the fonts. I don't use a font manager (perhaps I should), just install from the context menu. I did wonder if removing Designer and re-installing might help.. not sure. Command prompt stuff is a bit beyond me.   
     
    Edit: Went into Windows Registry and deleted all 18 fonts, then rebooted and re-installed the fonts. Montserrat Medium is now exporting fine, but Montserrat Regular is still garbled.  Not sure if it's relevant, but I loaded up the file before I added the fonts back, and it was looking for Montserrat regular twice. Which seems odd. 
     
    My search continues !
  14. Like
    WhiteX reacted to 4dimage in AD export to PDF, text with font Roboto Light is destroyed   
    Hi Chris,
    thanks for your reply.
     
    I got the same error with the public Beta.
    1) I installed the latest beta 1.6.3.99 and exported the AD testdocument. The effect was stil the same - text with Roboto Light was broken in the resulting PDF document.
    2) I deleted all Roboto fonts from my Windows, downloaded all fonts again directly from google fonts and installed them. Then i opened the AD testdocument with the Beta version and exported again to PDF. The same error occurs with Roboto Light.
    ---
    Then i had an idea!
    In the fonts panel i switched the language explicitley to German.

    Since then the error with the testdocument is gone!
    I went back to the release version 1.6.2.97 and now the error is also gone. Now even new documents that use Roboto Light export correctly to PDF. And this works regardless which language i now choose in the fonts panel. Very strange, maybe some font caching effect... ?
     
    But - I also tried to export my orginal webdesign in which i detected the PDF error first. With this document now all Roboto Fonts are exported correctly but another font in the upper left logo is stil broken. In this case the font for the logo is "Univers 55" (Type 1). I also typed in the two words again. Same effect. Changing the font family to Arial or Roboto solves the problem. But it's a logo and has to use exactly "Univers 55".
    The original view in AD is this:

    But the exported PDF looks like this:

    The same error occurs in the latest Beta 1.6.3.99.
    I guess there is a serious bug. Maybe from character encoding? On one hand it's strange enough that switching the language in the fonts panel once (first time after installation) will "solve" some font problems in general. On the other hand it seems to be unpredictable which fonts will stil produce errors at the end.
    Don't missunderstand - but Affinity Designer as the WYSIWYG "Editor" in which i created the text shows my design correctly. So i must be shure, that the exported PDF looks exactly the same. Otherwise the PDF export feature is rather useless. Imagine, i work on a design for hours and days and at the end i get errors trying to export a PDF that is meant to present the artwork to my client.
    Not really helpfull, isn't it ?
     
     
  15. Like
    WhiteX reacted to IanSG in Dictionaries and spell check   
    It's easy!  The Hunspell dictionaries are provided as 2 files named something like aa_AA.aff and aa_AA.dic.  These files are placed in a folder called aa_AA which is under the additional dictionaries folder.  "aa_AA" is just an example - the actual filenames will depend on which language you're using.  Some of the dictionaries are supplied as .xpi files - these are Thunderbird addons.  In reality they're just zip files, so you just need to rename the file extension to .zip and then unpack them.
     
    You can find a load of dictionaries here and here.
  16. Like
    WhiteX reacted to IanSG in Dictionaries and spell check   
    So the question now is what format do the Affinity programs expect the dictionaries to be in?  I've tried a couple of Hunspell ones and they didn't work.
    <edit>
    Looking at the dictionaries that Affinity is supplied with, it seems they are Hunspell!  Just make sure the dictionaries are in the correct folder structure!
  17. Like
    WhiteX reacted to Alfred in Dictionaries and spell check   
    We’re talking about two different things here. Support for UI languages has to be built in, but spellchecking need not be limited to those languages. Serif PagePlus, for example, has (as supplied by Serif rather than WinSoft International) never offered more than four UI languages; however, the dictionaries for spellchecking the text in a document have long covered about a dozen languages, and latterly there has been a Hunspell option allowing the installation of additional dictionaries for many more languages.
  18. Like
    WhiteX reacted to Vicente Sarmento in spelling check   
    "Check spelling while typing" could be relabeled: Spelling ON/OFF.
     
    Easier, simpler... no? Anyone?
  19. Like
    WhiteX got a reaction from PaulAffinity in CPU load.   
    There's a possible fix to this. This is what worked for me... I think this problem appears on nVidia GPU's only.
     

  20. Like
    WhiteX got a reaction from PaulAffinity in CPU load.   
    Update (12.13.2017):
    Spoiler: I found the problem (at least for me)
    So here are my findings after some new testing with these versions:
    AD Latest Stable (1.6.1.93) Win
    AD Latest Beta (1.6.3.96) Win
     
    Both versions of AD does the same. High CPU load almost all the time. After trying every possible Performance setting, not running any apps beside Affinity (closing even the web browsers), the weird behavior did not change. CPU still jumps to 80%-90% if I start to move around the canvas (doesn't matter if I zoom in or just pan around, CPU spikes immediately, and stays high).
     
    Long story short, AD completely changes behavior if I have more than 3 files loaded. With 3 files, everything's nice and smooth, no excess CPU load. BUT when I add the fourth file to the mix, this weird behavior starts. Even if the 4th document is empty. When I close one of the files, and I'll have 3 documents open again, CPU drops to normal. When I pan / zoom, it goes up as expected, but drops again when idle.
     
    So, what's the thing with the 4th file? I usually load around 10-15 files in AD, all of my ongoing projects. With AD 1.5 this wasn't a problem.
     
    P.s. Sorry for double post, just wanted to make sure you'll see this.
  21. Like
    WhiteX reacted to vovkasolovev in Bug: Expand Stroke has very low accuracy   
    The accuracy of the Expand Stroke is so low that it does not allow you to use it for precise work, like making SVG icons for Retina resolutions, where all theres mistakes become obvious.
    Check out two video examples about straight lines and circles.
    2018-03-28_11-44-37.mp4
    2018-03-28_12-05-01.mp4
  22. Like
    WhiteX reacted to MEB in Segment tool AD 1.6.4.104   
    Hi Max N
    We are already aware of these types of issues when the shape's edges overlap. Hopefully this will be fixed in a future revision/version.
    Meanwhile here's another way to achieve the desired result:
     

     
     
  23. Like
    WhiteX reacted to Ben in Reset Bounding Box   
    This is not as straight forward as you think.
     
    Each object has what we call a "base box".  This is essentially the box that defines the bounds of an object, and what is post-transformed to put the object into the correct position.
     
    The geometry of some objects are defined by their base box - such a shapes and text.  The internal box is used as the container into which the geometry is created.  Curve objects can easily have their transforms "baked", but for these other dynamic objects, the base box provides a continuing reference for edibility.  So, for example, you can always reselect a shape object and fix it's rotation or shear - you don't lose the transform used to create your shape, or its editability as a shape (as opposed to converting to curves).
     
    Another issue is that some shapes and text are adjusted to fit their box based on their absolute positioning and size.  Rounded corners on rectangles are sized based on their on-page base box size and shear.  But, most importantly, the transformed base box ALWAYS contains these rounded corners.
     
    Now, if we provided an alternative user-defined box, based on the current transform of a dynamic shape, what happens if you apply a further transform to the shape?  The box you have may no longer contain the geometry as the transform affects the corner geometry which could now grow outside of the user-defined box.  Combining this with snapping, you now have a disconnect between the box edges and the geometry bounds that will be snapped.  I can almost guarantee that users will then complain that "snapping is not accurate" - when what is actually happening is that the geometry bounds and the user-defined selection box are not consistent.
     
    If there is to be any more consideration of this issue, I think people will need to provide use cases to illustrate exactly where their problem is.  It might be that it just needs a different approach, but there might also be something we can do.  Bear in mind, however, that we have a wider understanding of the implications of the feature that you may think is trivial.
     
  24. Like
    WhiteX got a reaction from Mark Ingram in CPU load.   
    There's a possible fix to this. This is what worked for me... I think this problem appears on nVidia GPU's only.
     

  25. Like
    WhiteX got a reaction from davision in Zeplin.io integration/cooperation   
    +1 here. I hope Serif will consider to give UI designers a solution (Affinity > Zeplin / Avocode).
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.