realbasic-nug
[Top] [All Lists]

Re: Storing the contents of a styled editfield...

To: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Subject: Re: Storing the contents of a styled editfield...
From: Russ Tyndall <fitzbew@nc.rr.com>
Date: Tue, 30 Jun 2009 14:43:36 -0400
Authentication-results: mx.google.com; spf=neutral (google.com: 74.124.194.228 is neither permitted nor denied by best guess record for domain of realbasic-nug-bounces@lists.realsoftware.com) smtp.mail=realbasic-nug-bounces@lists.realsoftware.com
Delivered-to: listarchive@realsoftware.com
In-reply-to: <61E0597D-4987-4B6F-99DA-5CCEF0567800@xochi.com>
References: <839A347D-2C6B-474A-86E3-53B7D4F9DE96@gmail.com> <3F065AC5-0800-4C72-AE51-26205201E422@tolisgroup.com> <61E0597D-4987-4B6F-99DA-5CCEF0567800@xochi.com>
Reply-to: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Sender: realbasic-nug-bounces@lists.realsoftware.com

On Jun 30, 2009, at 2:06 PM, Michael Diehr wrote:

Correct -- EditField.StyledText.RTFData is an string which can be stored in a text file, and this is enough data to restore an edit field to its prior state.

As long as the RTF data originates in REALbasic, I think it works ok. Problems may arise if you try to get RTF from another source, as the RTF parser in RB is limited.


I haven't done any testing with 2009r2 or 2009r2.1, but I had enormous problems while trying to get this to work on Linux. At the time it looked like RB was adding spurious characters into the string when creating StyledText.RTFData on Linux that was hosing up the display when the string was pulled back out.

But everything worked great on Windows and OS X.

So if you plan to deploy to Linux, test thoroughly.

-----------------
Russ Tyndall
Wake Forest, NC




_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>