This is the code reading in the XML and loading the XUI element:
implementation_date = oid_find_children($qvarr[1], implementation_datearr,
"implementation_date_qv");
temporary_implementation_date_value =
oid_content(oid_child(implementation_datearr[1], 1));
junk = gsub("<newline/>", "|", $temporary_implementation_date_value);
# junk = gsub("", "~", $temporary_implementation_date_value);
implementation_date_value = '<textbox id="ImplementationDate"<br"/>width="275"><value>' . $temporary_implementation_date_value .
'</value></textbox>';
This is the code reading the updated (or not) XUI and inserting content back
into XML:
implementation_date = oid_find_child_attrs(oid_root($xuidoc),
implementation_datearr, "id", "ImplementationDate");
implementation_date_out_value = oid_content($implementation_datearr[1]);
junk = gsub("\\|", "<newline/>", $implementation_date_out_value);
# junk = gsub("\\~", "\\", $implementation_date_out_value);
junk = oid_select(oid_child(oid_caret(), 15),1,1);
delete_mark;
goto_oid(oid_child(oid_caret(), 15));
insert_tag value;
insert_string -sgml "$implementation_date_out_value"
I believe bug number one occurs when the XUI "engine" attempts to display
in the XUI dialog's XUI textbox. XUI!
I believe bug number two occurs when oid_content reads
$implementation_datearr[1].
Or that the same bug exhibits in each of those situations.
Uncommenting the nbsp gsub lines bypasses the problem and should be in-use
tomorrow, pending testing resources. I'll probably submit this to support
later.
On Wed, Sep 9, 2009 at 10:01 AM, Brandon Ibach <
brandon.ibach@single-sourcing.com> wrote:
> Hey, Paul...
>
> I recall dealing with these sorts of issues when working with COM/VB
> dialogs as Editor customizations (before XUI was an option). Can you
> show some of your code for getting the content from your document into
> the XUI and back?
>
> -Brandon 🙂
>
>