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

mrqasq

Members
  • Posts

    99
  • Joined

  • Last visited

Reputation Activity

  1. Like
    mrqasq reacted to EricP in Create a 'media browser' panel of our image folders to view and place them in the document   
    I like the place panel but I would like it to be persistent. If I drag 20 images and start placing them one by one (not autoflow), I cannot stop the process or switch to another tool to make a small adjustment, otherwise the place panel disappears and I loose track of what images have already been placed.
    Making it persistent like any other panel would be very helpful when working with imported assets
  2. Like
    mrqasq got a reaction from thomaso in Adding bleed after file is already done :(   
    this might help me the most. I will try it and report back
    YES. This is the solution. Thanks mate!
  3. Thanks
    mrqasq reacted to thomaso in Adding bleed after file is already done :(   
    If objects that are placed at the artboard edges got created in the required size so they exceed the artboard size, then it maybe sufficient for those to activate bleed in the document properties. (kind of 1 click as mentioned by @loukash)
    But if the objects need to get created larger (as in your circle example screenshot) then you need to edit each of the according objects. Possibly you use the Contour Tool to increase the outer shapes (e.g. instead of resizing via Transform Panel).
    Dirty workaround: If you alternatively want to increase all objects on all artboards simultaneously but without increasing the artboards you can choose "Select All" -> activate the Context Toolbar option "Transform Objects Separately" -> set the anchor in the Transform Panel to centred -> and add a percentage for Width or Height (with the aspect ratio locked active).
    This enlarging method also works for selected objects only but then it may require many single clicks to select the wanted objects.
  4. Like
    mrqasq reacted to walt.farrell in Round Corners - Windows 11   
    If by "pay attention" you mean "respond here", then probably not. The Feedback section is for us to express and discuss our requested improvements. Serif reads those requests/discussions, and factors them into their plans. But generally, as they do not want to disclose future plans, they do not respond here. Even if they respond, the usual responses are often "we would like to do it someday" or "we don't like to say no, but we are not considering it at the moment". So you won't get a yes, or a no, or a timeframe, usually.
    If, though, you mean "implement the changes discussed here", we can only wait and see if they ever happen.
  5. Thanks
    mrqasq reacted to imagodespira in Round Corners - Windows 11   
    bitegr: Thanks! It is great and now i can separate the window between other dark mode apps. 
    @Serif: Please try it and you will see that your decision to make no round corners where wrong! It is no problem to make it, so please do it!!!!!
    For me, it is a game changer!
  6. Like
    mrqasq reacted to bbrother in "Align to" can't be selected first in the alignment panel. Not logical, not like it was in V1.   
    User can't select first the "Align to" option in alignment panel beacuase it is greyed out. The manual says something different.
    Here's what you can read in the help files for version v2 ↓

    Before you comment:
    I know this behavior changed between app versions 1.7-1.8. At the beginning, we had the opportunity to set the alignment parameters first, but this was later changed.Users quickly got used to the previous behavior before the change because it was logical and very intuitive.
    There were many complaints and requests to reinstate the previous behavior. Yo can check it using the link bellow ↓
    https://forum.affinity.serif.com/index.php?/search/&tags=aw-3864,afd-3927&search_and_or=and&sortby=relevancy
     
    Reasons to treat this as a bug and why i'm making the post in bug forum:
    Incosistent behaviour between apps versions Actual steps ar not the same as suggested by manual  
    Reasons to rolll back to the previous behavoiur and allow users to set the aligment parameters first:
    Not logical/intuitive behaviour (not allowing to set parameters for action before applying that action it's a nonsense) Not a good idea to have objects leaping about the place before we go on to click the right options. It's very, very distracting and wearing, particularly after watching objects go to the wrong place before we set them up how whe want. Not productive and notcomfortable tool behaviour for reasons i mentionet above.  
    Sorry, I'm going to get emotional here:
    For God's sake why don't you let users use the options the way they want.
    Reconsider your bad decision and bring back old behavoiur. Listen and don't be deaf to users arguments. You can only gain.
    And a one more question to moderators, devs, anyone behind making this bad decision:
    Why did you deliberately change the way the alignment parameters work when nobody asked for this and why did you not restore them to the previous version despite complaints and requests from users supported by rational arguments?
  7. Like
  8. Like
    mrqasq reacted to MikeTO in Crop a shape   
    It didn't work because those are strokes and not shapes so you'll need to convert them to shapes first. Select them and choose Layer > Expand Stroke to convert them to shapes and then you'll be able to cut off pieces to delete with the Knife tool.
    Cheers
  9. Like
    mrqasq got a reaction from thebodzio in Roadmap - Serif what are You up to - next ?   
    I think we all waited for the @Ash post here which answered many questions we had.
    Going forward with this idea of openness, I have a proposal for Serif staff members:
    I remember back in the days when there was a roadmap for V1, but then it was canceled due to reasons known for Serif.
    Since we're now in V2, I would humbly ask to consider going back to this idea. We all visiting the forums daily see that big red info at the top that response time is elongated due to v2 premiere. That's understandable. But since many of us still wait for the things we asked for 3-5-7 years ago and some of them even simple are still not implemented - I think we could all benefit, as a community, from the list of things you want to add in the future. Since there are many features that were "considered" to be added years ago, and didn't ever found its way into the suite, I can't see any cons to this idea. You still can just write something and don't provide. But many of us, me included, we could sleep happier knowing that this or that will eventually come since it's on the list.
    If you're afraid this roadmap topic would push users to show their dissatisfaction - just close the topic like you did @Ash with V2 pricing post...
    I would understand if this would a CIA forum, or FBI and there are some things top secret, but then again - we are here not only as customers but a willing to help fan base, we truly love your efforts put into the software. Could you share more with us? In the past, we've seen many posts all over the internet regarding your lack of communication. There are many speculations than etc., and I think it all does more harm than help to Affiniters as w whole group. This could be so easily strengthen with more communication, and what could be more appreciated that a list of the "soon in suite" things? Please at least consider it, and if the answer will be again "NO" that try at least to elaborate why you choose so.
    The second thing needing a separate topic is polls. This would be great if we would be greeted by a poll that would state "Hi, we need your opinion since we are now working on this and that and we would like to know what else would you like to see". And users could pick and choose or write down what they need. Simple action and everyone who bought the app would feel important and that he's opinion matters.
    I really think that a person or a company that uses "I know better" view on things is considered poorly. If you know better what are needs are, atleast share that opinion in the roadmap
    If you don't make a poll like this, I will do it just for fun
    Enjoy your day, everyone.
    Take care!
  10. Like
    mrqasq got a reaction from GRAFKOM in Set Export Persona transform to measuring type (mm, cm, inch, etc)   
    The issue was described in v1 app:

    Now in v2 I have same issue again, where even when my rullers are set to mm, while I'm dragging new slices, I see only px sizes.
    Which for me doing with print sizes is worthless since I can't calculate in my head px to mm in any given dpi resolution this would be great to being able to set app-wise measurment to cm and forget it once and forever.





     
    Here's also a video which shows inconsistency of sometimes showing the size while dragging a shape tool, while not showing while dragging marquee tool or slice tool. The code is there just make an option to select it's visibility and measurement type for everyone around the world.
     
    IMG_1552.MOV
  11. Like
    mrqasq got a reaction from Rudolphus in Set Export Persona transform to measuring type (mm, cm, inch, etc)   
    The issue was described in v1 app:

    Now in v2 I have same issue again, where even when my rullers are set to mm, while I'm dragging new slices, I see only px sizes.
    Which for me doing with print sizes is worthless since I can't calculate in my head px to mm in any given dpi resolution this would be great to being able to set app-wise measurment to cm and forget it once and forever.





     
    Here's also a video which shows inconsistency of sometimes showing the size while dragging a shape tool, while not showing while dragging marquee tool or slice tool. The code is there just make an option to select it's visibility and measurement type for everyone around the world.
     
    IMG_1552.MOV
  12. Like
    mrqasq reacted to Patrick Connor in MSI Installer upadate?   
    The 2.0.3 MSI (unsandboxed) install puts the exact same software build (all the same EXE/DLL build files and support files) as the 2.0.3 MSIX (sandboxed) install. The ONLY difference is the installation technology. Even if the EXE/MSI installer was available today, the resultant software would act as your current MSIX Installation, only you can choose which directory to install the files into (unsandboxed) and a few other minor differences. 
    Fixes to the software will come in 2.0.4/2.0.5/2.1.0 etc and those fixes will be available in both install technologies, as unsandboxed MSI and sandboxed MSIX.
  13. Like
    mrqasq reacted to SrPx in Crashes within 5 seconds of launching: affecting all V2 Suite apps   
    Are those 5 seconds (seems tight to be able to do it) enough for you to set "hardware acceleration - open cl" as non checked, off, but actually exit normally the app? As a crash avoids saving any preference setting. People are reporting more crashes and issues with Open CL than with memory allocated (but it can be an issue in very low memory (ie, a 4gb RAM laptop) cases or misconfiguration).  Also, showing preferences-> Performance, and preferences-> tools screenshots here could be very helpful. Specially as that's a system (unless you left some detail out) with no card, it's using the integrated CPU graphics. Also, how much RAM has got your system (to compare to what's set on preferences, etc). Windows tells you that in Windows Settings-> System-> About (it even tells you how much memory is really allocated and how much is reserved. Usually not a prob with intel). Another setting interesting to check (again, if fast enough to exit normally so that the setting is saved)  is to set the renderer as WARP, instead of your integrated graphics. If it stops then crashing, that fact gives valuable info.
    If it's crashing, it's not saving the preference, so, another way to avoid the Open CL issues is to directly launch Affinity without Open CL, like recommended here: 
     
  14. Like
    mrqasq reacted to Mark Ingram in Are legacy MSI v2 installers available?   
    Yes, we will be providing MSI installers to customers who require them. This FAQ will be updated with links to MSI downloads when they become available.
    Yes. These are now available
     
  15. Like
    mrqasq reacted to Designer1 in Poor export quality of PNG and JPG.   
    I like using Affinity Designer. It's a very good app. However, export quality and antialiasing can be improved.
  16. Like
    mrqasq got a reaction from SrPx in [Not solved. Just a sharing a trick for it] Double clicking on the primary or secondary colors crashes [Photo, Designer, Publisher]   
    I would try to reset windows. I had similar problem in the past with gimp and couldn't resolve it. But after windows reset (which is a pain) it worked.
     
    In Run window input PowerShell
    Type:
    systemreset -factoryreset
    Press enter
  17. Like
    mrqasq got a reaction from SrPx in [Not solved. Just a sharing a trick for it] Double clicking on the primary or secondary colors crashes [Photo, Designer, Publisher]   
    Just a thought, you're mentioning in your description that you have a laptop also. Do you have issue there as well?
  18. Like
    mrqasq reacted to stokerg in App keeps closing   
    Hi @Sana Rehman,
    Could you see if you have any crash reports and post them here.  To find the reports see here and i can get these debugged.
    Couple of things you can try now, start Affinity while holding down the CTRL key and you'll get a window popup asking if you'd like to clear some settings.  3 options will be selected and you can just click on Clear.  Now try working with the colour picker and see if you get a crash.  If you do, then restart Affinity and go into Preferences and on the Performance section, disable openCL at the bottom of this window if its enabled, then restart Affinity and try using the colour picker again 
  19. Like
    mrqasq reacted to walt.farrell in iPad Pro 12.9 Enable all personas visibility like desktop   
    Thanks for the clarification  
    By the way: in case you haven't noticed it yet, Serif generally does not discuss topics in the Feedback forums. This section of the forums is here for us to express our wishes, and for Serif planners to read. They seldom respond in this part of the forum, and I would be extremely surprised if they would debate.
  20. Like
    mrqasq got a reaction from wtrmlnjuc in iPad Pro 12.9 Enable all personas visibility like desktop   
    Make it dynamic. Would be less clicks when possible, and compacted when need be. Like less space available like your case. It's not impossible.
    For me on PC with lower resolution it's also cluttered sometimes but things as important as personas are always visible.
    Why we have this dualism in UX ? Things are ok somewhere and unacceptable elsewhere? I thought they aim to unify workflow. 
    Better yet as I suggested somewhere else - give us option to customize toolbars and let everyone set like they want it instead forcing someone's opinion on all saying  'we know better'.
    Or make double row at the top. Stop hiding features behind buttons. We have space, why not use it?
    Wouldn't You agree?
  21. Like
    mrqasq reacted to Mark Oehlschlager in EDITED: Offer Naming Dialog Boxes for Newly Created Items   
    Why is it that for so many "New ..." commands (new category, new swatch, etc.) the Affinity apps don't automatically throw up a naming dialog box? Seems quite logical to give the user the opportunity to name the newly created item straight away, rather than forcing one to go back into the menu structure with 3-4 extra clicks.
    EDIT: Allow me to apologize and to withdraw this post. I was watching one of the V2 tutorial videos (probably produced when V2 was still in Beta), and an Asset category first had to be created before it could then be selected and named. It reminded me of a complaint I had with the V1 apps.
    I should have checked this behavior in the release version of the V2 apps. As I now actively create new items in my copy of V2 apps, a naming dialog box does indeed now appear by default, with the notable exception of the command to create a Spare Channel in Photo 2. 
    Sorry for the inaccuracy of the post.
     
  22. Like
    mrqasq reacted to Kent Davis in Grid…is this normal?   
    @MEB did explain me really clear.
    Look at my youtube. 
     
     
     
  23. Like
    mrqasq reacted to MoonaticDestiny in iPad Pro 12.9 Enable all personas visibility like desktop   
    Hey, walt. This is something I really want to have a debate about. I think all personas should be lined next to each other. How it was in v1 and how mrqasq here is asking for and the reason why I say that is because it makes it easier for the user to toggle between into each persona. These personas are very important. Users should be able to toggle into them easily with one tap. Now, users have to do 2 taps just to get to them. 2 taps slows workflow and it makes it less easy to toggle into them.
    Heres the REAL issue though. Serif thought it was a good idea to put the context toolbar at the top on the same row the personas are on. Bad idea. That row at the top now becomes full of icons and these context toolbar icons now clash with the persona, document, and edit buttons. Because they clash, serif now has to make room for the context toolbar buttons and has put the personas into their own little single button pop up menu. This was a bad design choice by serif. This design choice makes the user do more work to get to important personas. This context toolbar ruins everything.
    I hate the context tool bar at the top. It was fine at the bottom in v1 but serif said something about they needed to move the context toolbar because it was in the way of the users canvas. It was distracting so it was moved to the top. I truthfully believe that if serif wanted to put the context toolbar at the top, they should have made a second row and have this second row reserved for the context toolbar. THATS what should have happened.
    That way the top row is reserved for all personas, the document, and edit buttons.  And then the context toolbar has its own row below for as many buttons it has. So now theres no button clashing going on and users can now 1 tap easily into their own personas.
    On top of that, the top row where the personas,document, and edit buttons are should have been where the customizable toolbar should have gone. Its what users have been asking for years. Serif made a mistake by putting the context toolbar there instead of the customizable toolbar. And you know why the context toolbar at the top is a bad design decision? Its bad when not all the buttons of the context toolbar can fit on the bar at the top that you have to do a swipe left on the bar to see the rest of the buttons of the context toolbar that are hiding behind the zoom preview mode and snapping. Thats when you know its bad. 
    So all personas should be displayed. No pop up menus for personas. The context toolbar should have gone on a second row below the top row. 
  24. Like
    mrqasq got a reaction from MoonaticDestiny in iPad Pro 12.9 Enable all personas visibility like desktop   
    Make it dynamic. Would be less clicks when possible, and compacted when need be. Like less space available like your case. It's not impossible.
    For me on PC with lower resolution it's also cluttered sometimes but things as important as personas are always visible.
    Why we have this dualism in UX ? Things are ok somewhere and unacceptable elsewhere? I thought they aim to unify workflow. 
    Better yet as I suggested somewhere else - give us option to customize toolbars and let everyone set like they want it instead forcing someone's opinion on all saying  'we know better'.
    Or make double row at the top. Stop hiding features behind buttons. We have space, why not use it?
    Wouldn't You agree?
  25. Like
    mrqasq got a reaction from MoonaticDestiny in iPad Pro 12.9 Enable all personas visibility like desktop   
    A picture is like a thousand words someone once said.
     
     

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