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

v_kyr

Members
  • Posts

    13,234
  • Joined

Posts posted by v_kyr

  1. 🤔 Snapping via a circle to lines won't really work here (see for example this related thread).

    Other tries/workarounds would be ...

    • to draw your lines with a double (even distributed distance) compound line brush
    • to draw symmetrical with the help of symbols
    • to enhance your line stroke and then expand stroke, afterwards to remove the applied fill and set instead a stroke color. Then remove on both sides the end line nodes which close the whole outline shape
    • to draw one slightly thicker stroked line and use an third-party auto vector tracer to perform an vectorization outline trace of your line drawing
    • ...
    • ... and so on, possible other ways ...
  2. 13 minutes ago, Joachim Digital Art said:

    seit 5 Tagen habe ich ein Problem mit allen 3 Affinity Apps. Nach drei oder vier Befehlen stoppt die App und meldet "Keine Rückmeldung"

    Ich nutze Windows 11

    Ich habe keine Veränderung an meinem System vorgenommen. 

    Du selbst explizit vielleicht nicht, aber Windows update u.U. - Was tun?

    1. Die apps einmal via der NO OpenCL Methode starten ...
       ... und schauen ob das eine Veränderung bringt.

      FERNER nach möglichen generierten crash reports ausschau halten und diese hier dann zeigen ...
       
       
    2. Wenn das nichts bringt, dann das MS .Net Framework checken und gegebenenfalls reparieren lassen ...

      - Reparieren von .Net Framework
      - https://download.microsoft.com/download/2/B/D/2BDE5459-2225-48B8-830C-AE19CAF038F1/NetFxRepairTool.exe
       
    3. Falls das auch nichts bringt, dann die Affinity apps auf deren Initalwerte zurücksetzen ...
       

     

  3. Hmm 🤔, I have the impression that the correction path portion (the connected dashed lines) which is added/connected to the already default straight line path, is overall performed/done in some bitmap result manner. And thus if the dashed correction path portion is left in there (aka not explicitely removed before exporting), the whole then gets rasterized on export here.

  4. 18 hours ago, MikeTO said:

    Photo's default tool is the View tool. I rarely use this tool in any app so I was wondering if there's a way to change Photo's default tool to the Move tool.

    Not via settable app defaults so far, as there's no changable properties setting for that in the app defaults. Meaning, it's actually directly app internal coded that way and so unchangable/settable from outside. And app UI wise it's also not settable to be the default.

     

     

  5. On 2/10/2024 at 1:17 PM, loukash said:

    Probably because within the Affinity UI concept, Studio panels generally operate live, each attribute change being a history/undo step.

    Whereas the floating Alignment popover window has the Cancel/Apply buttons so that you can make all alignment attributes in one step, then either cancel or confirm. It's a different UI approach, and in my opinion the right one. There are individual alignment commands available by other means – menu, keyboard shortcuts, context toolbar – if needed.

    The whole is more a matter of coding and UI setup.

    For example, the FX panel stuff does also perform direct/live changes, can be undone via the apps undo/redo operation stack, I can also detach that, so make/use it in flowable state and it just has a close button. The same can be done with the top alignment panel if wanted.

    Further, it's no big deal in coding to place the already available UI elements and their associated (bound) function calls, from one panel type onto another one with an additional close button. - In case of the actual alignment panel, if wanted, it would be just needed to make it also detachable from there where it actually is, in a manner how can be done with the FX panel stuff.

  6. 9 minutes ago, BioWeb said:

    Here is one screenshot from export and one from the result.

    What do you think ? What I'm I doing wrong ?

    Nothing, as I said before ...

    On 2/10/2024 at 1:46 PM, v_kyr said:

    Check/open the resulting SVG in ADe, look through the layers and inspect opacity settings etc. Further open the by ADe generated SVG inside an external editor and look if there are possibly any base64 uuencoded PNG sections inside (...aka rasterized base64 image data sections) or SVG opacity settings (fill-opacity:  < 1) etc.

    Further, if you reopen the by ADe generated SVG file then again in ADe, you will usually see which layers & which group layer contents has been rasterized to image portions!

  7. 15 minutes ago, demonweasel said:

    Circling back around to this. I did that step but I'm not sure where/how to access such a log.

    After starting Photo --font-cache-logging, look under/inside %appdata%\Affinity\Photo\2.0\  if there is then a log.txt file inside.

    And just for completness here, another fonts related cmd line option is starting the apps via --disable-font-preview-cache.

×
×
  • 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.