Page 1 of 1

Quark 10 Measurement Coercion

Posted: 23 Oct 2014, 17:35
by jeff.walters

It has been a long time since I have been on this forum. I realize that this issue is an oldie but a goodie, but I thought I would ask about it here in case someone has any other tips.

I am having to add coercions in for all measurements. I was able to save my apps as 32-bit only in Mac OS 10.6/Quark 6.5 and not have to do this coercion step. But we have made the jump to QuarkXPress 10.1.1 on Mac OS 10.9.4. I am now having to go back and add in coercions to all measurements.

My questions: 1) Does QuarkXPress 10.2.x do anything to fix this? I assume not. 2) Is there anything else I can do to not have to add coercions in everywhere?

An example:

For any measurement, I am finding that I have to coerce the data type to be able to use the value.

So for this:

tell application "QuarkXPress"
tell front document
set pageWidth to page width
end tell
end tell

I get a result of:

«data FXHM00006402»

Adding "as real" after page width causes an error.

So I have to add the coerce command as such:

set pageWidth to page width
set pageWidth to coerce pageWidth to real

Also, is there a one line way of doing that?



Re: Quark 10 Measurement Coercion

Posted: 24 Oct 2014, 02:06
by Jean-Marie Schwartz
Hi! I'm afraid not! This is a real pain actually! So hard to read results as easily as we used to be able to in the past. :evil:

Re: Quark 10 Measurement Coercion

Posted: 24 Oct 2014, 02:46
by pjanssen
Reported the issue several times, but it seems it can't be fixed (or there are other priorities…).

Re: Quark 10 Measurement Coercion

Posted: 24 Oct 2014, 03:47
by Jean-Marie Schwartz
I read this morning a thread on MacScripter where Shane Stanley says sth about AS working with objects and not data (see here). So I guess that's the point. But I couldn't say who's responsible for it. What I know is that we used to read those datas easily a while back and that AFAIC upgrading to Mountain Lion ruined that.

Re: Quark 10 Measurement Coercion

Posted: 03 Nov 2014, 19:03
by jeff.walters
Thanks! I thought that was what I was going to find, but thought I would double check. I don't have much hope that anything in Quark that is currently "broken" will ever be fixed.