Hangman

Hi @jimacad, That's really great to hear, I'm glad everything is working for you now so you can get back to work...

Hi @jimacad and another warm welcome to the forums, It may be worth trying a factory reset by holding the Ctrl Key down while launching Affinity Designer. When you see the Clear User Data Screen leave the first three items selected click the Clear button let Designer finish loading and then see whether or not that fixes the issue... Let us know whether or not that makes any difference. If not then if you could provide the information @Komatös has requested that will be helpful for the moderation team at Serif in trying to diagnose the cause of the issue.

Hi @RHD fine art and design and welcome to the forums, Are your placed images Affinity Photo, JPEG, PNG or TIFF files? There is a known bug logged under AF-1390 that sounds very similar to the issue you're seeing and which is still awaiting a fix... If your images do happen to be placed Affinity Photo files then a workaround for the problem is to substitute the .afphoto cutouts for .tiff versions which should rectify the text wrap issue... I appreciate that's not ideal, especially if you have lots of cutout images in your publication but I'd perhaps take the images on one page, maybe the page shown in your screengrab, export the images as TIFF files, replace the Affinity Photo files with the TIFF versions, Save, Close and Reopen your document to see whether or not the text wrap remains in place... If your Placed images are not Affinity Photo files are you able to upload your Publisher file or even a sample Page along with any linked image files so we can take a closer look at what might be causing the issue?

Hi @Carolina Illanes, Many thanks for your sample files... This may not be quite what you're looking for as Publisher doesn't have an auto-update option, though you could equally argue that is a good thing so you don't inadvertently update your Publisher document when you don't want to but, you can link your Excel file to your Publisher document using Data Merge and insert the relevant fields into your text and then when you make any updates to your Excel file and Save the changes you only have to click the Update button in the Data Merge panel and then Complete the Data Merge for your changes will be reflected in your Publisher file... Possibly not as neat as linking Word with Excel or InDesign's approach but let us know whether you think this could work for you or not... Knitting Pattern.mp4

Hi @Dan C, Many thanks for your indepth testing here... It's interesting as the Colour Studio has always worked this way since incarnation on macOS... Noted… These are my observations based on your feedback on the macOS side, though all could be wrong... Scenario 1 Colour Studio Colour Sliders Change mode to RGB Using the menu, change this from 8 bit to 16 bit view Change mode to RGB Hex ⚠ Note this is now also using 16 bit I appreciate on Windows this is reset to 8 bit when switching modes resulting in a difference between Mac and Windows but I was trying to understand whether this is just the affinity apps showing a 16-bit representation of the Hex Value... #RGB (4 bits each) #RRGGBB (8 bits each) #RRRGGGBBB (12 bits each) #RRRRGGGGBBBB (16 bits each) or whether, in this scenario the Hex values should be shown using a RGB565 conversion, though if that were the case it would potentially negate transparency support, i.e., Colour Studio Colour Sliders Change mode to RGB Using the menu, change this from 8 bit to 16 bit view Change mode to RGB Hex In 16 bit RGB Mode, i.e., RGB565 #284BFF would appear as #0x2a7f Scenario 2 Colour Studio Colour Sliders Change mode to RGB Using the menu, change this to Percentage view Change mode to RGB Hex ⚠ Note this is now also using Percentage, which shouldn't be possible - the Hex values are also incorrect due to this... See my reply to @garrettm30 in the previous post, if I've understood the conversion correctly in this scenario the value displayed would appear to be correct based on the percentage selection, i.e., #284BFF correctly appears as #101D64 when the RGB values are set to percentage... Scenario 3 Colour Studio Colour Sliders Change mode to RGB Using the menu, change this from 8 bit to 16 bit view Change mode to CMYK ⚠ Note this is now also using 16 bit, which shouldn't be possible I appreciate that Affinity apps themselves don't support CMYK/16 but are we not just seeing a true 16 bit representation of CMYK values ranging from 0 to 65,536... Having said that, this was logged as a bug under AFD-6355 and AFD-6356 back in January 2023... AFD-6355 was shown as fixed in v2.1.0.1703/5 though in the current v2.4.0 when the Colour Palette is set to 8 bit, the CMYK sliders show 8 bit values in the Colour Palette, 16 bit values in the Colour Chooser Sliders and Percentage values in the Colour Chooser list on the right...

I've simply disabled the shortcut because it is so annoying but having it removed by default would be welcomed...

I'd been working with decimal conversions all day and had decimal on the brain, a classic case of thinking one thing, typing another, i.e., thinking percentage, typing decimal... So my logic for #101D64 being correct was based on hexadecimal representation of percentage values, i.e., when the RGB sliders are set to percentage: For Each RGB Hex Pair: Take the decimal equivalent of the first character for each colour from the chart and multiply by 16 Take the decimal equivalent of the second character for each colour from the chart and add it to the first value get the R, G and B values So for #284BFF Red: 2 x 16 = 32 + 8 = 40 Green: 4 x 16 = 64 + 11 = 75 Blue: 15 x 16 = 240 + 15 = 255 Convert the RGB Values to Percentages: Red: (40 / 255) x 100 = 16% (15.68%) Green: (75 / 255) x 100 = 29% (29.41%) Blue: (255 / 255) x 100 = 100% Convert the Percentages Values to Hex Equivalents: Take the Hex equivalent for the percentage value from the chart for each colour Red: 16 = 10 Green: 29 = 1D Blue: 100 = 64 So when percentage is set as the colour mode #284BFF translates to a Hex value of #101D64 That's because I mistyped the Hex Code, #2B48FF instead of #284BFF... I've now corrected the original post to reflect this, apologies for that......

Can confirm this is indeed the case...

Auto-update is the wrong term as in you'd have to click the Update option in the Data Merge Panel and Regenerate the merged Document, so it's a manual update and certainly not as flexible as linking the Excel file to Word but if I've understood the question correctly (which I may not have done), it's still technically possible to achieve, it's just a bit more long-winded in Publisher...

Hi @garrettm30, Hopefully, this will help but basically though technically the two different Hex values displayed are correct between the Wheel and RGB Hex Slider, it can appear confusing, so it's not a bug per se though may be considered one in as much as the two colour models don't display the same Hex value in the same way, the Wheel uses 8-bit, the Slider uses ... Steps to Reproduce With the RGB Sliders shown in the Colour Palette set the value to Percentage in the Colour Preferences Panel Change the Colour model to the Wheel (either is fine) Create a Shape and apply a Hex value to the shape, e.g., #284BFF Switch the Colour Model to the RGB Hex Sliders The Hex value in the RGB Hex sliders is shown as the decimal equivalent of #284BFF, i.e., #101D64 (which is technically correct) The main 'issue' here is that the two different colour models display the same Hex value differently and you can't switch the value from percentage to 8-bit or 16-bit when using the RGB Hex Sliders, you first have to go back to the RGB sliders to change the value from percentage back to 8 or 16-bit which I think has the potential to lead to confusion, hence my questions... Questions Should both the Colour Wheel and Sliders adopt a uniform display method, i.e., both display Percentage when that option is selected Should the option to switch from Percentage back to 8-bit or 16-bit be available when displaying the RGB Hex Sliders Hex Values.mp4

Hi @Carolina Illanes, Are you effectively using a grading spreadsheet to calculate the stitch and row counts? My understanding is that you want to maintain a live link between your Excel Spreadsheet and a Publisher document so that any updates to the spreadsheet will auto-update the Publisher file, would that be the correct assumption? If so, then this would be possible using the Data Merge feature of Publisher... What would be really helpful is if you have a sample spreadsheet you are happy to upload together with a sample Word document that shows how the knitting pattern is laid out in Word. With that we can put something together to demonstrate how that could work for you with Publisher, assuming the assumptions are correct...

Bonjour @Christian USL et bienvenue sur les forums, Pourriez-vous enregistrer votre fichier Publisher en tant que package afin qu'il inclue tous les fichiers liés, car il peut s'agir de l'un des fichiers liés à l'origine du problème d'exportation... ____________________________________ Hi @Christian USL and welcome to the forums, Could you save your Publisher file as a Package so it includes all the Linked Files as it may be one of the Linked files causing the export issue...

I could be wrong but I think the bug fix is only going to be how Affinity apps read eight-digit Hex codes rather than adding the ability to include the alpha channel info. Currently, the Affinity apps are reading the last six digits, i.e., the Green, Blue and Alpha and using those values as the colour to display instead of the first six, the Red Green and Blue which means they are displaying the incorrect colour...

Hi @Dan C, It is indeed, no issues with Monterey using either method, they appear to have effectively placed the scrollbar outside the text selection area in Sonoma when it appears within the text selection area on Monterey, though that may just be a visual change only...

Hi @DWright, You can test the version I created if it helps which demonstrates the same issue... Placed Artboards.zip

Hi @Rufus Reade, As @Alfred mentions, you are actually editing the PDF, not your original Publisher file which is why you see the text issues and can no longer place images, use text wrap or change your text boxes. If you re-open the original Publisher document all should be back to normal...

Hi @Dan C, Many thanks for bumping...

Hi @Rufus Reade and welcome to the forums, This sounds as though you've opened and are attempting to edit the PDF document in Publisher rather than the original Publisher file itself, is that the case? When exporting your file to PDF uncheck the Subset Fonts checkbox just below the Embed Fonts Dropdown in the Advanced section and see if that maintains your ligatures correctly when the PDF is opened in Publisher...

Hi @Jonopen, I don't know if there is an issue with either Sonoma and/or Apple Silicon but this is working as expected with Monterey on Intel... The one thing that isn't working is Page Up and Page Down to navigate to the next 'page' of the font list, this affects the font menus in the Context toolbar, Character panel and Glyph browser but works in the Text Styles font menu though I believe this specific issue is already logged... Glyph Browser.mp4

Hallo @Zotti, Können Sie ein Beispieldokument oder sogar eine Beispielseite des Dokuments hochladen, das das Problem aufzeigt, damit wir einen Blick darauf werfen können? Dies sollte zu einer schnelleren Lösung führen, anstatt dass jeder rät, was das Problem verursachen könnte ... ____________________________________ Are you able to upload a sample document or even a sample page from the document exhibiting the issue so we can take a look? It should lead to a quicker resolution rather than everyone guessing as to what may be causing the problem...

Hallo @Zotti und willkommen im Forum, Könnten Sie einige zusätzliche Informationen bereitstellen, z. B. Wie passen Sie Ihren Zeilenabstand über die Option „Zeilenabstand“ im Absatzbedienfeld oder die Option „Zeilenabstand überschreiben“ im Zeichenbedienfeld an? Ist in Ihrem Dokument ein Grundlinienraster aktiviert? Was passiert, wenn Sie versuchen, den Zeilenabstand anzupassen? ___________________________________________ Hallo @Zotti and welcome to the forums, Could you provide some additional information, e.g., How are you adjusting your line spacing, via the Leading option in the Paragraph panel or the Leading Override option in the Character panel? Do you have a Baseline Grid enabled in your document? What happens when you try to adjust the line spacing?

Hi @Carolina Illanes and another warm welcome to the forums, Could you perhaps provide a little more information in terms of what you want to achieve... You can certainly copy text from an Excel Spreadsheet and paste it as unformatted text in Publisher but the text wouldn't have any direct link back to your spreadsheet so changes made to the spreadsheet wouldn't be reflected in your Publisher document... Publisher does have a Data Merge feature which would link back to your spreadsheet and reflect any changes made but each row and/or column of text would appear effectively in a cell in Publisher though you can still determine the layout of the content so it doesn't have to be a rigid table format, e.g., you could use Data Merge to create Business Card artwork with N-Up per page... Note: Data Merge is an Affinity Publisher option so not available in Affinity Designer or Photo. If you are able to let us know what you are attempting to do we can hopefully, provide some alternative options for you. You can also download a trial of the Affinity apps from the Serif website if you want to try them out to see if they meet your needs.

I'm not sure of the end goal here other than joining the respective nodes and I appreciate that you've deliberately used square caps for demonstration purposes but based on your screen recording alone, would changing these to butt or round caps (depending on your preference), aligning the nodes and then merging the layers not achieve the same end goal where you have all your tree branches as a single layer? Edit: @MEB beat me to it... Tree.mp4

Hi @nemoDreamer and welcome to the forums, This looks like a bug... Balanced strokes up to and including 2.5 pt are being exported as unbalanced strokes Balanced strokes above 2.5 pt are being exported as expanded strokes My understanding is that all balanced strokes should be exported as expanded strokes on export to PDF.

Bonjour @Delphine34140, Portable Network Graphics (PNG, prononcé officiellement /pɪŋ/ PING, prononcé familièrement /ˌpiːɛnˈdʒiː/ PEE-en-JEE) est un format de fichier graphique raster qui prend en charge la compression de données sans perte. PNG a été développé comme un remplacement amélioré et non breveté du Graphics Interchange Format (GIF) - officieusement, les initiales PNG signifiaient l'acronyme récursif « PNG n'est pas GIF ». PNG prend en charge les images basées sur une palette (avec des palettes de couleurs RVB 24 bits ou RVBA 32 bits), les images en niveaux de gris (avec ou sans canal alpha pour la transparence) et les images RVB ou RVBA en couleur sans palette. Le groupe de travail PNG a conçu le format pour le transfert d'images sur Internet, et non pour des graphiques imprimés de qualité professionnelle ; par conséquent, les espaces colorimétriques non RVB tels que CMJN ne sont pas pris en charge. Un fichier PNG contient une seule image dans une structure extensible de morceaux, codant les pixels de base et d'autres informations telles que des commentaires textuels et des contrôles d'intégrité documentés dans la RFC 2083. _____________________________________________ Portable Network Graphics (PNG, officially pronounced /pɪŋ/ PING, colloquially pronounced /ˌpiːɛnˈdʒiː/ PEE-en-JEE) is a raster-graphics file format that supports lossless data compression. PNG was developed as an improved, non-patented replacement for Graphics Interchange Format (GIF)—unofficially, the initials PNG stood for the recursive acronym "PNG's not GIF". PNG supports palette-based images (with palettes of 24-bit RGB or 32-bit RGBA colours), grayscale images (with or without an alpha channel for transparency), and full-color non-palette-based RGB or RGBA images. The PNG working group designed the format for transferring images on the Internet, not for professional-quality print graphics; therefore, non-RGB colour spaces such as CMYK are not supported. A PNG file contains a single image in an extensible structure of chunks, encoding the basic pixels and other information such as textual comments and integrity checks documented in RFC 2083.