Hangman

Hi @phillencolin and welcome to the forums, It's because the width and height are undefined... If you change both to say 1024 and Save your file should open in both Designer and Photo (see attached file)... <svg xmlns="http://www.w3.org/2000/svg" width="1024" height="1024" viewBox="0 0 8 8"> <path fill="currentColor" d="M5 1L2 7h1l3-6H5zM1 2L0 4l1 2h1L1 4l1-2H1zm5 0l1 2l-1 2h1l1-2l-1-2H6z"/> </svg> code.svg

Hi @Callum, Perfect, many thanks for logging...

Hi @leec2024 and welcome to the forums, I'm assuming you have the English (United Kingdom) dictionary selected in the Character panel rather than just the English dictionary which is the US English dictionary...

Hi @Dennison, This is a known bug logged as a bug under AFB-7732 and AFB-7733. It's caused by having text frames with two differing resolutions which can be caused when opening IDML files or by changing the document dpi directly in a Publisher-only document between text frame creation... Based on the change in text size from 10 pt to 2.4 pt this suggests that either you've opened an IDML file which Publisher interprets incorrectly at 72 dpi or if created from scratch in Publisher you've changed the document dpi from 72 dpi to 300 dpi in between creating text frames, my assumption is the former... To prove this (based on your screengrab) do the following: Steps to Correct Unlink the text frames on the left and right pages Delete the text frame on the right-hand page with the 2.4 pt text Go to Document Setup and change the document dpi from 300 dpi to 72 dpi Recreate the text frame on the right-hand page Relink the two text frames Go to Document Setup and change the document dpi from 72 dpi to 300 dpi Save the document You should now see the text in the text frame on the right-hand page appear correctly at 10 pt. Note: This will affect any text frame in your document inherited from the source IDML file if that is the source for your document so you may need to repeat if you find other instances throughout your file.

Hi @Chris B, That's interesting and thanks both for the update and for testing further... I'd certainly be interested to know what you discover should you manage to track down what is causing this, it's a really odd one...

Hi @Sukavi, Are you able to upload the file in question so we can take a look at what might be going on? If it's a file you'd rather not upload to the public forums you can request a private Dropbox link by replying to this message and someone in the moderation team will respond...

Hi @Dan C, Since it's always been possible I'd just assumed it was by design though admittedly I can't think of any logical or practical use for it if it were so many thanks for logging this as a bug...

I agree and I'm sure you're right as it would make far more sense...

Quite possibly, in which case a little line merging and nesting (as per your clip) will resolve that...

Hi @NathanC, That makes sense, thanks for clarifying...

That's because it doesn't appear as part of the logo or the placed Photoshop file, it has been added to the Publisher file directly...

Hi @NathanC, I'm slightly unsure what the expected behaviour should be here, i.e., would you only see the result of the Luminosity Mask once an adjustment had been made to the Exposure, however small that adjustment is? When no adjustment has been made to the exposure, clicking Preview in the Luminosity Range Mask shows a Blank White canvas as does the Shadows Preset with the Midtones and Highlights Preset showing a black canvas despite the adjustment made to the Luminosity Map... Making a tiny adjustment to the exposure, e.g., 0.1 then shows a preview once the Preview option is selected in the Luminosity Range Mask... is this what would be expected?

Hi @Mikezots, Did you mean to post this in the Windows forum or were you trying to open the file using the Windows version of Publisher? Your file opens without issue for me but that could be because the PDF on Page 4 is Linked so I don't have access to it. That particular file Mendis Front.pdf is shown as Linked (Remote) in Resource Manager because it's located at... ../CloudStorage/Dropbox/Landscape projects/CS Mendis/Consult notes/Mendis illustrations/Mendis Front.pdf I would try renaming the PDF or moving it to a different location so it's shown as Missing when you attempt to open the Publisher file and see if the Publisher file opens and if it does move the PDF to your internal Hard Drive and relink it. Let us know whether that works... I've resaved the Publisher file and attached it here but I suspect you'll see the same issue until you resolve the linked PDF. Mendis CS New.afpub

Hiallo @RandyPuh und willkommen im Forum, Ich glaube nicht, dass dies funktionieren wird, da beim Exportieren in PDF der Erase-Mischmodus gerastert wird, was dazu führt (siehe die angehängte Datei Banner_700_x_1000_(C)_Erase.pdf)... Ein Ansatz zur Vermeidung der Rasterung wäre, die Datei im Designer zu öffnen, die weißen Striche des Kirchenumrisses im Logo auszuwählen, sie zu erweitern und sie dann von den grünen abgerundeten Rechtecken zu subtrahieren. Dies hat den Vorteil, dass beim Export in PDF nichts gerastert wird (siehe angehängte Datei Banner_700_x_1000_(C)_Subtract.pdf), was dazu führt... Hier sehen Sie jedoch das offensichtliche Problem: Wenn Sie versuchen, die Umrisse der Kirchen in der gleichen Farbe wie 50 % Hintergrundviolett zu gestalten, verlieren Sie aufgrund des Kontrastverhältnisses zwischen Grün und Lila jegliche Definition, also lassen Sie es besser Umriss der Kirche nicht in Weiß zu verwenden oder die Farben völlig neu zu überdenken, um den Kontrast und die Lesbarkeit zu verbessern ... Banner_700_x_1000_(C)_Erase.pdf Banner_700_x_1000_(C)_Subtract.pdf

I'm unsure whether this has been logged as part of AF-1822 where it isn't possible to apply Set Selection Box after Cycling the Selection Box to Regular Bounds for objects rotated by 90°, 180° and 270°. The 'workaround' for this bug is to offset these specific angles by .01° to say 89.99° or 90.01°, 179.99° or 180.01° and 269.99° or 270.01. Doing so allows Set Selection Box to be enabled. The issue, however, is that while using the workaround should allow Make Same: Width and Make Same: Height to function correctly it doesn't, both incorrectly use Base Box instead of Regular Bounds values when enabling 'Set Selection Box'... Note: This affects both Grouped and Non-Grouped Objects...

It does work but as mentioned above you have to consider the orientation of the Regular Bounds Bounding Box... If you have grouped objects with a width of 50 mm and a height of 100 mm rotated by 90°, the Regular Bounds Bounding Box will still be 50 mm wide x 100 mm high only orientated by 90° despite visually appearing to be 100 mm wide and 50 mm high... Make Same: Rotation does work for Groups... There are three bugs here, two of which are already logged... AF-1761 - Lines should use Regular Bounds rather than Base Box when grouped... AF-1822 - It's not possible to apply 'Set Selection Box' after Cycling the Selection Box to Regular Bounds for objects rotated by 90°, 180° and 270°... The third bug which is a direct result of the second bug and I don't believe is logged yet is that even after Cycling and Setting the Selection Box for either the Group, the contents of the Group or both to Regular Bounds, Make Same: Width and/or Make Same: Height fail for Grouped Objects...

Hi @NathanC, Many thanks for testing and logging... I note that @Super Alpine is on Sonoma so does this suggest the bug they're experiencing is different?

No, this is just the MacBook Pro screen...

Hi @Sean P, No problem... Renaming the 'com.seriflabs.affinitypublisher2.beta.plist' (whilst the app is closed) and renaming the app makes no difference. A new plist file is created but the problem persists in the Beta... In many ways, I guess it's perhaps not so relevant since it's working in the Retail version but it's still very odd... Let me know if you want me to upload any specific files from the Beta...

Hi @Sean P, Is that a Windows file path you've referenced?

FWIW, I tested it using the Hunspell Danish spelling and hyphenation Dictionaries installed and had no issues...

I believe @walt.farrell is referring to /Users/username/Library/Spelling, i.e., the location of the Dictionary files on your Hard Drive.

Hi @NathanC, I'm unsure whether this is the same issue but I can replicate the failed toggle shortcut behaviour using the following steps: Steps to Reproduce Launch Publisher If the Tab Key is already set as the Toggle UI keyboard shortcut remove it With no keyboard shortcut set for Toggle UI create a new document or open an existing document. Hit the Tab Key (once is sufficient to trigger this) - Note: this is the key step Open the Settings panel and set the Tab Key as the Toggle UI keyboard shortcut Close the Settings panel Hit the Tab key to toggle the UI and nothing happens Create a new file or open another document Hit the Tab key to toggle the UI and nothing happens Manually select the first document tab, hit the Tab key to toggle the UI and nothing happens Manually select the second document tab, hit the Tab key to toggle the UI and nothing happens Ctrl-Tab to switch between documents The Tab Key now works and hides/shows the UI Note If both documents are closed without closing Publisher and Steps 2 to 10 above are repeated using Ctrl-Tab to switch between documents can sometimes result in the Tab key no longer working for either document.

The update is working without issue for me, do you see the same issue after rebooting either the app or rebooting your Mac?

Hi @Chris B, Interestingly, this is now working correctly in the 2.4.2.2371 Retail release but not in the 2.4.2.2371 Beta despite not appearing on the Retail Bug fix list...does that make any sense? 🤔