4dimage Posted December 2, 2022 Posted December 2, 2022 Just posted a little "tutorial" on how to use image pathes. There is also a ZIP with all files included in that post: I found a bug in the preview section of the data merge assistant window: I saved, closed the Publisher file and reopened it. Opened the assistant window und clicked "Aktualisieren" to sync the data source. Now in the page flip widget i can not longer switch from page to page 1, 2, 3, ... with the inner arrow buttons but only jump to the first page or the last page (left and right buttons). I can still jump to a specific page by doubleclicking the page number input field and typing the raw page number in by hand -> blur -> preview jumps to this record. What I notice is that the page number is followed by a semicolon "1;" - which is a typical CSV seperator in german CSV schema. This was not when i first added the data source and did all the initial data merge setup. Then i saw only the pure numbers [1,2,3,4] and could switch from page to page with the inner arrow buttons. The Excel spreadsheet seems to be ok? Also tried to delete the data source in the assistant and import the fotos_1-1.xslx again. Now it's always showing up the semicolon after the page number in the page flip widget 🤔 Is there a CSV separator error when importing/storing/reopening the Excel sheet in the Publisher file? Some Windows localization CSV schema collision ? Quote Hardware: Windows 11 Pro (24H2, build 26100.3775, Windows Feature Experience Pack 1000.26100.66.0), Intel(R) Core(TM) i9-14900K, 24 Core@3.20 GHz, 128 GB RAM, NVIDIA RTX A4000 (16GB VRAM, driver 551.61), 1TB + 2TB SSD. 1 Display set to native 2560 x 1440. Software: Affinity v1 - Designer/Publisher/Photo (1.10.6.1665), Affinity v2 (universal license) - Designer/Publisher/Photo, v2 betas.
Dan C Posted December 9, 2022 Posted December 9, 2022 Hi @4dimage, Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. I've tried replicating this with your test files (thanks for providing these!) however thus far I'm not seeing this same issue - I'm able to save, close, reopen and then update the data merge file without this occurring, even with my app UI set to German. If I manually try and enter a semicolon this is not accepted and removed from the input field. Are you able to repeat this issue with your file, and if so can you please provide a screen recording for me? Also, can you please confirm, are you storing both the Affinity Document and data merge file locally, or are these in a cloud folder/external drive etc? Many thanks in advance Quote
4dimage Posted December 11, 2022 Author Posted December 11, 2022 Hi, sorry - today i found out that this error is fundamentaly caused by the screen recorder software. I used the actual Aiseesoft Screen Recorder for this. https://www.aiseesoft.de/screen-recorder/ If i open e.g. Designer v2.0.0 and even v1.10... everything seems to be ok. As soon as i start recording all numeric input fields get a trailing semicolon. This caused the input field to parse the existing string value e.g. "2;" as invalid input when trying to flip the page with the arrow keys. If i completely restart the app(s) the errors have gone - until i use aiseesoft again and start recording. From now on i will use OBS Studio for this. With OBS all input fields stay normal. Really weird... Quote Hardware: Windows 11 Pro (24H2, build 26100.3775, Windows Feature Experience Pack 1000.26100.66.0), Intel(R) Core(TM) i9-14900K, 24 Core@3.20 GHz, 128 GB RAM, NVIDIA RTX A4000 (16GB VRAM, driver 551.61), 1TB + 2TB SSD. 1 Display set to native 2560 x 1440. Software: Affinity v1 - Designer/Publisher/Photo (1.10.6.1665), Affinity v2 (universal license) - Designer/Publisher/Photo, v2 betas.
Dan C Posted December 12, 2022 Posted December 12, 2022 Many thanks for letting me know, that's certainly strange as I've not seen something similar to this previously! It's possible this screen recorder is using/interacting with Windows .NET, causing this in the Affinity app. I'll be sure to inform our team of this here such that we are aware should we see further reports of this in the future, but you may also wish to contact the developers of the screen recording software to inform them of this, as I believe this is something that will need to be changed on their end, as you've found this does not occur with other screen recorders Many thanks once again Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.