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

carl123

Members
  • Posts

    8,494
  • Joined

Posts posted by carl123

  1. You have a few things going on in that project file making things more difficult than they should be

    1. It appears you have cropped the picture previously so use Layer > Rasterise to get rid of the previously cropped pixels

    2. Switch off the lower Background Layer, just work on the top background layer

    3. The blue line you see in my attached file is a vertical guide, used solely to see when the wall is straight.  You do not match the perspective grid to the guide you match the straight vertical part of the wall to the guide.

    4.  The guide is just a reference placed close to the wall, you don't need to move the wall so it is exactly on the guide, just ensure the top and bottom of the wall are the same distance from the guide.

    5.  When using the Perspective Tool, use single pane but switch Show Grid off , it is just getting in the way for this exercise.

    6.  Drag the perspective from the top left node to the right, (keeping it perfectly horizontally) to align the wall vertically.  Do not move the node up or down as that just distorts the image in the wrong way.

    7 After you have aligned the wall you will have transparent pixels on the left hand side, you will need to recrop the image to remove them

    8.  Because of this requirement to recrop an image after straightening it, it is usually best to do the straightening first before any sort of cropping is done on the image

    9. Just keep practicing, you will soon find out how everything works


    See the attached, where the left hand wall has been aligned to a vertical guide (switch on guides if they are off in your program)

    Tv-Kitch2.afphoto

  2. Attached is a Crop to Opaque macro which should work where you have irregular transparency at the top and bottom of an image, like the sample image shown below.

    It works in 2 parts, first cropping the transparency at the top of the image then cropping the transparency at the bottom of the image.

    Note: If you only have transparency at the top of the image you would need to modify the macro to stop the second part being run or weird things happen.  (If anyone has found a way to force a running macro to pause at a specific point, that could be useful here)

    The macro was written purely as a proof of concept macro whilst stuck on a train, I have no real need for such a macro but it's here for others to dissect and use or modify/improve as required.


    Only tested on images up to 5000px X 3000px so far
    Tested only on one layer pixel images where the layer is named Background (the default)
    Seem to work in most real life scenarios but will fail if you push it beyond its capabilities.

    sample image.jpg

    crop to opaque - version 1.afmacro

  3. If you like it quick and dirty, try this...

    1. Draw a line from A to B

    2. In the Transform panel rotate the line so it is perfectly horizontal
    (Use CTRL + Arrow keys to rotate in 0.1 degree increments if needed)

    3. With the line still selected hit the Reset Selection Box button in the context toolbar

    The width now displayed in the Transform panel is the original  A to B distance

  4. 13 hours ago, Rick G said:

    Absolutely nothing happens with that equation neither in the release nor the current beta.

    The Equation does indeed work but it is a very subtle effect at the setting shown (1.01).

    In the attached screenshot I have two identical Art Text layers the top one in black. In that screenshot I have increased the effect of the Equation ( from 1.01 to 1.5) so you can see, more clearly, what it does.

    In reality you use a very small value (1.01) and apply it to each subsequent layer to build up a smooth shadow effect with no jagged edges.

    Needles to say, I created a quick macro to do that part, as there are a lot of layers

    export1.jpg

  5. 53 minutes ago, R C-R said:

     My only objection is to the idea that there is some inherent logical reason for preferring 'before' on the left & 'after' on the right. There is none.

     

    The "inherent logical reason" is that's the way it has always been and what we are used to.

    Try doing a Google image search for

    before after

    and see what you get

    https://www.google.co.uk/search?q=before+after&source=lnms&tbm=isch&sa=X&ved=0ahUKEwi1t7XF7sDZAhUCLMAKHUb-CtMQ_AUICigB&biw=1920&bih=901

    Even if you try to "fool" Google by doing a search for

    after before

    You'll still get before & after pictures.

    It was correct in the Plus range of software (PhotoPlus etc) and even the Affinity Help topics refer to it as Before/After so why display it as After/Before

    Why on earth Affinity programmed things the other way around we can only speculate on, or wait for one of the Developers to enlighten us as to why changing the status quo, in this case, provides additional benefits that none of us are currently aware of.

     

  6. 13 hours ago, Traveler said:

    For example I would have one macro set to resize document to 600 px tall, one 700 px tall, and one 800 px tall. I may try one and then just undo and try another one before.

    Here is a link to a macro that should allow you to choose all those settings dynamically within the one macro.

    You may be able to adapt it to your workflow

     

  7. Attached is a resizing macro with a slider that allows you to dynamically resize your image's height  from 1000px to 100px in 100px increments

    The slider values goes from 0 to 1.0

    Where...

    1.0 = 1000px for the height
    0.8 = 800px for the height
    0.7 = 700px for the height
    0.2 = 200px for the height
    etc
    etc

    You can use the CTRL + Arrow keys in the Slider adjustment box to quickly change increments in 0.1 (100px) values

    But for those of you that prefer using the slider to change the value, the macro has been written so that any values after the first decimal place are effectively ignored.
    So you do not have to move the slider to precisely 0.600 to get a 600px high image.  Any value from 0.600 to 0.699 will always result in an image size of 600px

    Likewise moving the slider to any value from 0.300 to 0.399  will always result in an image size of 300px, etc, etc, etc

    Once you have resized the image you would need to perform a Document > Clip Canvas command to get rid of the transparent pixels now surrounding the image

    Note: The macro has a clip canvas command at the end of it which I have disabled in this demo so you can see the macro working in "real time" but it can be reenabled by editing then resaving the macro if you prefer the macro to do this step for you automagically

    The Equations formula used in the macro is

    x*h/clampmax((rounddown(a*10)*100),h)
    y*h/clampmax((rounddown(a*10)*100),h)

    This macro has been tested but not exhaustively, it is here as a demo for others to use or adapt as required.  The main purpose in writing it was to find a way for the slider to ignore any decimal points values after the first one, which was (eventually) achieved using the "rounddown" command.

    Note: There is either a bug or misinformation regarding the use of the "rounddown" command which I will file a separate bug report for and link to from this post at a later time

     

    Selectively resize image height from 1000px to 100px.afmacro

     

    EDIT: The link to the bug report can now be found here

     

  8. Provided you have no locked layers

    Here are 2 other methods

    Select > Select All Layers
    Edit > Copy
    File > New from Clipboard

    Which will only copy layers that are not hidden into a new document

    Or if you want to stay in the same document (and have nerves of steel)

    Select > Select All Layers
    Edit > Copy

    Select all Layers in the Layer panel and hit the Trash icon
    Then Edit > Paste

     

     

  9. 11 minutes ago, Mark Ingram said:

     

    That's 4.6.2.

     

    According to Microsoft, 8.0 can't install 4.6.2, are you sure you're on 8.0 and not 8.1?

    Yes definitely 8.0 not 8.1, this PC keeps getting reminders to update to 8.1

    Likewise, we could not install .NET framework 4.7.1 from the last AP beta - if we were on 8.1 it would have installed Ok

    and finally we have legacy software for a client that will not run on 8.1 which is why we always keep one PC on 8.0 just for them

     

     

    system.jpg

  10. 8 minutes ago, Mark Ingram said:

     

    I'm glad you can install it again - though I'm surprised it installs on 8.0 at all, as .NET 4.6.2 is listed as unsupported on Windows 8.0 (and as such, we've had to update our list requirements to say we don't support Windows 8.0).

    I only have .NET 4.0.0.0 on this Windows 8.0 PC but both the retail and all the betas have always run fine on it  (Excluding beta 1.6.3.100)

    PS This page says you still support Window 8.x.  You may need to update it if that is no longer the case

    https://affinity.serif.com/en-gb/photo/full-feature-list/

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