MikeW Posted October 20, 2023 Posted October 20, 2023 7 minutes ago, Mr. Doodlezz said: I was focusing on an option within Affinity Publisher since we're in the thread (regardless of all previous spreadsheet comments) for custom date formatting in Affinity, aren't we? 🤨 The thread changed from being able to format dates in APub to custom formatting in Excel not being transferred into APub during a data merge. But the answer is the same--there is no option that I understand for calculated future dates (no spreadsheet-like calculations at all). Without creating a sample, I don't know if an Excel sheet using such calculations would come in intact, either. Quote
Mr. Doodlezz Posted October 20, 2023 Posted October 20, 2023 52 minutes ago, MikeW said: The thread changed from being able to format dates in APub to custom formatting in Excel not being transferred into APub during a data merge. But the answer is the same--there is no option that I understand for calculated future dates (no spreadsheet-like calculations at all). Without creating a sample, I don't know if an Excel sheet using such calculations would come in intact, either. Sure, a lot of people have taken the discussion in a different direction. Maybe those folks just aren't the right ones to answer my question since I'm not bringing up spreadsheet tasks or issues with data merging. I'm asking about the feature that this thread originally focused on, and I believe it still does, according to the first page and the thread's title. It's still custom date formatting for fields started by Ash to highlight and help with this exact feature, isn't it? (Just wondering if it’s actually me being the one off-track with my question here.) Anyway, you might be right, and there seems to be no way to achieve what I want, at least none that I've found, which is similar to what =TODAY() + 30 does in Excel – too bad! Quote
walt.farrell Posted October 20, 2023 Posted October 20, 2023 4 minutes ago, Mr. Doodlezz said: I'm asking about the feature that this thread originally focused on, and I believe it still does, according to the first page and the thread's title. It's still custom date formatting for fields started by Ash to highlight and help with this exact feature, isn't it? (Just wondering if it’s actually me being the one off-track with my question here.) The topic is about being able to format the actual date/time values in different ways, not about being able to calculate using dates. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.4
amcd Posted January 8, 2024 Posted January 8, 2024 The Time/Date fields in latest version of Publisher 2.3.1 - DEFAULTS to UK GMT. Unfortunately with your new standard, I have lost my ability to easily format date/time fields that I had been using for years. I am in Brisbane, Australia which is Australian Eastern Stand Time (AEST) i.e. UTC/GMT +10 year round . Sydney is currently Australian Eastern Daylight Time (AEDT=AEST+1) i.e. UTC/GMT +11 during summer. I tried using Ash's table (26 June 2023) for some hours with no luck. Please can you direct me to a tutorial or easy instructions that shows me how to edit the time/date fields. I would be very grateful if you would send me specific examples of Field Formatting for Brisbane and Sydney. Many thanks amcd Quote
MikeTO Posted January 9, 2024 Posted January 9, 2024 16 minutes ago, amcd said: The Time/Date fields in latest version of Publisher 2.3.1 - DEFAULTS to UK GMT. Unfortunately with your new standard, I have lost my ability to easily format date/time fields that I had been using for years. I am in Brisbane, Australia which is Australian Eastern Stand Time (AEST) i.e. UTC/GMT +10 year round . Sydney is currently Australian Eastern Daylight Time (AEDT=AEST+1) i.e. UTC/GMT +11 during summer. I tried using Ash's table (26 June 2023) for some hours with no luck. Please can you direct me to a tutorial or easy instructions that shows me how to edit the time/date fields. I would be very grateful if you would send me specific examples of Field Formatting for Brisbane and Sydney. Many thanks amcd Hi, are you using macOS Sonoma? There's a known issue with Sonoma and time zones. Serif has it on their list but it may be something Apple has to fix. Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
amcd Posted January 15, 2024 Posted January 15, 2024 Yes I am using macOS Sonoma. I am not convinced this is an Apple issue. I no longer have Ventura on my Mac. I will try on Monterey. Quote
amcd Posted January 15, 2024 Posted January 15, 2024 Apart from this time/date issue. I am also experience quite a lot of instability with latest Publisher 2.3.1 app on Sonoma 14.2.1. I can only clear various issues by restarting. Publisher. This is costing me a lot of time. Please, where can I can I download a previous .dmg of Publisher 2 for the time beings since the problems have only hit me with Publisher 2.3.1 Many thanks amcd Quote
Staff Affinity Info Bot Posted October 22, 2024 Staff Posted October 22, 2024 The issue "Update button for 'Current Date & Time' field fails if text frame is placed on a master page" (REF: AF-4201) has been fixed by the developers in the latest beta build (2.6.0.2805). The fix is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us. Quote
Staff Affinity Info Bot Posted March 10 Staff Posted March 10 The issue "Time zone offset is not detected on macOS Sonoma, causing Document Statistics and exporting Page Information to be incorrect" (REF: AF-681) has been fixed by the developers in the latest beta build (2.6.2.3187). The fix is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us. 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.