FrameMaker 12 Publish Crash

Hi Anchal,

Thank you for all your efforts with this. However, the UserString issue is not fixed with the FrameMaker 12.0.2. Here is the way I am testing this:

1) Create a new Portrait FrameMaker document.

2) Create two small text frames at the top of the page.

3) Select one frame and run this:

#target framemaker
var doc = app.ActiveDoc;
var textFrame = doc.FirstSelectedGraphicInDoc;
textFrame.UserString = "Set with ExtendScript";
alert (textFrame.UserString);

The fifth line displays "Set with ExtendScript" like you would expect. However, when you comment out the fourth line and just try to display UserString, it displays "undefined".

I tried selecting the second text frame and repeating the test with FrameScript:

Set oTextFrame = FirstSelectedGraphicInDoc; 
Set oTextFrame.UserString = 'Set with FrameScript 6';
Display oTextFrame.UserString;

It displays the UserString like it should. When I comment out the second line and run it again, it still displays the correct UserString. If I save and close the document and reopen it, it still displays the correct UserString.

FrameScript 6 is correctly reading and writing the UserString property, but ExtendScript is not. Please let me know if you have any questions or comments. Thank you very much.

Rick

Hi Colin/Arnis,

Thanks for reporting the issue. We have noted the issue with us. Seems like the crash had been there since long (in the TCS route) – but went unreported as we had not been using UserString much internally. Now that the Publishing route (earlier part of TCS only) is a part of FM itself, the issue seems to have surfaced.

We are evaluating a fix for it and would like to understand more on the usage of “UserString”:

• UserString stores private data, what kinds of data is generally taken to the output?
• how is it interpreted (used) in the outputs: pdf/webhelp/epub?
• do you use its value in all outputs or some of them?

Regards,

Amit