Date: Mon, 30 Oct 2006 05:25:02 -0400
From: WINSERVER SUPPORT
To: all
Subject: AUP 451.9j GAMMA is available - FINAL
Newsgroups: winserver.public.gamma.testing
Message-ID: <1162204369.40.0@winserver.com>
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 82

The final GAMMA is now available (of course, all pending any last minute issue).

This is a summary of the changes since the last GAMMA a few weeks ago:

- The blue background for the wcJava Chat was removed.

You have to clear your browser cache and also maybe the installed JAVA
engine cache too. But try it first without clearing the cache to see if the
new wcjava.jar file is picked up by the java engine.

- The Wildcat! Native Mail System now supports LONGER FILE NAMES for
Wildcat! message attachments.

By LONGER, we mean it was changed from the short 15 characters MAX to 79 characters max. We could not go the full 260 LFN without changing
structures. This new LFN size should be sufficient for 99% of the practical
and realistic needs.

It is backward compatible. Meaning, all older applications, WCX and SDK applications, will works like it always did. It will only know about the
old SFN size. Only the new Wildcat! Mail System and 3rd party WCX/SDK applications that are recompiled (no change needed) will be able to see the LFN.

DETAILS FOR DEVELOPERS ONLY:

If you have WCX or SDK applications that create mail with possible
attachments, technically, you don't have to do a thing. The SFN attachment name is still supported.

But of you recompile your code, then the attachment field becomes the longer field size. So you can use this to set the real file name and not the short file name as required today.

The only change, if any, for 3rd party Applications, is that they don't need
to use the SFN when setting the TMsgHeader.Attachment field.

In fact, to make it even easier for 3rd party developers, there is a new SDK API function:

Function WcSetMessageAttachment
(
msg as TMsgHeader,
byval FileName as string,
copyto as Boolean
) as boolean

Before, the sequence for a proper attachment was:

step 1: set the TMsgHeader structure

dim msg as tmsgheader
clear msg
msg.to = ... set the to info
msg.from = ... set the from info
msg.subject = ... set the subject
msg.conference = ... set the conference number

set 2: set the attachment using SFN and copy file

msg.attachment = ... set the SFN file name
Copy the attachment to the WC:\TEMP

set 3: finally add the message

AddMessage(msg, bodytext)


Now, all you need to do in step 2 is:

set 2: set the attachment using SFN and copy file

WcSetMessageAttachment(msg,"filename",TRUE)

This will probably set the fields, check to make sure its no longer than 80 characters, and also COPY the file to the WC:\TEMP making it ready for the AddMessage() post to see the attachment.

---
HLS
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)