I'm converting DOORS tables into RTF and storing them in the "Object Text" attribute. After conversion, the module becomes unresponsive-either it fails to open if the converted object is visible by default, or it hangs with an infinite loading icon when scrolling to the converted object.

The original tables contain a large amount of content (~90k characters). Although IBM documentation states there's no character limit for Text attributes, reducing the size to ~60k resolves the issue, and the module functions normally.

No memory overflow messages are shown.

Has anyone encountered similar behavior? Could this be a rendering limitation rather than a character limit?

Saying an attribute has no limit does not mean anybody tried a test with 90k characters!  

How many of these tables do you expect?  If you only have a small number I would suggest an embedded spreadsheet

I'm converting DOORS tables into RTF and storing them in the "Object Text" attribute. After conversion, the module becomes unresponsive-either it fails to open if the converted object is visible by default, or it hangs with an infinite loading icon when scrolling to the converted object.

The original tables contain a large amount of content (~90k characters). Although IBM documentation states there's no character limit for Text attributes, reducing the size to ~60k resolves the issue, and the module functions normally.

No memory overflow messages are shown.

Has anyone encountered similar behavior? Could this be a rendering limitation rather than a character limit?

Hello Richard, 

thank you for your feedback.

That's exactlly what I opted for, I converted and stored DOORS tables inside Excel spreadsheets using the provided API.

Then I inserted the spreadsheets inside of the object text.

I have quite a large number of these tables in my modules, will these inserted OLE spreadsheets be bad for the performance of the module? or be bad in any way?

Saying an attribute has no limit does not mean anybody tried a test with 90k characters!  

How many of these tables do you expect?  If you only have a small number I would suggest an embedded spreadsheet

I'm converting DOORS tables into RTF and storing them in the "Object Text" attribute. After conversion, the module becomes unresponsive-either it fails to open if the converted object is visible by default, or it hangs with an infinite loading icon when scrolling to the converted object.

The original tables contain a large amount of content (~90k characters). Although IBM documentation states there's no character limit for Text attributes, reducing the size to ~60k resolves the issue, and the module functions normally.

No memory overflow messages are shown.

Has anyone encountered similar behavior? Could this be a rendering limitation rather than a character limit?

There is an option some place to stop OLE objects being duplicated when you create baselines. Other than that there should be no problem. If you are concerned you could place the OLE into a file system and create an external link to it. Downside of that is that you lose the preview image in the module. 

------------------------------
Richard Watson

Original Message:
Sent: Wed May 14, 2025 04:53 AM
From: Khalid Khalid
Subject: DOORS / DXL richText & rendering issue

Hello Richard, 

thank you for your feedback.

That's exactlly what I opted for, I converted and stored DOORS tables inside Excel spreadsheets using the provided API.

Then I inserted the spreadsheets inside of the object text.

I have quite a large number of these tables in my modules, will these inserted OLE spreadsheets be bad for the performance of the module? or be bad in any way?

------------------------------
Khalid Khalid

Original Message:
Sent: Sun May 11, 2025 07:00 AM
From: Richard Watson
Subject: DOORS / DXL richText & rendering issue

Saying an attribute has no limit does not mean anybody tried a test with 90k characters!  

How many of these tables do you expect?  If you only have a small number I would suggest an embedded spreadsheet

------------------------------
Richard Watson

Original Message:
Sent: Thu May 08, 2025 01:04 PM
From: Khalid Khalid
Subject: DOORS / DXL richText & rendering issue

I'm converting DOORS tables into RTF and storing them in the "Object Text" attribute. After conversion, the module becomes unresponsive-either it fails to open if the converted object is visible by default, or it hangs with an infinite loading icon when scrolling to the converted object.

The original tables contain a large amount of content (~90k characters). Although IBM documentation states there's no character limit for Text attributes, reducing the size to ~60k resolves the issue, and the module functions normally.

No memory overflow messages are shown.

Has anyone encountered similar behavior? Could this be a rendering limitation rather than a character limit?

------------------------------
Khalid Khalid
------------------------------