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

flobnoit

Members
  • Posts

    23
  • Joined

  • Last visited

Reputation Activity

  1. Like
    flobnoit got a reaction from annamilano in Designer, Export Persona: How to use "User Variables"?   
    Hi all, 
    Within Designer (Windows) can someone explain how to use the User Variables in the Export Persona? It intuitively seems like creating a User variable would make it available to the Path Components of all slices; and so that updating the Value of a variable would update it for all Slices (within the same file) calling that variable.
    At present (2.1.1) this is not the case for me.
     
    Example case, behaviour and expectations:
    --
    I am making mockups. I have a 2 slices for each of 2 different product blanks. I have a symbol over each blank where I can place the logo variations the clients want to see, and I have 4 color variations of each blank.
    I build a path as in the attached image: "Text [Slice Name] - [UserVar]" on Slice 1. I switch on my layer of blue variations, set [Color] to "blue" on Slice 1. 
    At this point, I would expect that I could open Slice 2, and build the path the same way by using the [Color] variable I created in Slice 1. However, the variable created on Slice 1 does not appear in the User variables box of Slice 2. I can create it again in Slice 2 (using identical spelling/case) but this also does not connect the value of the variable across Slices.
    If I "Copy export setup to clipboard" from Slice 1, and Paste it in Slice 2 (so that presumably the variables are identical), and then update the value of [Color] on Slice two, the new value does not become applied to Slice 1. I would expect that a variable being created would allow me to update the value in one place and allow for all instances of that variable to be updated as well. 
    --
    I did not find any explanation of this panel in the help documentation, and the only forum post referring to it seems to be from the pre-2.0 forum. And the behaviour now appears to be similar to what was reported then.
     
    If this is expected behaviour, any guidance on the logic would be appreciated (so I can adapt and integrate).
    If this behaviour is not expected, I would like to request that User Variables be available file-wide so that updating the value of Variable A updates it in all places that call Variable A. 
    Additionally I would like ask if it's feasible to make a small window (even just in the Export Persona) that allows for the User variables and their values to be kept open in the Studio, so they may be updated more easily. This would help streamline the accurate naming of exports during repetitious tasks.
     
    Thanks,
    flobnoit
     

  2. Like
    flobnoit got a reaction from annamilano in Improve Designer, Export Persona: "User Variables"   
    Greetings Affinity team,
    My Improvement ask for Designer (and possibly the other programs as well? I have the Universal license, but almost exclusively work with Designer) would be as follows:
    Context: Designer (all builds) Export Persona
    In the Slice export naming box, there is a box for setting "User Variables".
     
    At present, creating a user variable and setting the value does not seem to do anything. The variable does not appear to be available to any other Slice path, meaning having a value in it is more cumbersome than simply filling out the Path Components field by hand. I searched the documentation and asked about this behaviour here, but it appears that it's a long-standing incomplete feature.
     
    Request: to make User Variables behave conceptually more like a variable in programming (or akin to the Symbols behavior), where once created it can be applied as a Patch Component in as many slice outputs as desired, and then updating the Value of the variable will update all future exports that draw on it. 
    My "that'd be cool!"-level request would additionally include adding a Studio block for the Export Persona to allow viewing and updating of User Variables. 
    Benefit: improving export workflows for people who are exporting several variations of the same slice, eg. when making product mockups with multiple colour variations for the outputs.
     
    Thanks,
    flobnoit
     
  3. Like
    flobnoit got a reaction from fynnn in Improve Designer, Export Persona: "User Variables"   
    Greetings Affinity team,
    My Improvement ask for Designer (and possibly the other programs as well? I have the Universal license, but almost exclusively work with Designer) would be as follows:
    Context: Designer (all builds) Export Persona
    In the Slice export naming box, there is a box for setting "User Variables".
     
    At present, creating a user variable and setting the value does not seem to do anything. The variable does not appear to be available to any other Slice path, meaning having a value in it is more cumbersome than simply filling out the Path Components field by hand. I searched the documentation and asked about this behaviour here, but it appears that it's a long-standing incomplete feature.
     
    Request: to make User Variables behave conceptually more like a variable in programming (or akin to the Symbols behavior), where once created it can be applied as a Patch Component in as many slice outputs as desired, and then updating the Value of the variable will update all future exports that draw on it. 
    My "that'd be cool!"-level request would additionally include adding a Studio block for the Export Persona to allow viewing and updating of User Variables. 
    Benefit: improving export workflows for people who are exporting several variations of the same slice, eg. when making product mockups with multiple colour variations for the outputs.
     
    Thanks,
    flobnoit
     
  4. Like
    flobnoit got a reaction from D.VE in Designer, Export Persona: How to use "User Variables"?   
    Hi all, 
    Within Designer (Windows) can someone explain how to use the User Variables in the Export Persona? It intuitively seems like creating a User variable would make it available to the Path Components of all slices; and so that updating the Value of a variable would update it for all Slices (within the same file) calling that variable.
    At present (2.1.1) this is not the case for me.
     
    Example case, behaviour and expectations:
    --
    I am making mockups. I have a 2 slices for each of 2 different product blanks. I have a symbol over each blank where I can place the logo variations the clients want to see, and I have 4 color variations of each blank.
    I build a path as in the attached image: "Text [Slice Name] - [UserVar]" on Slice 1. I switch on my layer of blue variations, set [Color] to "blue" on Slice 1. 
    At this point, I would expect that I could open Slice 2, and build the path the same way by using the [Color] variable I created in Slice 1. However, the variable created on Slice 1 does not appear in the User variables box of Slice 2. I can create it again in Slice 2 (using identical spelling/case) but this also does not connect the value of the variable across Slices.
    If I "Copy export setup to clipboard" from Slice 1, and Paste it in Slice 2 (so that presumably the variables are identical), and then update the value of [Color] on Slice two, the new value does not become applied to Slice 1. I would expect that a variable being created would allow me to update the value in one place and allow for all instances of that variable to be updated as well. 
    --
    I did not find any explanation of this panel in the help documentation, and the only forum post referring to it seems to be from the pre-2.0 forum. And the behaviour now appears to be similar to what was reported then.
     
    If this is expected behaviour, any guidance on the logic would be appreciated (so I can adapt and integrate).
    If this behaviour is not expected, I would like to request that User Variables be available file-wide so that updating the value of Variable A updates it in all places that call Variable A. 
    Additionally I would like ask if it's feasible to make a small window (even just in the Export Persona) that allows for the User variables and their values to be kept open in the Studio, so they may be updated more easily. This would help streamline the accurate naming of exports during repetitious tasks.
     
    Thanks,
    flobnoit
     

  5. Like
    flobnoit got a reaction from NM_ in Designer, Export Persona: How to use "User Variables"?   
    Thanks @v_kyr - it looks like the problems of 2020 persist still. I'll wait a couple more days to see if anyone else has thoughts, then formally move this over to bugs/requests forum.
  6. Like
    flobnoit got a reaction from NM_ in Designer, Export Persona: How to use "User Variables"?   
    To other forum-goers who happen across this topic- If this is a topic of interest to you, I have also made this a formal post in the Feedback forum where you can show your support:
     
  7. Thanks
    flobnoit got a reaction from Aleksandar Kovač in Designer, Export Persona: How to use "User Variables"?   
    Hi all, 
    Within Designer (Windows) can someone explain how to use the User Variables in the Export Persona? It intuitively seems like creating a User variable would make it available to the Path Components of all slices; and so that updating the Value of a variable would update it for all Slices (within the same file) calling that variable.
    At present (2.1.1) this is not the case for me.
     
    Example case, behaviour and expectations:
    --
    I am making mockups. I have a 2 slices for each of 2 different product blanks. I have a symbol over each blank where I can place the logo variations the clients want to see, and I have 4 color variations of each blank.
    I build a path as in the attached image: "Text [Slice Name] - [UserVar]" on Slice 1. I switch on my layer of blue variations, set [Color] to "blue" on Slice 1. 
    At this point, I would expect that I could open Slice 2, and build the path the same way by using the [Color] variable I created in Slice 1. However, the variable created on Slice 1 does not appear in the User variables box of Slice 2. I can create it again in Slice 2 (using identical spelling/case) but this also does not connect the value of the variable across Slices.
    If I "Copy export setup to clipboard" from Slice 1, and Paste it in Slice 2 (so that presumably the variables are identical), and then update the value of [Color] on Slice two, the new value does not become applied to Slice 1. I would expect that a variable being created would allow me to update the value in one place and allow for all instances of that variable to be updated as well. 
    --
    I did not find any explanation of this panel in the help documentation, and the only forum post referring to it seems to be from the pre-2.0 forum. And the behaviour now appears to be similar to what was reported then.
     
    If this is expected behaviour, any guidance on the logic would be appreciated (so I can adapt and integrate).
    If this behaviour is not expected, I would like to request that User Variables be available file-wide so that updating the value of Variable A updates it in all places that call Variable A. 
    Additionally I would like ask if it's feasible to make a small window (even just in the Export Persona) that allows for the User variables and their values to be kept open in the Studio, so they may be updated more easily. This would help streamline the accurate naming of exports during repetitious tasks.
     
    Thanks,
    flobnoit
     

  8. Like
    flobnoit got a reaction from Aleksandar Kovač in Designer, Export Persona: How to use "User Variables"?   
    Thanks @v_kyr - it looks like the problems of 2020 persist still. I'll wait a couple more days to see if anyone else has thoughts, then formally move this over to bugs/requests forum.
  9. Thanks
    flobnoit reacted to v_kyr in List of some third party vectorization & tracing tools   
    Vectorization and autotracing software for Win + Macs:
    Where * = "the more the better"
    Super Vectorizer 2 (commercial, Mac) ** TracedLines (commercial, Mac) Intaglio Vectorize (free to use, Mac) DragPotrace (Mac) + Potrace (free, Win + Mac) * Potrace (free, Win + Mac) * AutoTrace (free, Win+Mac) * Inkscape (free, Win + Mac) ** Illustrator (commercial, Win + Mac) CorelDraw (commercial, Win + Mac) MS Expression Design 4 (Win, nowadays free) OpenToonz (free, Win + Mac) Image Vectorizer (commercial, Mac) Trace (free, Win+Mac) Vector Magic (commercial, Win + Mac) *** vtracer (free, Win + Mac) * Vectorize! / Legoist (commercial, Mac) VectorStyler (commercial, Win + Mac) ...etc... Online tracing tools:
    autotracer vectorizer vectorizer.ai ** vectorization Vectorize Raster Images Online (online Photopea, free) VTracer * Online SVG Converter (by Potrace) Svgco Svgstorm SVGConverter ...etc... Online centerline supporting tracing tools:
    Rapid resizer fConvert Online Vectorizer ...etc... iPad tracing tools:
    Adobe Capture Vector Q Vectornator Vectorize! ...etc... Some forum threads about tool based bitmap tracing/vectorization:
    Image Tracing in Affinity Designer? Image Trace to Vector Path Converting Pixel drawing to Vector? Auto Trace In AFFINITY DESIGNER Best Image Vectorizer for Mac with Affinity Designer Good vector tracer or vectorizer ... and so on ... See also:
    Awesome PNG to SVG (GitHub) Comparison of raster-to-vector conversion software (Wikipedia) ...etc...
  10. Like
    flobnoit reacted to v_kyr in 8 Years Later, Still NO AutoTrace (convert raster image to vector)   
    Well it's overall not that easy at all to build some outstanding good own tracing algorithm. And most people who are often giving their two cents here in the forum, either way seem to don't know much about bitmap-to-vector tracing in general. - BTW, AI capabilities aren't needed to get and determine some halfway good tracing quality, there are some older tracing algorithms (>= 7 years) which are quality wise still unmatched by nowadays (more modern) implemented tracers.
    Comparison of some tracing software ... etc. (we also once compared some of them here in the forum in some older threads) An algorithmic and output quality wise even nowadays still hard to beat vector tracer is VectorMagic. Also the Inkscape's included, by their dev team custom color quantisation etc. optimized Potrace & Autotrace based tracers, when setup and used the right way, do produce good quality results. They just lack some better UI usability.
    And Affinity? I doubt they will ever can compete here, since as I already mentioned, developing a good tracing algorithm from scratch is no trivial task at all and reusing something already good existing here is mostly associated with a payment of license fees (for example in order to reuse Potrace in commercial products one needs a specific payable licence)!
     
  11. Like
    flobnoit got a reaction from nodeus in Improve Designer, Export Persona: "User Variables"   
    Greetings Affinity team,
    My Improvement ask for Designer (and possibly the other programs as well? I have the Universal license, but almost exclusively work with Designer) would be as follows:
    Context: Designer (all builds) Export Persona
    In the Slice export naming box, there is a box for setting "User Variables".
     
    At present, creating a user variable and setting the value does not seem to do anything. The variable does not appear to be available to any other Slice path, meaning having a value in it is more cumbersome than simply filling out the Path Components field by hand. I searched the documentation and asked about this behaviour here, but it appears that it's a long-standing incomplete feature.
     
    Request: to make User Variables behave conceptually more like a variable in programming (or akin to the Symbols behavior), where once created it can be applied as a Patch Component in as many slice outputs as desired, and then updating the Value of the variable will update all future exports that draw on it. 
    My "that'd be cool!"-level request would additionally include adding a Studio block for the Export Persona to allow viewing and updating of User Variables. 
    Benefit: improving export workflows for people who are exporting several variations of the same slice, eg. when making product mockups with multiple colour variations for the outputs.
     
    Thanks,
    flobnoit
     
  12. Like
    flobnoit reacted to fiery.spirit in We need to talk about artificial intelligence.   
    Every artist I know and follow is ardently against generative AI. There are serious ethical concerns in how Adobe and others have obtained the data, as well as legal ambiguity that leans toward being unable to copyright the resulting images.
     
    It's gotten to the point that digital artists who grew up on Adobe products are boycotting them completely now. And a lot of those artists are picking up Serif's products to fill that hole. I've personally been recommending the products solely because they don't support AI image generators. This is a serious issue for creatives and it absolutely drives the decision to purchase Serif's products.
     
    Even ignoring the Ethical and potential legal issues, it just makes sense for Serif to differentiate itself from the competition hy giving artists what they want-- a program that doesn't actively promote theft.
     
    All the crypto/nft/AI grifters can get their  image generators elsewhere. Please keep it away from one of the few good alternatives to Adobe.
  13. Sad
    flobnoit reacted to v_kyr in Designer, Export Persona: How to use "User Variables"?   
    See related older discussions about "Export Persona" and "User Variables" there, they possibly never really fixed those things so far ...
    export persona user variables site:forum.affinity.serif.com ... and so on !
  14. Like
    flobnoit reacted to Jowday in How about having a different function for Alt+mouse wheel   
    I don't think anyone ever asked for it in Publisher. It is very useful when drawing in Designer and Photo, not so much in a DTP program. The thing is the three programs share almost all code and functionality so clashes of interest like this will happen. This also means Serif must consider possible action.
    Optimally Serif should identify these clashes and offer customization options to remedy the situations. Users of Publisher that never make art or illustrations in Designer/Photo will rarely understand or need rotation of the page. Perhaps in Publisher it should rotate the page in steps of 90 degrees instead. Whatever makes sense to customers.
    So indeed needs are different. But instead of repeating that which leads absolutely nowhere I would recommend what I just said; that Serif adds customization where it resolves such issues.
    Ah, the benefits of LISTENING.
  15. Like
    flobnoit reacted to Ash in 2.1 Beta Build 8 (2.1.0.1769) release notes   
    Hi All,
    Thanks again for all your continued help with this release. We are getting very close to launch. This will be the final beta build before what will hopefully be our first release candidate next week. For that reason we are not really making any further significant changes (or anything which could be considered risky). 
    The main thing I want to make you all aware of is that we have decided to not release the cross-references feature with 2.1. For that reason this feature has been removed from this week's build.
    Any documents you may have created which include cross references will still open (and they will even still update), but you will not be able to edit or create new cross-references in 2.1. We understand this might be disappointing for some of you, however we will be moving into 2.2 beta very shortly after 2.1 release, and as soon as a 2.2 beta is available that will include cross-references again (and will definitely make it to 2.2 release!)
    We have made this decision primarily as we have been working on adding better formatting options (as have been requested on these forums) into the feature, but we have not quite managed to get it to a point where we feel it will be releasable in time - and considering all the other great stuff / fixes we have put into 2.1 we don't want to delay the whole of 2.1 because of it.

    Other than that in this build it's mostly just fixes which you can see in this thread.
    Thanks,
    Ash
  16. Like
    flobnoit reacted to VolkerMB in Affinity Designer V2 getting really slow and laggy after some time   
    It seems that all the apps have lost steam... at least on my computer (Ryzen 7 3700, 32GB RAM, 1TB SSD, RX5700XT (8GB)). I've encountered a similar problem to @4dimage with the glyph browser, too. Without having measured it precisely, I'd say all V2.0 apps run half as fast as V1.x, sometimes even slower. Currently I prefer to use the older iterations of the Affinity apps if none of the newer features are required for the job.
    Let's hope, V2.0.1 will fix some of the issues.
  17. Like
    flobnoit reacted to MEB in Vector/pattern fill   
    I see what you mean. I also wouldn't mind to have the ability to fill objects with vector patterns. Thread moved to the Suggestions for Affinity Designer on Desktop section.
  18. Like
    flobnoit reacted to Pauls in [Windows 11] Designer 2.0.4 freezing / crashing randomly with common actions for no apparent reason   
    when the app freezes go to task manager. Select the designer app and right click. There will be an option to create a crash dump.

    I think you are suffering from something we have identified and will have a fix in our next beta
  19. Like
    flobnoit reacted to Serif Info Bot in [Windows 11] Designer 2.0.4 freezing / crashing randomly with common actions for no apparent reason   
    The issue "App hangs when zooming" (REF: AFD-6338) has now been fixed by the developers.
    This fix is included in build 2.1.0.1706 (or later) which is already available as a customer beta and will be included in the next release.
    Customer beta builds are announced here and you can participate by following these instructions.
    If you still experience this problem once you are using that build version (or later) please make a new thread referencing this one.
  20. Thanks
    flobnoit reacted to Sean P in AD [1.10.0.1104] Pixelated brushes on grouping   
    Hi StuartRc,

    Thanks for letting us know - it looks like an annoying redraw issue - a quick change of the zoom level does seem to cause the document to redraw, but of course as soon as you start painting again it will happen.

    I've reproduced this and will get it passed on to development.
  21. Haha
    flobnoit reacted to Old Bruce in Is AFFINITY dead?   
    Regardless ... Its got beautiful plumage!
  22. Like
    flobnoit reacted to Dan C in Print to Driver: not working as expected   
    No problem at all, many many thanks for the wealth of information provided!
    I've logged this directly with our QA/dev team for further investigation - as you've confirmed this is a 'regression' in versions newer than 1.9.1, therefore the team will need to perform testing in multiple versions of Affinity and this may take some time.
    I'll be sure to update you here with any findings or further details required, but we're certainly glad to hear you're enjoying using Affinity as much as we enjoy making it! Many thanks for your kind feedback here
  23. Thanks
    flobnoit reacted to MEB in Windows: Preview Pane image   
    Hi @flobnoit,
    No worries. Where are you storing Affinity native's files? If i remember correctly there's a cloud synchronisation service/folder that doesn't display the thumbnails for our files (I have to double-check this).
  24. Like
    flobnoit reacted to MEB in Windows: Preview Pane image   
    Hi @flobnoit,
    Welcome to Affinity Forums
    We do embed a thumbnail that Windows is able to display in the Preview pane. Do you have Save thumbnails with documents enabled/ticked in Affinity Designer Preferences, General section?
  25. Like
    flobnoit reacted to walt.farrell in [resolved] Stroke Align: not responsive   
    What kind of object?
    Are you sure it is a closed curve? Open curves do not have an outside or inside, and so they have only centered strokes.
    A screenshot and/or sample file would help.
×
×
  • 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.