vonBusing
-
Posts
300 -
Joined
-
Last visited
Posts posted by vonBusing
-
-
4 hours ago, MikeTO said:
Here's a bug report with a lot of light mode issues and one dark mode issue.
Thanks @MikeTO for compiling and filing this. I was thinking yesterday that this should probably be filed as a bug, but didn't get further than starting to search if it was already reported as such or not.
-
Apparently the icon contrast is not consistent. While it is perfectly OK in the Transform panel in light UI:
It fails in the Document setup dialogue box (see previous post) .
-
I use the Default OS contrast, which is light in the day and dark in the evening, all in default settings. The contrast is somewhat better in dark mode, but it could be expected to be acceptable for fairly normal eyes with these settings, in both modes. Enabling high UI contrast did not change the contrast of the actual icon.
-
I've been confused with the locked proportion icon since the v2 introduction. With v2.1, I am still confused. It is very hard to tell what the icon is actually showing, so it's a 50% chance of fail each time. Maybe the contrast is too poor:
-
22 hours ago, Catshill said:
Unless I've missed something V2 still does not remember (or allow you to set a preset) the File settings Area
Disappointingly, you still have to remember to change to change it from "All Spreads" to "All Pages" which is what commercial printers require.
Grrr.
Yes, noticed that too 😩. One could think that this a very low hanging fruit that should be programmatically very easy to fix, but still not fixed in version 2.0. Maybe Serif will one day explain this incomprehensible choice.
-
I am facing similar issues when saving files from Affinity Photo, Designer or Publisher (all 1.10.4 releases on macOS 10.15.7 Catalina, on 2019 Intel MBP). As soon as a file dialogue is required (new file/new name), there is a very big risk of infinite beach ball. Does not happen when saving existing file.
I thought first it was the latest update of Default Folder X that needs to load with each file dialogue, but reverting to a previous version did not help.
-
21 minutes ago, Fred Lespine said:
Thanks. I tried it but Designer crashes as well. 😐
Yes that was my personal experience as well, but Photo was somehow, able to do the trick even if Designer failed.
Re-importing exported pdf is kind of a last resort as you can retrieve the content and layout. But to keep sanity in future document maintenance you will have to manually restore the full structure, which can be a tedious task on a large document.
Working with the beta is easy. It stays in parallel with the release version without interfering. That also means you have to separately import color palettes, assets libraries, brushes... that you would use in with your documents.
-
3 hours ago, Fred Lespine said:
Same here, I have a bunch of files that I was supposed to update but I cannot reopen them anymore. 😓
But I'm still running an old Mac Sierra version, so I'm not sure that the OS is involved...Fred, you could try as suggested above to open the files in Designer or Photo if you have them available (I had best success with Photo), save and reopen the file in Publisher.
Alternatively, you could download the latest Publisher beta (at the time of writing version 1.10.2.1167) that seems to be much more stable when opening older Publisher files. I had no issues reopening files I saved through this beta in the current release version of Publisher, but you still might want to work on copies of your files, just in case.
-
+1 for the ability of linking to text in an external file (that can thereby be used by several publisher files).
Supernice if markdown/html would be recognized for semantics, and a fantastic bonus if styling of the imported text could be linked to the document text styles (for example with matching html class attributes).
-
On 10/4/2021 at 11:56 AM, Pauls said:
if you can reopen them saving will work around this bug - Ther will be a fix coming in 1.10.2
When is 1.10.2 expected? I have similar issues with several files and it is quite disturbing. I suspect possible issues with linked files that could be the culprit. But it is not possible to relink them if the app cannot survive opening the documents in the first place.
-
-
8 hours ago, firstdefence said:
Make a song with this in it: Added support for OpenType reverse chaining contextual single substitutions. lol!
Good for them they fixed this, although I have zero clue what that means. There are 2 parts left and right of "reverse chaining" that could, maybe, be understandable,. But how "reverse chaining" is connecting them is not even Greek to me. But it sounds like pretty good song material.
-
-
-
I really appreciate that Publisher and Photo betas usually have the Auto-update option available. The download size is significantly smaller than a full software download (which is now worse than ever with universal apps). I wish Designer beta could offer that option more often.
See it as a sustainability goal: smaller downloads have smaller energy consumption footprint. Multiplied with the number of downloads, you have a substantial drop in the flood.
-
-
On 12/12/2020 at 7:06 AM, HarryMcGovern said:
I understood that the beta installed and operated as a completely autonomous app.
They absolutely do. I have no issues running both the release and the beta at the same time. They have separate support folders in the user's ~library/Application Support folder.
I don't know why the beta hijacked the file format for you, but it is very easily reset to the release version from the info panel of any afpub file.
-
Hi HarryMcGovern, You like to live dangerously with your files when you make this kind of beta (1.x) the default program. As stated in the disclaimer of this thread, files you open and save with this beta might not be compatible with the currently released 1.(x-1) version. In the same time, while new features are beeing tested out during these beta cycles, there are no guaranties that they will be compatible with the future released 1.x version. You might end with corrupted files.
Regarding your save folder issues, it is normal behaviour for applications to save by default in the same location were you opened the file, alternatively where you last saved a file. Regular applications working with documents don't "set up" folders for their documents. You can save them wherever you want. But you should definitively save beta files separately from your real working files to avoid the risk of corrupting real working file by mistake.
-
😳 Not seeing that on MBP 16" and macOS Catalina 10.15.7...
-
Universal apps! incredibly overweight apps are back in town...
-
2 hours ago, markw said:
Curious, why dose the App Registration think I’m using a 2010 Macbook Pro when it’s actually from 2017?
The same thing happens with the Publisher beta too.My hardware detection was accurate in both applications. Maybe an article number mismatch/duplicate for your model in the Serif lookup database?
-
2 hours ago, SarahPower said:
darn, I probably would not have bought this if I knew the data merge was not there!
I was excited at the prospect of not spending 70+ a month for adobe and purchased the suite based on all the positive reviews and from what I saw - but didn't remember the monthly mailers in my haste - I cannot lose InDesign without having that feature.
Does anyone know any work-arounds? plugins? other software? (besides Microsoft word)
Monthly mailer sound like some newsletter that could probably quite easily be handled by html/css/js. Any browser could make it to a pdf, if required.
-
-
Maybe you solved that, but did you try Copy and Paste (cmd-C with the app selected on the dmg and then cmd-V in the Application folder) instead of drag and drop?
QR Code Tool
in 2.5 Beta New Features and Improvements
Posted
I tried to enter multi-row VCARD data in the payload field and got a resulting QR code, but the phone would not recognize it as such: "no usable data found".