Number: 1244

Date: 30-May-84 15':13':22

Submitter: vanMelle

Source: Burton

Subject: Illegal arg when delivering plain text of a message containing imageobj''s

Assigned To: 

Attn: release

Status: Fixed


Problem Type: Bug

Impact: Moderate



Priority: Hopefully

System: Text

Subsystem: Lafite



Lisp Version: 14-May-84 20':07':29

Source Files: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Disposition: '
["Sybalsky" "12-Sep-84 13':57':29" Attn': Status':(Open->Fixed)]

Description: '
Date': 16 May 84 10':48 PDT'
Subject': Lafite': Illegal arg {imageobj} under gv.addtoitem'
cc':, Sannella'
Lafite System Date':  8-Apr-84 17':20':45'
Lisp System Date': 14-May-84 20':07':29'
Machine': Dorado (Burton)'
Microcode version': 24,4'
Memory size': 10000'
Frequency': Once'
Impact': Moderate'
I created a message by shift selecting things out of an arform.  When I tried to deliver it, I told it to deliver plain text then got an illegal arg {imageobj}.  The imageobj was an MB (menu button) from the ar that was in the body of the message.  John believes there is a missing call to COERCETOTEXT some where in lafite.'
It occurs to me that this may be a place to call the IMAGEOBJ PREPRINTFN and that the PREPRINTFN for menu buttons should produce the text (The PREPRINTFN currently for MBs is NIL.)'
Date': 16 May 84 11':11 PDT'
When sending plain text, Lafite does not call COERCETEXTOBJ, assuming that BIN will produce plain text.  In the case where the text has imageobj''s in it, of course, such an approach has no hope of producing text for the imageobj, and Lafite should probably at least warn you about that.'
The error you report is where BIN of a textstream is getting not a byte, but an IMAGEOBJ.  From my point of view, that is clearly a Tedit bug.  I suspect the view is different from TeditSupport.  Perhaps we need to talk about what the right thing is.'


Test Case: 

Edit-By: Sybalsky

Edit-Date: 12-Sep-84 13':57':30