Sean P
-
Posts
10,115 -
Joined
-
Last visited
Posts posted by Sean P
-
-
1 hour ago, ronnyb said:
@Sean P thanks for the prompt reply and staying on top of this one, much appreciated! Yes, the Precise Clipping is the issue!
FYI, the issue persists in the new 2.5 beta.
You're welcome! Glad I could get to the bottom of it - I've updated the issue with the latest version.
-
2 minutes ago, EricP said:
Thanks for this feature, it's going to be great
Found an issue when expanding strokes
Could you attach a copy of that line with the curve (pre-expanded please). I've got one to expand slightly incorrectly, but not had anything expand quite like that has!
-
1 hour ago, Return said:
Works on windows.
Thanks! Interestingly it looks like it could be upgrades from 2.4.2 that is causing the issue. If I ctrl run up I don't get a problem (like you're not), but if I do an upgrade from 2.4.2's User Data I get the issue.
-
1 hour ago, dominik said:
Clicking does add a new pressure point but with zero width! To me this looks like a bug. I would expect it adds a point but does not the line's width at that point.
d.
Thanks - I've logged this to be looked at.
-
47 minutes ago, dominik said:
OK, correction: for some reason I cannot get this tool to work in APub's Designer Persona. In AD it does work as described above.
d.
45 minutes ago, anto said:Line Width Tool does not work in Publisher - Designer Persona
Thanks for letting us know I'll get this logged
-
-
I've just poked the file some more and found its down to using semi transparent gradient stops in the Gradient Overlay FX with Artboards.
Does the issue go away if you delete the artboard and keep the objects? Also can you attach a screenshot of the Performance section of the Settings dialog for the affected apps please?
How does the Navigator Panel render as well? -
Thanks for re-uploading! I will check back later on
1 hour ago, ronnyb said:I don’t think so, that doesn’t make any sense, otherwise why does Publisher render the file fine but Photo and Designer fail at rendering the same file on my computer with the same setup?? Also, why did it render fine before the last beta, now it’s broken (only in Designer and Photo)? Remember this bug started as a bug only on export, now it has crawled into the main rendering display… my setup has not changed at all, same monitors etc.
Because the issue you're seeing looks related to the way things are being rendered, and having different monitors of multiple resolutions and scalings have caused rendering issues within the app. There were many variables as I said based on where the app window was, and the screen the app was started on that caused the rendering to be different so I want to try and rule these out.
There was an issue that was causing Effects to be output incorrectly to PDF and the Export Preview was representive of this. The only way you would have seen that in the main window, was if you was importing the exported PDF back in, which I assume is not what you're doing?Have you tried opening this with external monitors disconnected at all or on your iPad as I suggested please? Also are you able to attach a video recording of the whole screen from a fresh launch that demonstrates this please?
-
Unfortunatley it looks like that upload might have failed as I can only see your original file and no package - not sure if thats because the zip on Dropbox is the same name as the one you tried to upload?
I've had a look on a different MacBook Air and it is still rendering fine for me on both Designer and Photo 2.4.2.
Your sig mentions Ventura - are you still using this or have you upgraded to Sonoma? All the machines I'm using are Sonoma.Also regarding screens have you tried disconnecting any external screens and just using the Macbook Pro's built in screen? I'm wondering if this is another issue that is being exhibited, by the rendering oddies that appear when using two screens with different scaling. As I mentioned previously the screen you launched the app on and the app window on all has an affect on what happens, so that might explain potentially why 2.4.1 Retail looks fine and 2.4.2 isn't/2.4.2 Publisher is ok.
Have you tried loading the file on your iPad to see how it renders on that?
-
Thanks for the file Ronnyb.
I've tried it on my iMac (Intel Sonoma), MacBook M1 Pro (Sonoma) with an XDR dsiplay and also had a few people try it on their Macs (combination of Macbook Air M1s and iMacs) and we're all unable to reproduce what you're seeing with 2.4.2. I did also install the Alumni Sans fonts (both from Adobe fonts and Google Fonts) and whilst most were detected, the main text wasn't, however I don't feel this would cause the problems you're seeing. Photo, Designer and Publisher all displayed the same for me.
-
Hi Ronnyb,
Please use this link and we'll take a look!
https://www.dropbox.com/request/4MhCvJkTqRaZ6fZMkxV8 -
Hi Philipt18
I've passed the crash logs on to development who have said that the crashing is coming from Preflight checks relating to a broken or unexpected pinned object glyph within the file (as @Pauls suggested above). These will be specific to the document you are using, so unfortunately without that, we are unlikely to be able to reproduce the crashes you're seeing. If you could send us the document you're using to our internal Dropbox account then we can try to investigate more.
Also if you're able to find or remake the video demonstrating the crash that would also be very helpful. In the meantime can you try disabling Preflight and see if that stops the document you're using from crashing, please? -
42 minutes ago, Hangman said:
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...
No worries - that is a shame though!
Do you happen to use external monitors with your Mac at all? -
2 minutes ago, Hangman said:
Hi @Sean P,
Is that a Windows file path you've referenced?
D'oh It is indeed, I had it in my mind you were on Windows. Thats certainly not going to help you on macOS is it! Unfortunately macOS isn't as simple as Windows, but if you try and temporarily rename the 'com.seriflabs.affinitypublisher2.beta.plist' (whilst the app is closed) from the location below and then the app. It should generate a new plist with the default options, and see if that is still causing you problems.
~/Library/Preferences/Thanks!
-
Hi Hangman,
I'm wondering if this is a setting you've got on the Beta? Could you try renaming the '2.0 (Beta)' here: %userprofile%\.affinity\Publisher\ so a new one is created and then see if that is affected.
If it is not would you be able to zip up a copy of that folder and send it over please? -
-
Ahh I'm seeing this now - I suspect this is actually By Design.
When Filler Text is inserted as Filler Text it will always add text to fill the space it occupies. This means that if you have some text after that point it will get overflowed (as evidenced by the Overflow marker on the text frame), so when your clicking to fit the text, its fitting it and then the filler text is likely filling up the space, forcing it to overflow again.
I'll pass it on to development to see what they suggest, but I'm not sure mixing filler text with real text is a proper use case - certainly nothing I've ever encountered before!
EDIT:
Just to add: As filler text will always add text to fill the space it doesn't have a defined word count, so this means it cannot ever flow to a defined page count, so will only do it page by page. -
That is very strange! What Input Source is your macOS set to, and do you have any other utilities running that might interfere or relate to the keyboard at all?
-
What macOS Keyboard Layout and physical keyboard model are you using? I've tried it with both British GB and Ukrainian layouts using the built in keyboard on a Macbook Air and its still behaving as expected.
-
Hi Anto,
This is working fine for me using 2.4.2.2371. It looks like you may have option held down instead of shift? Holding Option and clicking will flow the frame page by page (which is what is happening in your video), where as Shift will flow the entire contents and make as many pages as it needs.
-
Thanks very much for the file! I can reproduce that here and it looks like its potentially related to the fact that the Warp Group has moved quite a distance from its origin. I'll get this logged with the development team.
In the meantime if you place your image inside the curve (and remove the frame) it should be able to achieve what you want - see the attached file. -
Hi Anto,
I think the issues you're seeing are very specific to the way your using Mesh Warp groups. Looking at what you're trying to do I don't understand why you're using a picture frame for the image. Just clip the mesh warp to the image you want to use for the shadow; the Picture Frame seems pointless in this instance.Would you be able to attach the document your video shows please. When reporting stuff please do try to attach all supporting files you've used to replicate your issues as these can be a massive help to us.
Either way I've tried to replicate the layout your video shows but I don't get any rendering issues you're seeing. I've attached the file I've used and a video showing the rendering behaviour I get.
-
On 3/29/2024 at 7:32 PM, loukash said:
… and it doesn't have a text search field to highlight words on the page, like browsers – and even the pathetic Apple Help app do.
Sometimes help pages are long, and the user needs to search for a keyword within the page.On 3/29/2024 at 7:34 PM, loukash said:Also, this "browser window" doesn't react to cmd-W (Close) command, even though it has focus. I wanted to close it with cmd-W and the main Affinity window was closed instead.
On 3/29/2024 at 8:34 PM, MikeTO said:The new Affinity window help has a much better default font size than the Mac system help which is great butthe user can adjust Mac help with +/- while the Affinity window doesn't support this accessibility feature.
But I fully agree that the lack of a text search field and Cmd+F is a big deal, I always jump to what I want with Cmd+F.
On 3/30/2024 at 8:46 AM, Paul Mudditt said:What I don't like about the web browser version is it vanishes when another app gets focus which was very unexpected.
On 3/30/2024 at 6:50 PM, walt.farrell said:It is missing in 2.4,2 beta, but it sounds like that may be intentional? At this point, the Help on macOS works basically like the Help on Windows, except that the Help browser on Windows uses the built-in Help files not the online Help site. I think the Windows approach is better.
Additionally, the way the current 2.4.2 beta is working removes one useful aspect of the macOS Help system. The macOS system doesn't just search the Help, it also searches the application menus, and cal let you select a menu item directly after searching for it. E.g.,
On 3/30/2024 at 7:16 PM, MikeTO said:I assumed that the missing help search field was just the normal bug and not intentional. If it's intentional, I agree, we need it back because it's how we find menu commands. At least when it's working. 🙂
Thanks all for your comments! I just wanted to let you know that these have all been logged and with development.
Regarding the actual missing search bar, unfortunately, that is currently to be expected due to (as I understand it) its reliance on the macOS Help Viewer. However, we are aware of this and are looking into a replacement for it!
-
On 3/28/2024 at 11:47 PM, philipt18 said:
Here's a video of the 8th crash.
https://share.zight.com/WnuXg0yD
I was doing the exact same thing as the 6th and 7th. Crash log attached. Oddly, I'm not sure why I needed to do what I was doing. The text was overflowed, but I have no idea why. Last time I saw that page it looked fine. So I started deleting empty lines until my text showed up at the bottom of the page, and then it crashes. The first 5 crashes were not the exact same action, but happened in a fairly short period of time.
Affinity Publisher 2 Beta-2024-03-28-194231.ips
Hi philipt18,
Unfortunately, this link isn't working for me - are you able to resend it, and if possible with a link to the file you're using, please? Is it the same file you're having crashes with or has it happened with several unrelated ones?Thanks!
.png.7714d5f3d4858764ec550f51c398952e.png)
Line Width Tool
in 2.5 Beta New Features and Improvements
Posted
There is an indicator on the nodes themselves to let you know if you're changing one or both.
When they have a dot in the middle it means you're affecting both start and end node. If there isn't then it will only adjust the one you change. You can single click on them to switch between the two states.
Adjusting both start and end node position:
Adjusting single node position: