Printing anomaly after creating simple applet

[jgolden]

I was wondering if I could get some feedback to see whether this is a problem with my applet, or if I might have come across a possible bug…

Without going into details as to why, my client needs to be able to set (and occasionally change) the default font GW uses when composing, replying to, forwarding, or resending a message.

I have to admit, this is the first time I’ve tried coding a Formativ applet.

The code I drafted is as follows:

dim cFontFace
dim cFontSize

Sub Main(Client, GWEvent)
cFontFace = “Arial”
cFontSize = 12
Call GroupWise.FocusSet(10,””)
Call GroupWise.FontSet(cFontFace, cFontSize, fnwREGULAR, False, False, 0)
if GWEvent <> “GW#C#REPLY” Then
Call GroupWise.FocusSet(0,””)
end if
End Sub

nd it seems to work. Except when I try printing a message created with this applet in place. A simple “Hello World” email, which was confirmed drafted in Arial 12-pt (as dictated by the applet) takes more than 25 pages to print (i.e. it’s as if the font is now 1200-pt). Saving the email to a txt file, and printing this text file prints normally.

Can anyone see what might have been done wrong with the above applet and / or suggest what might be happening wrt the printing of emails created with this applet in place?

TIA

Jeff

Topic

[Support 3]

We are unable to re-produce the behaviour in GroupWise client 7.0.3 (8/03/2008). It print one page from the draft message and received message where the Font modified by the code above. The font and size appear to be fine in print out.

However, the code above change the Font to “Arial” but the font size change to “8”, default font size is “10” and font “Tahoma”. Does your font size change when you run the code? May be a bug in the GroupWise “Fontset()” token.

Which version of the GroupWise client you are running (see Help and About GroupWise)? You may need to upgrade the client to latest release.

Regards,
Advansys support

[jgolden]

quote:

---

We are unable to re-produce the behaviour in GroupWise client 7.0.3 (8/03/2008). It print one page from the draft message and received message where the Font modified by the code above. The font and size appear to be fine in print out.

---

Well, that’s a good thing to know. At least it now throws suspicion into their environment as to why messages created with this applet are not printing properly.

1 thing I forgot to mention. Not sure how much it affects the tests. The client has locked the client to only allow text-mode; HTML-encoded messages are disallowed.

quote:

---

However, the code above change the Font to “Arial” but the font size change to “8”, default font size is “10” and font “Tahoma”. Does your font size change when you run the code? May be a bug in the GroupWise “Fontset()” token.

---

Yes, additional tests had the font style and size change to whatever was set, unless there was a typo in the style. in that case, it reverted to Tahoma 8-pt, which is what the client has set as their default font for their Windows XP Message Box font.

quote:

---

Which version of the GroupWise client you are running (see Help and About GroupWise)? You may need to upgrade the client to latest release.

---

The client is still at 6.5.7 (2007-09-13). They’re still a few months away from upgrading their environment to GW7. However, they are trying to get the formativ runtime seet up in their development environment, where they are testing their GW7 upgrade strategy. Hopefully I’ll be able to test it there.

Thanks again for the quick response.

jeff

[Support 3]

We don’t think the GroupWise client text-mode will affect the result. The issue could be environmental, you may need to try to re-produce in another machine.

We also think there could be a bug in the “FontSet()” token where it does not change the font size in GroupWise 7. Please let us know if the token works in your GroupWise 7 environment.

Regards,
Advansys Support

[jgolden]

Well, built a clean, new GW703 environment in the lab; DL’ed / installed formativ runtime so I can test the applet. (Confirmed GW client 7.0.3 – 08/03/2008). Confirmed the font is set when executed on new messages. Simple ‘hello world’ test email was queued to be 11 pages when created with the applet. I’ve posted something to the GW community to see what anomalies / issues might be known with the fontset() function. As it stands, I’m at a loss… (Was going to post a screenshot here showing all this, but couldn’t see a link to do so).

[Support 3]

It seems starange issue as we can not re-produce in house. FontSet() Token API should not interfere with print behaviour.

May be you can try to re-produce the bahaviour manually without the Applet by creating a message, change the font and size then type the “Hello World” and finally print. May be you can try to re-produce it in another machine with different printer.

Let us know if you have any positive suggestions from the GroupWise community.

Regards,
Advansys Support

[jgolden]

I’m still waiting for a response from the GroupWise support forums, but I’ve tried your other suggestions. In 3 different trees (all running eDir 8739), using 3 different desktops in each environment (Win2kSP4, WinXP-SP1, WinXP-SP2), all with GW703 (1 was upgraded from 6.5.7 directly to 703, 1 from 700 to 703 and 1 703 natively) and to 3 different printers (1 in each of the 3 environments), I had the same results. If I manually create the message and change the font in the same order that the applet would have performed the tasks, the results are as expected – 1 page. But with the applet, it’s around 12 pages.

While waiting for the GW support team to respond to my query, I’ll try DLing the free DebugView utility from SysInternals, and see if I can find anything that way.

I’ll provide another update when I get through the debugs.

jeff

[Support 3]

On a separate note, found the following article which discussed about the Font Sizes and Printing Plain Text in GroupWise:
http://www.novell.com/communities/node/4538/font-sizes-and-printing-plain-text

It appear you can also change the default GroupWise font size in Registry. Not sure whether the end result will be the same, you can try to modify your code to change the registry font size value. The Registry String value usually present if you already setup the font size in GroupWise (Tools – Options – Environment). One side effect to this approach is your GroupWise default font name and size will be the value in the registry.

You do not need to run your code each time on composing message, you can run it when GroupWise startup. Please take extra care when changing the registry value. See the Formativ Language Guide – utilities.Registry() method which provide access to the Windows registry. Let us know if you need some registry sample code.

Regards,
Advansys Support

[Author]

Replies