PainShop Pro Scripting - More on PSP X and Text

Author

More on PSP X and Text

SuzShook

2006-06-11, 4:11 am

There is an interesting addendum to all this talk about text, and it is what
PSP itself will do with a Text/TextEx command in a script, regardless of if
or when we insert a conversion factor. PSP determines the version of the
script from the 'Host Version' parameter in the ScriptProperties statement
at the beginning of the script. If this parameter says 8 or 9 or is left
blank, PSP determines the script is from a prior version of PSP. If then a
TextEx command is encountered, PSP knows the PointSize is in pixels, and
will write the text in pixels, performing the necessary internal conversion
to Points, which, as we've been discussing, is relative to the resolution of
the image. Therefore, if you have either a blank 'Host Version', or an 8 or
a 9 for that parameter, PSP does the pixel-to-point conversion for you, and
then writes the text using the number of PIXELS in the script, so all text
will look the same, regardless of the image resolution. If you ask for 26
pixels, you will get 26 pixels, regardless of the image resolution.

When the command in the script is the Text command instead of the TextEx
command, no matter what the 'Host Version' says, PSP knows this command is
from PSP 8, and it will do the pixel-to-point conversion for you. As in the
previous case, the text will be written using the number of PIXELS
specified, and all text will look the same, regardless of the image
resolution.

Things get interesting when the "Host Version" is 10. In this case, PSP
thinks the PointSize units are already in points, and will write the text
using POINTS rather than pixels, which will give a different results for
different image resolutions.

Let me illustrate with some examples. Suppose you have a script that
specifies 26 as the size for a font. If the script has a 'Host Version' of
' ', 8 or 9 (or uses the Text rather than the TextEx command), your text
will be 26 pixels, no matter what the resolution. This table illustrates
the numbers in this scenario:

Image Resolution PointSize What You See Points
100 ppi 26 26 pixels 19
200 ppi 26 26 pixels 10
300 ppi 26 26 pixels 6
60 ppc 26 26 pixels 82

Now if the same script has a 'Host Version' of 10, you will get text that is
26 POINTS in size, no matter what the image resolution, so what you see at
each image resolution will be very different:

Image Resolution PointSize What You See Points
100 ppi 26 36 pixels 26
200 ppi 26 72 pixels 26
300 ppi 26 108 pixels 26
60 ppc 26 9 pixels 26

This is why scripts running with a 'Host Version' of 10 and the TextEx
command have such differences in what you see when text is written. Hence,
the entrance of Howard's "enhanced" conversion factor. What it does, in
essence, is scale the text back to 26 pixels in all instances, so what you
see is always the same.

Nothing is easy, so here is the major problem - the case where the 'Host
Version' does NOT say 10, but the conversion factor is used anyway.
Remember, when the 'Host Version' does not say 10, PSP performs the
conversion for you. Therefore, we have here a case where PSP is going to do
the conversion for you, after you've already recalculated the PointSize
using the conversion factor, creating a sort of "double whammy". The
conversion factor code determines the correct font size based on the image
resolution. At the same time, the script thinks it has to do the conversion
for you, so it does, resulting in truly bizarre results. Carrying through
the case where the PointSize is set to 26, the 'Host Version' parameter is
blank or 8 or 9, and the conversion factor is used, you would see these
results:

Image Resolution PointSize What You See Points
100 ppi 26 24 pixels 17
200 ppi 26 12 pixels 4
300 ppi 26 8 pixels 2
60 ppc 26 105 pixels 320

The lesson to be learned here is BE CAREFUL what you code. I think there
are three rules to observe when you are writing scripts:

1. If you are using the Text command, or have the Host Version set to
blank or 8 or 9, PSP will do the conversions for you - don't include the
conversion factor code.

2. If you are using the TextEx command, and you have the Host Version set
to 10, use the conversion factor code to make the display text the same size
regardless of image resolution.

3. And finally, rule number 3, be aware that text in PSP X is always a bit
smaller than that in previous versions of PSP, for all of the above reasons.
To get a font size to use in PSP X that will give you the same results on
screen as a certain font size in PSP 8 or 9, use this formula:

Font Size in PSP X = (Font Size in PSP 8 or 9 * Your Display DPI setting)
/ 72

or use the script I set up last fall to do this for you (ss-PSPXFontSizer)

If you've read this far, and you don't have a headache, you're a truly
persistent individual! Hope this hasn't totally confused you - it's just
the facts, as I see them. You can check my numbers out, but I've run
literally 100's of tests, and this is what I've concluded. Absotively
conflusterating! Suz

P.S. The Version parameter in the GeneralSettings section of the TextEx
command seems to have no effect whatsoever on the display size of the text.
It's the 'Host Version' parameter that governs all, in my experience!
--
Suz Shook
C-Tech Volunteer

JoeB

2006-06-11, 4:11 am

"SuzShook" <suzshook@adelphia.net> wrote in news:448a0b9b_3
@cnews:

> There is an interesting addendum to all this talk about text,
and it
> is what PSP itself will do with a Text/TextEx command in a
script,
> regardless of if or when we insert a conversion factor. PSP
> determines the version of the script from the 'Host Version'
parameter
> in the ScriptProperties statement at the beginning of the
script. If
> this parameter says 8 or 9 or is left blank, PSP determines the
script
> is from a prior version of PSP. If then a TextEx command is
> encountered, PSP knows the PointSize is in pixels, and will
write the
> text in pixels, performing the necessary internal conversion to
> Points, which, as we've been discussing, is relative to the
resolution
> of the image. Therefore, if you have either a blank 'Host
Version',
> or an 8 or a 9 for that parameter, PSP does the pixel-to-point
> conversion for you, and then writes the text using the number
of
> PIXELS in the script, so all text will look the same,
regardless of
> the image resolution. If you ask for 26 pixels, you will get
26
> pixels, regardless of the image resolution.
>
> When the command in the script is the Text command instead of
the
> TextEx command, no matter what the 'Host Version' says, PSP
knows this
> command is from PSP 8, and it will do the pixel-to-point
conversion
> for you. As in the previous case, the text will be written
using the
> number of PIXELS specified, and all text will look the same,
> regardless of the image resolution.
>
> Things get interesting when the "Host Version" is 10. In this
case,
> PSP thinks the PointSize units are already in points, and will
write
> the text using POINTS rather than pixels, which will give a
different
> results for different image resolutions.
>
> Let me illustrate with some examples. Suppose you have a
script that
> specifies 26 as the size for a font. If the script has a 'Host
> Version' of ' ', 8 or 9 (or uses the Text rather than the
TextEx
> command), your text will be 26 pixels, no matter what the
resolution.
> This table illustrates the numbers in this scenario:
>
> Image Resolution PointSize What You See Points
> 100 ppi 26 26 pixels 19
> 200 ppi 26 26 pixels 10
> 300 ppi 26 26 pixels 6
> 60 ppc 26 26 pixels 82
>
> Now if the same script has a 'Host Version' of 10, you will get
text
> that is 26 POINTS in size, no matter what the image resolution,
so
> what you see at each image resolution will be very different:
>
> Image Resolution PointSize What You See Points
> 100 ppi 26 36 pixels 26
> 200 ppi 26 72 pixels 26
> 300 ppi 26 108 pixels 26
> 60 ppc 26 9 pixels 26
>
> This is why scripts running with a 'Host Version' of 10 and the
TextEx
> command have such differences in what you see when text is
written.
> Hence, the entrance of Howard's "enhanced" conversion factor.
What it
> does, in essence, is scale the text back to 26 pixels in all
> instances, so what you see is always the same.
>
> Nothing is easy, so here is the major problem - the case where
the
> 'Host Version' does NOT say 10, but the conversion factor is
used
> anyway. Remember, when the 'Host Version' does not say 10, PSP
> performs the conversion for you. Therefore, we have here a
case where
> PSP is going to do the conversion for you, after you've already
> recalculated the PointSize using the conversion factor,
creating a
> sort of "double whammy". The conversion factor code determines
the
> correct font size based on the image resolution. At the same
time,
> the script thinks it has to do the conversion for you, so it
does,
> resulting in truly bizarre results. Carrying through the case
where
> the PointSize is set to 26, the 'Host Version' parameter is
blank or 8
> or 9, and the conversion factor is used, you would see these
results:
>
> Image Resolution PointSize What You See Points
> 100 ppi 26 24 pixels 17
> 200 ppi 26 12 pixels 4
> 300 ppi 26 8 pixels 2
> 60 ppc 26 105 pixels 320
>
> The lesson to be learned here is BE CAREFUL what you code. I
think
> there are three rules to observe when you are writing scripts:
>
> 1. If you are using the Text command, or have the Host
Version set
> to
> blank or 8 or 9, PSP will do the conversions for you - don't
include
> the conversion factor code.
>
> 2. If you are using the TextEx command, and you have the Host
> Version set
> to 10, use the conversion factor code to make the display text
the
> same size regardless of image resolution.
>
> 3. And finally, rule number 3, be aware that text in PSP X is
always
> a bit
> smaller than that in previous versions of PSP, for all of the
above
> reasons. To get a font size to use in PSP X that will give you
the
> same results on screen as a certain font size in PSP 8 or 9,
use this
> formula:
>
> Font Size in PSP X = (Font Size in PSP 8 or 9 * Your Display
DPI
> setting)
> / 72
>
> or use the script I set up last fall to do this for you
> (ss-PSPXFontSizer)
>
> If you've read this far, and you don't have a headache, you're
a truly
> persistent individual! Hope this hasn't totally confused you -
it's
> just the facts, as I see them. You can check my numbers out,
but I've
> run literally 100's of tests, and this is what I've concluded.
> Absotively conflusterating! Suz
>
> P.S. The Version parameter in the GeneralSettings section of
the
> TextEx command seems to have no effect whatsoever on the
display size
> of the text. It's the 'Host Version' parameter that governs
all, in my
> experience!

Well, I actually read the whole thing without getting a headache,
but I think that's because the stuff actually has to enter the
head to produce a headache while if it goes over the head there
are no adverse effects :-)

Actually, I did get the drift for quite a bit of it, but it will
likely take time - and re-visiting, as I've saved it just in case
I would ever need it - before I can let the rest enter the head
without having ASA on hand.

But for those with the background to make complete sense of it,
I'd have to say you did yeoman's work putting this all together
and posting it. You deserve a hand, and a break from your
labours!

Regards,

JoeB

Spandex Rutabaga

2006-06-11, 4:11 am

SuzShook wrote:
>
> There is an interesting addendum to all this talk about text, and it is what
> PSP itself will do with a Text/TextEx command in a script, regardless of if
> or when we insert a conversion factor.

When you say "PSP itself" what version(s) of PSP are you talking
about?

{major snippage)

> Now if the same script has a 'Host Version' of 10, you will get text that is
> 26 POINTS in size, no matter what the image resolution,

But how does the point size you get depend on the *display*
resolution?

(major snippage}

> Nothing is easy, so here is the major problem - the case where the 'Host
> Version' does NOT say 10, but the conversion factor is used anyway.

Is it correct that there is no problem if you use the host version
to determine whether or not to use a conversion factor?

(major snippage)

> The lesson to be learned here is BE CAREFUL what you code. I think there
> are three rules to observe when you are writing scripts:
>
> 1. If you are using the Text command, or have the Host Version set to
> blank or 8 or 9, PSP will do the conversions for you - don't include the
> conversion factor code.

Which conversions? Those that depend on image resolution? Those that
depend on display resolution? Those that depend on the units? Some
two of these three? All three?

> 2. If you are using the TextEx command, and you have the Host Version set
> to 10, use the conversion factor code to make the display text the same size
> regardless of image resolution.
>
> 3. And finally, rule number 3, be aware that text in PSP X is always a bit
> smaller than that in previous versions of PSP, for all of the above reasons.

That can't be true as you wrote it because the size of text in points
depends on the image resolution and therefore can become any size in
pixels, whereas in prior versions a pixel size is always a pixel size.
There is no meaningful way to compare a point size to old pixel sizes
except by first converting it to pixels.

> To get a font size to use in PSP X that will give you the same results on
> screen as a certain font size in PSP 8 or 9, use this formula:
>
> Font Size in PSP X = (Font Size in PSP 8 or 9 * Your Display DPI setting)
> / 72
>
> or use the script I set up last fall to do this for you (ss-PSPXFontSizer)
>
> If you've read this far, and you don't have a headache, you're a truly
> persistent individual! Hope this hasn't totally confused you - it's just
> the facts, as I see them. You can check my numbers out, but I've run
> literally 100's of tests, and this is what I've concluded. Absotively
> conflusterating! Suz

I suppose by analogy with a word processor people want to specify
text sizes in points. However, to me it is a bit peculiar because
I don't expect the text to stay the same size when I resize the image
(as it would when I changed the page size in the word processor).
Instead I expect the text size to stay unchanged relative to the
image content no matter what the display resolution, zoom factor or
print size. (That's just the opposite of what happens when you
resize a watermark image in a word processor since the text size
doesn't change.) Apart from that I believe digital images have no
size other than pixels and I always want to be aware of the size in
pixels so I know whether anti-aliasing will blur my text or not. If
we add to that the fact that versions of PSP prior to X worked in
pixels for text size, it might be most profitable to reference
everything to do with text to pixel units. I'm looking for the
answer to the question "how do I get a particular pixel size of
text running a script in any version of PSP on any computer display
with any regional settings and any image resolution?"

With that in mind I have tried to make a summary matrix of what
you said. I would like you to correct it since I haven't read any
scripting documentation lately and I may have misunderstood some
of your posts.

Version Text TextEx
blank Pix Pix [#]
8 Pix Pix [#]
9 Pix Pix [#]
10 Pix Pts [*]

Version refers to host version. Text means the Text command and
TextEx means the TextEx command. Pix means the PointSize parameter in
either command is interpreted as pixels and Pts means it is interpreted
as points. It is assumed that this table is true when the scripts with
the characteristics show are run in PSP X and *also* PSP 9 and 8.

Questions:
Is the above table correct?
Is this table only for scripts with the characteristics shown and run
solely in PSP X or does the second line, for example, (also? instead?)
refer to what happens when the script is run in PSP 8?
Does PSP 8 and/or PSP 9 understand what a TextEx command is or not
(e.g. because the command is new in PSPX)?
If the answer is no then items marked [#] and [*] actually cause a
script error when the script is run in PSP 8 or 9, correct?
Is it correct that, no matter what the host version placed in a script
(including 10) a script run in PSP 8 or 9 always creates text based
on a PointSize interpreted as pixels?
Is the only situation in which points are used the one where (1)
the host version in 10 and (2) the command is TextEx and (3) the
script is run in PSPX?
If there is only one problem case why does anyone use the TextEx
command in place of Text?

The table entry marked [*] requires a conversion factor between points
and pixels. It is the only such situation. Let's assume we know a size
in pixels we want for the text and need to compute the equivalent size
in points. We need the code below.

Resolution = ImageInfo['PixelsPerUnit']
Units = ImageInfo['Unit']

# Optionally, using Python OS functions, interrogate the Registry
# to find the display resolution in dpi that is set in Windows.
# Otherwise use 96 as a default resolution.

Display = 96

if Units == 'Inches':
ConversionFactor = Display / Resolution
else:
ConversionFactor = 2.54 * Display / Resolution

PSPX_Points = ConversionFactor * DesiredPixelSize

Alternatively given a desired point size for the text in PSP X:

OldStylePixelSize = DesiredPSX_Points / ConversionFactor

Are the steps and the code correct? Is Display always in dpi no matter
what the regional settings/units in effect?

Howard Dickson

2006-06-11, 4:11 am

Folks,

Well to keep things simple, I won't be checking image resolution or
adding any conversion factor code for PSP8 & PSP9 scripts. I've usually
set any text size proportional to the current image's Width (or Height)
with a line something like this...

textsize = App.TargetDocument.Width/75

As the text is sized in Pixels in these two versions, I've always found
that text will always be sized in proportion to the image size (or as
near that matters).

As PSPX sizes text in points, I have to use the conversion factor, as
differing image resolution directly alters the point size. I still use
Width (or Height) as a text scaling function although I usually have to
initially tweak the divisor to get the text similar to say the original
PSP9 text size. Once that's done though, the text size is adjusted in
proportion to the image size and resolution... or at least it seems that
way to me.

I'll simply add the following to PSPX scripts (derived from my original
tweak and Suz's 'Units' check)...

# Get Image Resolution

ImageInfo = App.Do( Environment, 'ReturnImageInfo' )

Resolution = ImageInfo['PixelsPerUnit']
Units = ImageInfo['Unit']

if Units == 'Inches':
factor = 72 / Resolution
else:
factor = 72 / Resolution * 2.54

# ----------

Then this (or similar)...

textsize = (App.TargetDocument.Width/75) *factor

So I'll be sticking to using this code with PSPX text scripts only. I've
never had anyone complain about text size in my PSP8 or PSP9 scripts, so
'if it aint broke, don't fix it' prevails.

Rgds,
Howard
--

---oooOOOooo---

Sheilsoft
ComputerSystems

www.sheilsoft.com

---oooOOOooo---

SuzShook

2006-06-11, 4:11 am

underprocessable

Howard Dickson

2006-06-11, 4:11 am

SuzShook wrote:

>
> Now, how do we get the display resolution from the Registry?????
>

Suz,

As far as I can make out, the Windows display resolution is stored in
this key in the registry...

HKEY_CURRENT_USER\Control Panel\desktop\WindowMetrics\\AppliedDPI

Quite how we can extract that data using Python, I'm not sure. I don't
think there is a native Python command to directly interrogate the
registry without adding functions/classes to the library... but I could
be wrong! :)

Rgds,
Howard
--

---oooOOOooo---

Sheilsoft
ComputerSystems

www.sheilsoft.com

---oooOOOooo---

Spandex Rutabaga

2006-06-11, 4:11 am

Howard Dickson wrote:

> As far as I can make out, the Windows display resolution is stored in
> this key in the registry...
>
> HKEY_CURRENT_USER\Control Panel\desktop\WindowMetrics\\AppliedDPI
>
> Quite how we can extract that data using Python, I'm not sure.

This http://docs.python.org/lib/module--winreg.html may help

Howard Dickson

2006-06-11, 4:11 am

Spandex Rutabaga wrote:
> Howard Dickson wrote:
>
>
> This http://docs.python.org/lib/module--winreg.html may help

Suz (&Span &others),

The 'Holy Grail' has been found (I think)!

First you need to import the 'winreg' library by inserting this line
under the first 'from JascApp import *' line of your script...

import _winreg

Then you can retrieve the display resolution from the Windows registry
with this code...

explorer = _winreg.OpenKey(
_winreg.HKEY_CURRENT_USER,
"Control Panel\\desktop\\WindowMetrics"
)

value, type = _winreg.QueryValueEx(explorer, "AppliedDPI")

print "Display resolution is ", repr(value)

I've tried it (PSP9), and it appears to work. Let me know how it is with
your system(s).

Rgds,
Howard

--

---oooOOOooo---

Sheilsoft
ComputerSystems

www.sheilsoft.com

---oooOOOooo---

SuzShook

2006-06-11, 4:11 am

Howard Dickson wrote:
> Spandex Rutabaga wrote:
>
> Suz (&Span &others),
>
> The 'Holy Grail' has been found (I think)!
>
> First you need to import the 'winreg' library by inserting this line
> under the first 'from JascApp import *' line of your script...
>
> import _winreg
>
> Then you can retrieve the display resolution from the Windows registry
> with this code...
>
> explorer = _winreg.OpenKey(
> _winreg.HKEY_CURRENT_USER,
> "Control Panel\\desktop\\WindowMetrics"
> )
>
> value, type = _winreg.QueryValueEx(explorer, "AppliedDPI")
>
>
> print "Display resolution is ", repr(value)
>
> I've tried it (PSP9), and it appears to work. Let me know how it is
> with your system(s).
>
> Rgds,
> Howard

Eureka, Howard! You got it. I tried it in PSP 8 and PSP X, and it works
fine. However, this requires that the script run from a Trusted folder, and
I just don't think it's prudent to require that all our text-writing scripts
be placed in Trusted folders. For one thing, users will get lax about
allowing scripts into those folders if it's a regular thing. What I'd
sooner see is a user variable at the beginning of the script called Display,
or DPI, by default set to 96. Then, if a user has a display resolution, or
DPI, different from the default value, he/she can edit that single line,
entering the correct DPI value. What do you think? Suz

Spandex Rutabaga

2006-06-11, 4:11 am

SuzShook wrote:
>
> Howard Dickson wrote:
>
> Eureka, Howard! You got it. I tried it in PSP 8 and PSP X, and it works
> fine. However, this requires that the script run from a Trusted folder, and
> I just don't think it's prudent to require that all our text-writing scripts
> be placed in Trusted folders. For one thing, users will get lax about
> allowing scripts into those folders if it's a regular thing.

Trust is a matter of trusting the source. Tell them if the scripts
come from you two they are kosher and that scripts from other sources
need to be treated with circumspection. Other script authors will
have to find ways to prove themselves the way you guys already have.

> What I'd
> sooner see is a user variable at the beginning of the script called Display,
> or DPI, by default set to 96. Then, if a user has a display resolution, or
> DPI, different from the default value, he/she can edit that single line,
> entering the correct DPI value. What do you think?

I don't think people out in the real world can be trusted to
successfully edit a script when there is a requirement for white
space not to change.

You could poll every Corel group asking everyone to report their
Windows > Display Properties > Settings > Advanced > General tab >
DPI setting to see how likely any editing would be. Maybe this does
not vary frequently.

You could also type into the script the Large Size 120 DPI setting
and comment it out. Then the likely most frequent edit would be to
flip the comment delimiter from the DisplayDPI = 120 line to the
DisplayDPI = 96 line. I don't know if this would lower the chance
of editing errors or not.

> Suz

Howard Dickson

2006-06-27, 9:08 pm

Spandex Rutabaga wrote:[color=darkred]
> SuzShook wrote:
>
> Trust is a matter of trusting the source. Tell them if the scripts
> come from you two they are kosher and that scripts from other sources
> need to be treated with circumspection. Other script authors will
> have to find ways to prove themselves the way you guys already have.
>
>
> I don't think people out in the real world can be trusted to
> successfully edit a script when there is a requirement for white
> space not to change.
>
> You could poll every Corel group asking everyone to report their
> Windows > Display Properties > Settings > Advanced > General tab >
> DPI setting to see how likely any editing would be. Maybe this does
> not vary frequently.
>
> You could also type into the script the Large Size 120 DPI setting
> and comment it out. Then the likely most frequent edit would be to
> flip the comment delimiter from the DisplayDPI = 120 line to the
> DisplayDPI = 96 line. I don't know if this would lower the chance
> of editing errors or not.
>
Folks,

Actually... having sussed all this out, I'll probably still only go with
my original code for PSPX text scripts. It keeps things simple, doesn't
need to be run from the Trusted folder, and probably works for most
users, who tend to use Windows defaults. The very occasional user who
does encounter a problem can be sent this further workaround. I do get
some script queries from time to time, so it's no big deal.

I just hope some of the Corel boys & girls read these forums, and sort
this, and text script recording operation flaws in the next update...
you can but hope! :)

Rgds,
Howard
--

---oooOOOooo---

Sheilsoft
ComputerSystems

www.sheilsoft.com

---oooOOOooo---

SuzShook

2006-06-27, 9:08 pm

Howard Dickson wrote:
> Spandex Rutabaga wrote:
> Folks,
>
> Actually... having sussed all this out, I'll probably still only go
> with my original code for PSPX text scripts. It keeps things simple,
> doesn't need to be run from the Trusted folder, and probably works
> for most users, who tend to use Windows defaults. The very occasional
> user who does encounter a problem can be sent this further
> workaround. I do get some script queries from time to time, so it's
> no big deal.
> I just hope some of the Corel boys & girls read these forums, and sort
> this, and text script recording operation flaws in the next update...
> you can but hope! :)
>
> Rgds,
> Howard

I tend to agree with you, Howard. I think I will include the whole section
of code that we developed over the past few days in the Tips doc, with
Display set to 96:

Display = 96
Prop = ScriptProperties()
if Prop['Host Version'][:2] == '10':
Version = App.Do(Environment, 'GetVersionInfo',)
if Version['MajorVersion'] == 10:
ImageInfo = App.Do(Environment, 'ReturnImageInfo')
Resolution = ImageInfo['PixelsPerUnit']
Units = ImageInfo['Unit']
if Units == 'Inches':
ConversionFactor = Display / Resolution
else:
ConversionFactor = Display / Resolution * 2.54
PointSize = PointSize * ConversionFactor

This will resolve text size problems from image resolution to image
resolution, including images created with ppc instead of ppi. It will only
effectively "do its thing" when the script's Host Version says 10 AND the
version of PSP running is also 10. Finally, it makes that last little
conversion for display resolution. I'd be willing to bet that the majority
of users use the default DPI setting - for those who don't, well, text is
already "off" for those users - will this make if more "off"? I don't think
the edit is so overwhelming - just change the 96 on line such and such to
120 . . . or whatever custom setting is being used. Fred - are you going to
chime in here???? Thanks for all the hard work, especially finding out how
to interrogate the Registry, Howard, and all your challenges and questions,
Spandex. Together, I think we've hammered it out! And BTW, I intend to let
Corel know about this.....! Suz

Fred Hiltz

2006-06-27, 9:08 pm

SuzShook wrote:
[snip]
> I tend to agree with you, Howard. I think I will include
> the whole section of code that we developed over the past
> few days in the Tips doc...
>
> Fred - are you going to chime in here???? Thanks for all
> the hard work, especially finding out how to interrogate
> the Registry, Howard, and all your challenges and
> questions, Spandex. Together, I think we've hammered it
> out! And BTW, I intend to let Corel know about this.....!

Hi everyone. I have been reading with high interest and want to add
my thanks to you all for doing Corel's job. I offered to write a
draft, but it looks like you already have it. Please let me know,
Suz, if you spot something I can do here.

The rest of life intrudes for a while as our family gets ready to
move. Just one town away, but the chaos seems no less for it. I'll
be in and out until mid-July.
--
Fred Hiltz, fhiltz at yahoo dot com

Howard Dickson

2006-06-27, 9:08 pm

Fred Hiltz wrote:
> SuzShook wrote:
> [snip]
>
> Hi everyone. I have been reading with high interest and want to add
> my thanks to you all for doing Corel's job. I offered to write a
> draft, but it looks like you already have it. Please let me know,
> Suz, if you spot something I can do here.
>
> The rest of life intrudes for a while as our family gets ready to
> move. Just one town away, but the chaos seems no less for it. I'll
> be in and out until mid-July.

Fred,

If you are in conversation with the Corel crowd, it may be worth
mentioning (if it hasn't been already) about the introduction in PSPX of
the Pixels/Points 'Units' option on the Text tool menubar, and how this
selection isn't captured when recording a script. I feel a new parameter
has to be added to the Text section of a script, in order to correctly
capture what option was in place at time of script recording, and more
importantly, set the correct option when the script is run.

I did report this a while back, but it might be worthwhile mentioning
again in the light of recent Text issues.

Rgds,
Howard

--

---oooOOOooo---

Sheilsoft
ComputerSystems

www.sheilsoft.com

---oooOOOooo---

Vern Stump

2006-06-27, 9:08 pm

AuntySpam

2006-06-27, 9:08 pm

My thanks also.

--

AuntySpam (a.k.a. Norma), C-tech Volunteer
http://www.geocities.com/brewnetty/home.html

"Vern Stump" <VictorDog@email.suppressed> wrote in message
news:448c1ec4$1_1@cnews...
> Fred Hiltz wrote:
>
> Fred and everyone:
> What a great group, people from everywhere who work together to resolve a
> problem. Every day for me, this is one of the greatest pleasures in life
> to see
> people work together, a very rewarding feeling.
> Thanks to all again,
> Vern
>
>