Borders in macros -- different horizontal Vs vertical

[ianrb]

Hello, why is it so?
I make a macro to add a border to a 11x14 inch vertical photo as in first photo
However, if the image is rotated 90 decrees and the same macro is added it appears as in second --- the image is not centered .
Why is that so? Been puzzling , and annoying me for a long time .
PS Have changed the border to black so it's easier to see
Cheers

[R C-R]

It would be easier to help you if you included the *.afphoto file & the macro, or at least tell us what step(s) are in the macro & how you created it.

[ianrb]

20 hours ago, R C-R said:

It would be easier to help you if you included the *.afphoto file & the macro, or at least tell us what step(s) are in the macro & how you created it.

Sorry -- had forgotten but will do it soon

[ianrb]

Help; how to share the macro? I know the export part but how do I get it to you
32mb afphoto file --- best way to share to the forum ?
I do have dropbox

Cheers
 

[ianrb]

This might ; or might not work (??)

https://www.dropbox.com/scl/fo/rcwap217rkggojgfcumn0/h?dl=0&rlkey=q9yip9aqx6kyoxaoxiit66iem

[walt.farrell]

For future reference, all you should need to do, @ianrb, is drag/drop them onto a post here. Or click the "choose files..." link at the bottom of the composition window when posting.

[Dan C]

Hi @ianrb,

Thanks for providing these files!

I can confirm that Macro Transforms work based on a Scaled Percentage of the X & Y values, therefore when your macro is recorded in portrait your transform is applying a 97% scale transform to the X value, and a 98% scale transform to the Y value.

Applying this macro to a landscape image then applies these scaled percentages to 'swapped' values from the original recording, resulting in unexpected results.

Therefore I would recommend creating 2 different versions of this macro - one for Vertical images and one for Horizontal, to ensure the correct scaling percentage is being applied to the expected axis value.

I hope this helps

[ianrb]

11 hours ago, walt.farrell said:

For future reference, all you should need to do, @ianrb, is drag/drop them onto a post here. Or click the "choose files..." link at the bottom of the composition window when posting.

Cheers mate , I was actually doing that but thought a 32mg file would not go through

[ianrb]

9 hours ago, Dan C said:

Hi @ianrb,

Thanks for providing these files!

I can confirm that Macro Transforms work based on a Scaled Percentage of the X & Y values, therefore when your macro is recorded in portrait your transform is applying a 97% scale transform to the X value, and a 98% scale transform to the Y value.

Applying this macro to a landscape image then applies these scaled percentages to 'swapped' values from the original recording, resulting in unexpected results.

Therefore I would recommend creating 2 different versions of this macro - one for Vertical images and one for Horizontal, to ensure the correct scaling percentage is being applied to the expected axis value.

I hope this helps

Thanks @Dan; thought that would be the answer and is OK for V 11x14 and H11x14 , however if a different ratio is used would require  different macros .
The white border in the macro is a new thing . I do have a macro to just add the stroke which is easy enough to manually reposition around the edge or a little inside the edge
Cheers

 

[v_kyr]

7 minutes ago, ianrb said:

...however if a different ratio is used would require  different macros...

Which shows the overall limitations (and useless idiosyncosity) of Affinity's macro implementation. There's no real way to auto determine and deal with dynamic sizes and orientations for documents/images here, also there is no file i/o and dynamic text handling support etc. - All in all it's pretty useless for all those tasks, which can be done with other systems macro facilities in an elegant manner.

[ianrb]

9 hours ago, v_kyr said:

Which shows the overall limitations (and useless idiosyncosity) of Affinity's macro implementation. There's no real way to auto determine and deal with dynamic sizes and orientations for documents/images here, also there is no file i/o and dynamic text handling support etc. - All in all it's pretty useless for all those tasks, which can be done with other systems macro facilities in an elegant manner.

I have to agree ; the macro system is rather messy .
Instead of make big/complicated macros, I find it easier to make a number of smaller macros and then make those smaller macros into a bigger one button macro . If changes are needed (seems often for me) I  just need to edit the small part and then remake the big macro

Cheers all

[v_kyr]

47 minutes ago, ianrb said:

I have to agree ; the macro system is rather messy .
Instead of make big/complicated macros, I find it easier to make a number of smaller macros and then make those smaller macros into a bigger one button macro . If changes are needed (seems often for me) I  just need to edit the small part and then remake the big macro

Personally I don't hazzle around with APh and macros for such usually simple and silly to do tasks, instead I use things like ImageMagick and Python scripts to add borders and the like.

[ianrb]

12 hours ago, v_kyr said:

Personally I don't hazzle around with APh and macros for such usually simple and silly to do tasks, instead I use things like ImageMagick and Python scripts to add borders and the like.

Never heard of those apps ; I wonder what else I don't know 😅
Maybe easier just not having using borders  !
I have this layer effects macro for adding border and shadow to layer images . Ratio makes does not any difference and it all adjustable . Once I have made adjustments to one it's just a case of copy + paste FX to other layers
Works well once I got the macro working , however there are limitations which I have forgotten now .
Bottom is the basic macro

[v_kyr]

2 hours ago, ianrb said:

Never heard of those apps

• ImageMagick
• ImageMagick - Image Edges, Border, adding space around the image ...
• ImageMagick examples - Cutting and Bordering

Python is a very powerful interpreter based programming language, with a very rich module concept and which is also predestinated for scripting!