David in Яuislip

Ha ha, great catch. I've tried all sorts but the quickest way I've found is to resize the pixel layer, copy and File/New from clipboard then paste special/dib, dump the pixel layer. If you resize an image layer then File/New from clipboard you need to rasterise it first and go from there Quite unexpected behaviour, 'poo' is such an excellent comment too and much nicer than the one I usually use

Starting with a pixel layer Copy Paste special/DIB Convert to curves Add shape above Select shape and image layers Boolean intersect Add border if required

Yes, with exiftool, Photo V1 doesn't expose the NEFCompression field exiftool -NEFCompression *.NEF shows this ======== DSC_6063.NEF NEF Compression : High Efficiency* ======== Z-9_DSC_3111.NEF NEF Compression : Lossless and only Lossless works

Inkscape? WireframeSphere.svg

This is with V1, I don't even see the hours in the Time column So I changed the cell format from [hh]:mm:ss to one from the Excel Format Cells Time category and that's ok as long as the value is <24 N.B. hh:mm:ss doesn't work Attached file revised as noted, hopefully it'll work DPOSmine.xlsx

No but if you need negative values to be adjustable in a macro then read on Record a macro with the affine tool set to 180° and positive Offset X & Y values Then a second affine tool set to 180° and no Offset values Click the cog on the first affine and set the eyes Now, when the macro runs you will see the image rotated twice so it's back to 0° but the Offset sliders act on the first affine so a positive value becomes negative, err I think. It's all a bit cuckoo AffineNegative.afmacro

Clunky is more polite than my word What I've done is write some text with the standard bullet styles, modify them then create new styles. I don't understand what level means for bullets but if you need to create a level 4 bullet then change the Left Indent & First Line Indent I've attached a simple file so that you can see what I did BulletStyles.afpub

Open a macro panel, import the macro then add it to the library. If you have many images to process you can use New Batch Job and call it from there The Help will probably be useful Look up Das Panel "Makro" Importieren von Makros and Die Stapelverarbeitung

In Photo I would extend the canvas so the width = height Here's a macro which does it, width & height must be even number of pixels SquareImage.afmacro

I didn't watch the video but if I needed to split an image into S M & H I'd make 2 copies and use Blend Ranges on each, that way you have control over the cutoff points. There is Select/Tonal Range but I've never found that useful

@Paradise33 I've redone the xml, Photo now detects the camera automatically AutelEvoPro2.xml

18MB to 1MB is quite a jump, I'd suspect compression artefacts. The histograms are for the entire image not the crop The forum software has mullered your images, you may get a more informed answer if you post them in a zip file Seaweeds.zip

Can you show a layer stack in Photo then describe how these layers are opening in Photoshop? I have noted that if the bottom layer is a pixel layer with no transparency then it will open in Photoshop as locked If it has some transparency it will open in Photoshop as a layer with no lock If the bottom layer is an image layer it will open in Photoshop as a layer with no lock Layers above the bottom layer never open in Photoshop as locked This is my experience with Photo V1, V2 may differ However, if I needed to swap psd files with Photoshop users commercially then I would use Photoshop

First, I found that ~Library/Spelling has a couple files 'en' and 'LocalDictionary', and that the first of those has most (or maybe even all) of the words for which I've invoked Learn in APub, including the example names I cited above (with their possessive forms). I'm guessing that the second file has words for which I've done the equivalent of Learn in MS Word (which is where I do most of my writing). Those are potentially useful discoveries that suggest that APub spelling correction on Mac indeed uses MacOS facilities. I'm flying a bit blind here but I would make a copy of the 'en' file. Assuming it contains Ngakɔshi ) Ngaguyɔ ) which worked and Ngakɔshi's ) Ngaguyɔ's ) which didn't I would delete them or do it officially through Publisher Unlearn Then I would place the attached files, en_US.dic and en_US.aff, in the folder suggested in the video. I assume you're using US English, if UK then change US to GB Second, I'm a newbie on this forum. David, you said "have a bump and hopefully someone from Serif will pick this up." Is there something specific I can do to explicitly increase the likelihood of that? A bump is just another post to raise its profile, you can always click the three dots, message top right, and report it Third, David, my Preferences/Tools doesn't have that additional dictionary folder option. I know that now so I dumped the image and replaced it with a video link Keep at it, you're nearly there! en_US.dic en_US.aff

Beaten but I'm still going to post it

When I played about with this a while back I was surprised that the additional dictionaries supplemented the main dictionary, had this not happened I would have copied the entire dic file and modified that I'm sure I remember reading that the Mac system was based on Hunspell https://apple.stackexchange.com/questions/402822/locating-the-file-in-which-a-dictionary-word-is-stored however, if a text file that uses the Hunspell protocol can't be found then I think you're goosed. That link was using OSX, maybe Big Sur is different In Windows under Preferences/Tools I can add additional dictionary folders, do you not have that on a Mac? See if this video helps Anyway, have a bump and hopefully someone from Serif will pick this up

I gave up with the Learn thing after I realised the palava to Unlearn Instead, for writing in UK English, I created a folder here C:\ProgramData\Affinity\Common\1.0\Dictionaries\en_GB which contains en_GB.dic and en_GB.aff Entries in these files supplement the main dictionaries in C:\Program Files\Affinity\Publisher\Resources\Dictionaries\en-GB My additional dic files have technical words in Dutch, Slovenian and Russian and everything works well The advantage of this is that words added to the .dic can have the Hunspell suffixes which the Learn thing doesn't do ie add Ngakɔshi/M Ngaguyɔ/M into that .dic, the word is recognised and so are the posessives, this is the content 6 squorrox tehnične technisch технический Ngakɔshi/M Ngaguyɔ/M Note that the Publisher screenshot shows no errors for these only Erra which demonstrates that the spell check was on This is the .aff SET UTF-8 TRY esianrtolcdugmphbyfvkwzESIANRTOLCDUGMPHBYFVKWZ ONLYINCOMPOUND c COMPOUNDBEGIN U COMPOUNDMIDDLE V COMPOUNDEND W SFX M Y 1 SFX M 0 's .

Linked layers don't survive, layers grouped in Photoshop do

Layer effects, I think V2 calls them Quick FX Copy the source object, select the target object and do Edit/Paste FX - that's V1 hopefully V2 is similar Adjustment layers can be copied, then select the target layer, choose an appropriate position from the Insertion icons, paste

To create a preset you need at least one slice Create the variations, 20w, 30w whatever then follow the pictures below to save it To apply the preset, highlight the slices to be modified and select the preset from the dropdown The whole thing is a bit jargonified and the Help didn't help me much, eg Export preset—presents slice presets offering common graphics formats and options for Apple app icon design. I prefer to think of it as Export preset—presents slice variations etc

That will end in tears, try a different approach If you group objects Apply the gradient to the group (Photo parlance, Publisher calls it the Fill tool as does Designer I think) Select bitmap fill Size, change angle as desired Now select one of the objects and you can move the gradient origin without resizing Additional objects can be added to the group: Add an object Nest within the group Select the group gradient Move the gradient origin a smidge and the new object will pick up the group gradient A recolour layer within the group ought to work

Photopea can get the guides from a Photoshop jpeg which can be saved as a psd which Affinity can interpret

Photoshop does save guides in a jpeg but the only software I have that will display them is Photoshop - the example uses CS2 To get the guides into Affinity save from Photoshop as psd, psb or tiff

Select layers Click Create slice button Apply Export preset All highlighted slices change from Single PNG to whatever your preset creates, in this case 20w, 30w & 40w pngs Export slices and 12 files are output

If the file contains the GPS data then use Metadata/Detail and you'll see something like this