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

GarryP

Members
  • Posts

    11,164
  • Joined

  • Last visited

Posts posted by GarryP

  1. It might be useful if you can give details of a specific instance (or, even better, more than one) where the current functionality is cumbersome, noting the points at which the process could be ‘streamlined’, so that people can follow the workflow themselves to see what happens.

    That might help people to better understand what the problem is and, perhaps, ‘get on board’ with your proposal.

  2. 1 hour ago, rikkarlo2 said:

    However I still can't figure out how to bring back the edited layer into channels and masks.

    In what way “bring back”?

    If you can describe:

    • what you have;
    • want you want achieve;
    • how you are trying to achieve it,

    ...then an expert in this area (not me) should have some advice for you.

    They might even have a technique you can use which doesn’t need so much effort, but they would probably need to have more information.

  3. ...and, as has been mentioned to you before, on multiple occasions, in multiple threads, by multiple people, the beta area of the forums is not the correct place to make requests that are not specifically related to the additions and changes that have been introduced in the beta software.

    See: https://forum.affinity.serif.com/index.php?/topic/181201-bug-reporting-and-feedback-tips/

    Specifically: 
    “Please keep this [feedback] within scope of the improvements we have made...”
    ...and...
    “Please bear in mind the beta forums are not for giving new feature suggestions which are outside of what have been added to the beta.”

    Just because something has not been specifically introduced in the beta doesn’t mean that it’s an issue to be discussed for the beta, otherwise every possible thing that hasn’t been implemented in the beta could be thought of as being an issue to be discussed for the beta, and that would just be silly.

    If you continue to ignore Serif’s guidelines for posting to the beta sections then I think there’s a chance that you risk having your access to the beta sections removed, meaning that you could then only post requests to the place where they should be made anyway, so maybe that's a good thing overall as they would possibly be seen by more people.

  4. One way you can check the Opacity of the pixels in an image, in Photo, is to:

    • Open the image;
    • Open the Channels Panel;
    • Scroll down to the Background Alpha channel;
    • Right-click on that channel and choose “Create Greyscale Layer” from the menu.

    (Alternatively you can simply make the Red, Green and Blue channels invisible but that doesn’t let you use the Histogram as below.)

    Any pixels that you see which are not completely white is where there is some transparency in the original image.

    Additionally, while looking at the Greyscale layer created above, you can also look at the Histogram Panel. If you see any ‘wiggles’ or ‘curves’ in the plot, rather than just a peak at the left and a peak at the right, then you have transparencies somewhere.

  5. I have nothing to do with the development of the Affinity applications, I'm just a user.

    The beta sections of the forums are for people with questions, requests and bug reports which are specific to the current beta release and what has been added or changed in that release.

    Questions, requests and bug reports about the applications in general - those that are not about things specific to the current beta release - should be posted in the 'normal' areas of the forums.

  6. lennyd21: If the problem you are reporting is that outlined by Walt then that’s already been requested here (in point 1): https://forum.affinity.serif.com/index.php?/topic/192894-suggestions-for-improvement-of-color-palettes/

    It’s also (sort of) related to this bug report: https://forum.affinity.serif.com/index.php?/topic/195702-swatch-panel-palette-keeps-reverting-to-colours-–-v23/

    It’s also (sort of) related to the discussion here: https://forum.affinity.serif.com/index.php?/topic/197615-make-global-swatch-default/

    ...and others. Basically quite a few people would like palettes and swatches to be handled differently to how they are handled now.

    These threads were found via a forum search for swatch default .

  7. If you press the T shortcut key when a Frame Text layer is selected then the software will think you want to type text and will give the Frame Text layer focus so you can type in it.

    This is the same as selecting a Frame Text layer with the Move Tool and then selecting the Frame Text Tool.

    I believe this is expected behaviour.

    Could this explain some of what you are experiencing?

  8. 29 minutes ago, N.T. said:

    can't help wondering if was in the update that had features that excluded v2 Photo module in it

    I don’t understand what you mean by that.

    Regardless of when the change happened, hopefully a member of staff will be able to give us an idea of whether it was a deliberate change (and, if so, why) or whether it’s something that might need some attention from the developers.

  9. In Publisher:

    When Copying text from a Frame Text layer, or with any ‘raw’ text on the clipboard, and then Pasting that text directly into the document, rather than pasting it into an existing Frame Text layer, the software will create a new Frame Text layer with a height that is half of the spread height and width that is half of the spread width. It then places the text in that layer.

    The text has to be part of a layer and the software has to ‘guess’ how large to make that layer, so it just makes it a quarter of the size of the spread, leaving it up to the user to resize it as necessary.

    In Designer: Substitute ‘canvas’ or ‘Artboard’, as appropriate, for the word ‘spread’ in the above text.

    In Photo: Substitute ‘canvas’ for the word ‘spread’ in the above text.

  10. 1 minute ago, Iztok said:

    I think you should simplify the color system

    I don’t see anything that is beta-specific in this request.

    Requests for new/changed functionality that is not specifically about what has already been implemented in the beta versions of the software should not be placed in the beta-specific sections of the forums.

    A moderator might move this thread to the correct section of the forums for you.

  11. 11 minutes ago, Linda Noone said:

    Where should I post this?

    No harm done, it just helps when things are in the right place, for both we users and Serif.

    If you are not using the beta software then it’s best to try and steer clear of the beta sections of the forums, unless you want to start getting involved with the beta testing that is.

    If you look near the top of the page you will see some ‘breadcrumbs’ which tell you where you are in the forums.

    For instance, this thread is currently in: Home > Affinity Support > Affinity Support & Questions > Affinity on Desktop Questions (macOS and Windows)

    This means that the thread is in the ‘normal’ place to ask questions about the Desktop software.

    If you see the word ‘beta’ anywhere in those ‘breadcrumbs’ then, unless you want to discuss the beta software, you’re probably in the wrong place.

    To find the right place in the forums, go to the Home page and then scroll down until you find a link which looks about right.
    If you have scrolled down to where it says “Beta Software Forums” then you’ve probably scrolled too far.

    Like I said, you’ve not done anything bad, you just happened to create the thread in the wrong section of the forums.
    It’s not a big deal and please don’t worry about it.

  12. 3 hours ago, Iztok said:

    I suggest that

    I don’t see anything that is beta-specific in these requests.

    Requests for new/changed functionality that is not specifically about what has already been implemented in the beta versions of the software should not be placed in the beta-specific sections of the forums.

    A moderator might move this thread to the correct section of the forums for you.

  13. I’m not seeing the same thing as you.

    In my attached video I have a document which is 7680×2160 pixels.
    I select the Crop Tool, then select the 16:9 Custom Ratio from the Presets.
    The crop size is 3840×2160 as expected, and the resultant image after cropping is also 3840×2160.

    (I tired the same thing with a 72dpi document and a 96dpi document and got the same result.)

    While using the tool I notice that the ratio in your image (3840×2160) doesn’t tally with that in my video (16×9). I wonder what’s happening there.

    Would you be able to share the original image so we can experiment with it?

  14. The text you quoted is, as far as I can tell, from the Vector Content Defaults page of the Help which also says, at the start:
    “When you create vector content, its appearance is initially determined by the default settings for the particular content you are creating.”

    Is the guide colour really classed as being part of “vector content”?

    If so then I think that Help page needs an overhaul as it seems to be talking about something which is different to how things currently are, from what you have said above.

    P.S. Did you spot the note I added about the Factory Reset not resetting the guide colour? (I might not be using it right as I might not understand what this functionality is supposed to do any more.)

  15. I don’t know at which version number things changed but I’m seeing this too on Windows 10.

    With V1.10.6 I can use non-integer values but with V2.4.2 I cannot.
    (All of the Decimal Places settings in Settings / User Interface are set to 3 in both applications.)

    Also, Ctrl+mouse-scroll on the Radius field has no effect in V2.4.2, other than to lose the field focus, but it works as expected in V1.10.6.

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