Add text to memo field problem

[RevMK]

Hello all,

I'm trying to use the 'add text to memo field' script. I have created a variable to hold the text I wish to add on to the existing text.

So, I set the variable manually, click my button and the text is added below the existing text, as expected. Great!

Next I add an xdiag to prompt for the text for the variable. I run the window, click the button, enter the text and click OK.

With this set-up the text replaces the contents of the field instead of being added to the end and I can not see why.

Has anyone else seen this behaviour, or is anyone able to reproduce it?

Thanks in advance.
Rev

[Tom Cone Jr]

Re: Add text to memo field problem

No code shown.

Alpha is most likely doing what you told it to do. What that may be is impossible to tell from what you've furnished so far.

Edits:

Sorry to be so sour.

A complete answer to your question would be: Nope.

But that's not very helpful is it?

A better question would have been:

a) here's the script I run to add variable text to an existing memo
b) here's the code I use to get the input text from the user by way of an xdialog
c) here's what happens next (code supplied)

why is the variable text entered through the xdialog overwriting all the memo text?

See the diff?

[RevMK]

Re: Add text to memo field problem

Hi,

Sorry as the steps were so short I thought I'd be easier just to describe the problem, rather than list the code. As it is an expressed action script I assumed it would be in reasonably popular use in a similar fashion to that which I described.

Xdiag box

DIM SHARED var_notes_add as C
DIM SHARED varC_result_add_notes as C
ok_button_label = "&Save"
cancel_button_label = "&Cancel"
varC_result_add_notes = ui_dlg_box("Add note",<<%dlg%
{region}
Note:| [%mw%.90,20var_notes_add];
{endregion};
{line=1,0};
{region}
<*15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
{endregion};
%dlg%)

Add text to memo field code

Dim TextToInsert as c
Dim InsertPos as n 
TextToInsert = a5_eval_expression("=Var->var_notes_add",local_variables())
TextToInsert = crlf()+TextToInsert 
InsertPos = -1

Dim TempObj as p
dim readonly_flag as l	
'Get a pointer to the Object on the Form/Browse that has the memo field.
TempObj = obj(parentform.name(16)+":"+"Notes")
'Check if the RTF memo is readonly
readonly_flag = TempObj.field.readonly
if readonly_flag = .t. then 
	ui_msg_box("Error","Cannot insert text into Memo field '"+"Notes"+"' because it is read-only",UI_STOP_SYMBOL)
	end 
else
	Dim MemoText  as c 
	MemoText = TempObj.text
	If InsertPos = 1 then 
		MemoText = TextToInsert + MemoText 
	Else if InsertPos = -1 then 
		MemoText = MemoText + TextToInsert
	Else
		MemoText = substr(MemoText,1,InsertPos - 1 ) + TextToInsert + substr(MemoText,InsertPos)
	End If 	
	
	'Now set the Memo field's text property to the next text..
	TempObj.text = MemoText
	
	'Now activate the memo
	tempobj.activate()
	'...and set the insertion point in the memo field after the inserted text
	if InsertPos = -1 then 'inserting at end of field
		tempobj.topparent.cursor_set(9999999)
	else
		tempobj.topparent.cursor_set(InsertPos + len(TextToInsert))
	end if 
end if

Followed by a save command.

I wondered if the focus had shifted, but even including a step before the insert command does not help.

Thanks

[Al Buchholz]

Re: Add text to memo field problem

InsertPos = -1

if InsertPos = -1 then 'inserting at end of field
[/CODE]

Is this code executing?

[RevMK]

Re: Add text to memo field problem

Hi Al,

Yes, watching the code in the debugger shows the value of -1 is passed as expected and follows the code path through this.

Stepping through suggests that MemoText = TempObj.text is failing to pick up a value as it returns blank.

Hmm.

[Tom Cone Jr]

Re: Add text to memo field problem

There's a big difference between "a memo field" and a "RTF memo field". Are you working with RTF data?

[RevMK]

Re: Add text to memo field problem

Hi all,

Thanks for your help. I've fixed the problem.

Answer:
It seems I had a command to shift the memo field out of readonly after the xdiag request script. Placing it before the xdiag request seems to have cured my woes.

Thanks again.
Rev