Jump to content
You must now use your email address to sign in [click for more info] ×

Publisher: Text inset adjustments by .01" per arrow press. Missing from V.2? Why?


Recommended Posts

44 minutes ago, Mike W077 said:

Sure, but it adds steps, including changing from mouse to keyboard, when simple mouse clicks used to work. 

Agree completely with Mike W077--it's very frustrating and time consuming to have to manually enter each numeric value when doing fine adjustments to fit text. For example, if you enter an inset value (eg, 0.005") and you require more/less inset, clicking the up/down arrows defaults to 1.0" and increments of 1.0" . This requires you to then stop and manually type in your new inset value (eg. 0.006").

In V1, simply clicking on the up/down inset setting allowed you to quickly see your changes in small increments, and by toggling back and forth, you could decide which inset setting was best. Doing fine adjustments in V2 is very cumbersome and time consuming!

I'm not sure who actually would use insets in 1.0" increments (useless except for enormous layouts).

I'm hopeful that the next release will fix this problem. Is there anyway to know when the next release might launch?

 

Link to comment
Share on other sites

11 hours ago, JEP said:

I'm not sure who actually would use insets in 1.0" increments (useless except for enormous layouts).

I'm hopeful that the next release will fix this problem. Is there anyway to know when the next release might launch?

Well said. Who needs 1.0" adjustments? Then there is the 0,0,0,100 color issue exporting to PDF, which often converts to a rich black. Argh! This has caused me no end of grief with my printer. Affinity wants us to use these programs for production work, right? Then, they have got to give attention to these kings of details. 

Link to comment
Share on other sites

12 hours ago, Mike W077 said:

Sure, but it adds steps, including changing from mouse to keyboard, when simple mouse clicks used to work. 

I agree that it takes more steps & is far from ideal, but I just wanted to make sure manually entering small values was working for you & not an indication of some additional bug in the Mac version I was not seeing.

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

15 minutes ago, R C-R said:

I agree that it takes more steps & is far from ideal, but I just wanted to make sure manually entering small values was working for you & not an indication of some additional bug in the Mac version I was not seeing.

Thank you for checking back on this. Do you have an idea if or when we could expect a fix for this? Thanks. 

Link to comment
Share on other sites

18 minutes ago, Mike W077 said:

Do you have an idea if or when we could expect a fix for this?

Since Serif does not usually comment on when (or if) such things will be fixed, the only way is to wait for an update (or a new beta) & see if it is fixed or not.

It's also possible this will end up being part of an added feature like a user-settable increment similar to the nudge distances tools preferences, which might take longer to implement than a simple change in the default.

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

1 hour ago, JEP said:

Yes, entering a small value works, but is veery time consuming.

I'm attaching screen recording that shows this.

The inset settings & defaults worked perfectly in V1--can't they be restored for V2?

Do you have an idea of if or when we could expect a fix for this? 

Awesome! Good job. Thank you. Come on Serif! Get this fixed. Those of us using Publisher for production need this fixed ASAP.

Link to comment
Share on other sites

8 minutes ago, Mike W077 said:

Those of us using Publisher for production need this fixed ASAP.

While I realize it is far from optimal, but as a workaround in the mean time you might consider setting the document units to points, pixels, or possibly picas or mm so that incrementing by 1 document unit is much more useful than for inches (or feet, yards, meters or any other large document unit).

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

Sorry R C-R.

This is NOT a viable option--everything else is in inches--doing constant conversions is even more cumbersome and time-consuming--it's impractical for us attempting to do layouts/publications with real-time deadlines.

As Mike W077 said, "Those of us using Publisher for production need this fixed ASAP."

Link to comment
Share on other sites

7 minutes ago, JEP said:

This is NOT a viable option...

Like I said, I realize it is far from an optimal solution but if you are a deadline it is probably a lot quicker to change the document units (which you can do quickly on the ruler origin) to change inset values than entering them from the keyboard.

After all, what other choice do you have if you are working in V2 of APub on a Mac? You obviously can't just wait until the fix is implemented, right?

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

21 hours ago, R C-R said:

After all, what other choice do you have if you are working in V2 of APub on a Mac? You obviously can't just wait until the fix is implemented, right?

After a while, all the little "gotchas" get to be too much. The 0,0,0,100 random conversion to rich black in PDFs (making problems with registration. This may be fixed in 2.X, but don't know for sure), the lack of span columns for paragraphs, and now this. Just little things that are really big things in a production work flow. There is another option, going back to InDesign, at least until these issues are resolved. Not what I want, but it is an option.

Link to comment
Share on other sites

1 minute ago, Mike W077 said:

There is another option, going back to InDesign, at least until these issues are resolved. Not what I want, but it is an option.

Yes, I know that is another option, which is why I said if you are working in V2 of APub, you do not have any other viable options.

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

  • 1 month later...
4 hours ago, JEP said:

This STILL is not fixed on the newest Beta version (2.1.0.1736)!

Are we ever going to get a fix for this?

But, at least it’s working in Affinity Publisher for iPad in the latest 1736-update of the 2.1 beta…

I can use 0.01 in the insets of an textframe…

Happy amateur that playing around with the Affinity Suite - really love typograhics, photographing, colors & forms, AND, Synthesizers!

Macbook Pro 16” M1 2021, iPad Pro 12.9” M1 2021, iPad Pro 10.5” A10X 2017, iMac 27” 5K/i7 late 2015…

Link to comment
Share on other sites

5 hours ago, JEP said:

This STILL is not fixed on the newest Beta version (2.1.0.1736)!

Are we ever going to get a fix for this?

Works for me as expected. Both with version 2.04 and 2.1.0.1736.
To scale up or down by one thousandth, the CTRL key must be pressed. 

AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB  | 32 GB DDR4 3200MHz | Windows 11 Pro 23H2 (22631.3296)
AMD A10-9600P | dGPU R7 M340 (2 GB)  | 8 GB DDR4 2133 MHz | Windows 10 Home 22H2 (1945.3803) 

Affinity Suite V 2.4 & Beta 2.(latest)
Better translations with: https://www.deepl.com/translator  
Interested in a robust (selfhosted) PDF Solution? Have a look at Stirling PDF

Life is too short to have meaningless discussions!

Link to comment
Share on other sites

2 hours ago, JEP said:

Are you on a PC or Mac?

Not working my Mac running Monterey (12.6.3)

I'm on PC.

AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB  | 32 GB DDR4 3200MHz | Windows 11 Pro 23H2 (22631.3296)
AMD A10-9600P | dGPU R7 M340 (2 GB)  | 8 GB DDR4 2133 MHz | Windows 10 Home 22H2 (1945.3803) 

Affinity Suite V 2.4 & Beta 2.(latest)
Better translations with: https://www.deepl.com/translator  
Interested in a robust (selfhosted) PDF Solution? Have a look at Stirling PDF

Life is too short to have meaningless discussions!

Link to comment
Share on other sites

3 hours ago, JEP said:

Are you on a PC or Mac?

The sig @Komatös includes indicates it is a Windows 11 Pro computer....

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

11 hours ago, JEP said:

This STILL is not fixed on the newest Beta version (2.1.0.1736)!

Are we ever going to get a fix for this?

Still not fixed. I've given up. Using Indesign. They are clearly not aiming this for professional use. Wake me when they fix this and the PDF export nightmare. 

Link to comment
Share on other sites

20 hours ago, JEP said:

Are you on a PC or Mac?

Not working my Mac running Monterey (12.6.3)

On my Macbook Pro 16” (M2 CPU) it’s working as expected…

Latest Affinity Publisher beta 2.10 build 1736 - I can use 0.01 inch in the textframe settings for insets…

MacOS Ventura latest beta version…

Happy amateur that playing around with the Affinity Suite - really love typograhics, photographing, colors & forms, AND, Synthesizers!

Macbook Pro 16” M1 2021, iPad Pro 12.9” M1 2021, iPad Pro 10.5” A10X 2017, iMac 27” 5K/i7 late 2015…

Link to comment
Share on other sites

10 minutes ago, AffinityMakesMeSmile said:

On my Macbook Pro 16” (M2 CPU) it’s working as expected…

Latest Affinity Publisher beta 2.10 build 1736 - I can use 0.01 inch in the textframe settings for insets…

MacOS Ventura latest beta version…

The main question is, can you use the up/down buttons to increase/decrease the values? This is what is under discussion.

image.png.d32dd1fc132ce05dd4b858c3d7012e1d.png

AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB  | 32 GB DDR4 3200MHz | Windows 11 Pro 23H2 (22631.3296)
AMD A10-9600P | dGPU R7 M340 (2 GB)  | 8 GB DDR4 2133 MHz | Windows 10 Home 22H2 (1945.3803) 

Affinity Suite V 2.4 & Beta 2.(latest)
Better translations with: https://www.deepl.com/translator  
Interested in a robust (selfhosted) PDF Solution? Have a look at Stirling PDF

Life is too short to have meaningless discussions!

Link to comment
Share on other sites

1 hour ago, Komatös said:

The main question is, can you use the up/down buttons to increase/decrease the values? This is what is under discussion.

image.png.d32dd1fc132ce05dd4b858c3d7012e1d.png

No, just by using the keyboard…

I thought it was about that it was impossible to use two decimals in the input field in the inset…

My apologies…

Happy amateur that playing around with the Affinity Suite - really love typograhics, photographing, colors & forms, AND, Synthesizers!

Macbook Pro 16” M1 2021, iPad Pro 12.9” M1 2021, iPad Pro 10.5” A10X 2017, iMac 27” 5K/i7 late 2015…

Link to comment
Share on other sites

3 hours ago, AffinityMakesMeSmile said:

No, just by using the keyboard…

I thought it was about that it was impossible to use two decimals in the input field in the inset…

My apologies…

No problem! Sometimes the obvious is before our eyes, but we don't see it.

What I would like to know now is if the problem occurs with all macOS versions or only with the latest one (Ventura?)?

AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB  | 32 GB DDR4 3200MHz | Windows 11 Pro 23H2 (22631.3296)
AMD A10-9600P | dGPU R7 M340 (2 GB)  | 8 GB DDR4 2133 MHz | Windows 10 Home 22H2 (1945.3803) 

Affinity Suite V 2.4 & Beta 2.(latest)
Better translations with: https://www.deepl.com/translator  
Interested in a robust (selfhosted) PDF Solution? Have a look at Stirling PDF

Life is too short to have meaningless discussions!

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.