Adobe Community : All Content - All Communities

Pod scrollbox issue

forums_noreply@adobe.com — Wed, 18 Jun 2014 12:58:23 GMT

Hi,

I have seen this issue for some time now, both with FM11 on Win XP and Win7, and FM12 on Win7. It is such an aggravating problem that I thought surely somebody else would have complained about it by now. So I decided that it must be some anomaly in my little world here. But recently, we've gotten a second copy of FM for somebody else and the same thing is happening. So let me ask all of you.

When a pod with a scrollbox is docked, AND there is something currently selected, AND you scroll that item out of site, the next click in the scroll box returns that item to the top and makes you select something that you didn't want to. Consider the following example, where element "A" is selected in the catalog:

Then, I scroll the list down like so...

Then, I try to click "M". Upon the click, the list first jumps back up to put "A" at the top and then I end up selecting "G", which is where the "M" was:

Has anyone seen this? It is incredibly annoying and makes you have to click down the list just to get to something. Plus you have to double check everything you select, because it might not be what you selected. The behavior seems consistent with all scrollboxes, whether part of a native FM pod or an FDK-generated pod. Also, it only seems to be a problem when the pod is docked.

Russ

Command object Delete() and CommandNum property issues

forums_noreply@adobe.com — Tue, 10 Sep 2013 19:15:25 GMT

Hi,

FM11. I can't seem to get the Delete() method to work on commands, nor can I retreive the proper CommandNum property. For example:

cmd = DefineCommand(1111, "TestScriptCommand", "TestScriptCommand", "^q");

alert(cmd.CommandNum);

...the message box displays some other number, like 48 or something. Then, cmd.Delete() seems to have to effect, because the command stays active and remains on any menus where I placed it.

the Command() callback works OK. It properly executes on 1111 for the command.

FM12 console appears with every XSLT transform

forums_noreply@adobe.com — Thu, 03 Apr 2014 15:02:46 GMT

Hi,

FM12.0.0.329, Win7

This question has been asked in various permutations with little successs, but let me try again. I need to find a way to disable the Console panel, which pops up every time I open an XML document with a message similar to the following:

XML Read Report Log

Source Document: C:\documentation_test\common\modules\test_ipeth_ping.xml

XSLT Processor Messages

Transformation Successful.

Everything worked fine but I still get this message with every document. Can I make it stop? If anyone from Adobe is reading, I want to say with some emphasis that this situation makes FM12 unworkable for me. I can't justify migration from FM11 if there is no way to stop this intrusion.

Thanks,

Russ

ANN: New ExtendScript samples for beginners

forums_noreply@adobe.com — Wed, 05 Mar 2014 13:53:14 GMT

Hi,

I've worked up a set of samples designed to help beginners get started with ExtendScript. This is mainly as a public service, as I felt there was a lack of simple, working samples out there to help new users get started. I really feel that the ability to customize FrameMaker is one of its great strengths and the acceptance of ExtendScript is very important to its future. So, if we want the product to stay competitive, it's my belief that more ExtendScript usage is critical.

Anyway, I encourage you to get to know it, not just for FrameMaker's sake, but also for your own professional development. Technical writers who can customize their tools, even in small ways, significantly increase their market value. ExtendScript can be tricky to get a hold of at first, even for an experienced FDK developer, but the effort is well worth it.

Enjoy, and feedback is welcome!

http://www.weststreetconsulting.com/WSC_ExtendScriptSamples.htm

Russ

(cross-posting to the main FM forum)

ANN: New ExtendScript samples for beginners

forums_noreply@adobe.com — Wed, 05 Mar 2014 13:52:13 GMT

Hi,

Enjoy, and feedback is welcome!

http://www.weststreetconsulting.com/WSC_ExtendScriptSamples.htm

Russ

(cross-posting to the scripting forum)

[This thread in the General forum is locked. Please comment or discuss in the Scripting forum here:

http://forums.adobe.com/thread/1421166?tstart=0 ]

Extendscript - Book component type - ES bug or doc error?

forums_noreply@adobe.com — Mon, 20 Jan 2014 22:27:00 GMT

Hi,

(FM 11, Win XP)

When you query ComponentType for an FM document book component, you get hexadecimal 0x200 which happens to equal Constants.FV_BK_FILE. However, the documentation says that this property should return one of:

• Constants.FV_BK_FOLDER (0x02) - Folder

• Constants.FV_BK_GROUP (0x40) - Group

• Constants.FV_BK_FM (0x8) - FrameMaker document

• Constants.FV_BK_MIF (0x10) - MIF document

• Constants.FV_BK_XML (0x20) - XML document

Given the supposed MIF and XML options, I'm not sure if there is a bug in ES or if the documentation is just wrong. An XML component also returns 0x200. Any thoughts?

Thanks,

Russ

How to clone a data structure object (ExtendScript)?

forums_noreply@adobe.com — Tue, 24 Sep 2013 15:16:38 GMT

Hi,

Is there some quick way to clone a data structure, like a text range, rather than doing all this:

newTR = new TextRange();

newTR.beg.obj = oldTR.beg.obj;

newTR.beg.offset = oldTR.beg.offset;

newTR.end.obj = oldTR.end.obj;

newTR.end.offset = oldTR.end.offset;

I tried this, but it failed as I expected:

newTR = oldTR.clone();

I tried this, but I got back the same object:

newTR = new TextRange(oldTR.beg, oldTR.end);

Any ideas?

Thanks,

Russ

Technique to undo a character format application?

forums_noreply@adobe.com — Thu, 12 Sep 2013 13:20:31 GMT

Hi,

Seems that answers to complicated questions are a bit sparse in these parts, but I'll try again anyway

I'm wondering if there is any technique to reliably undo a character format application change; that is, an application of properties to a range of text with SetTextProps(). It is fairly simple to remember a list of original properties (PropVals) and the original text range (TextRange), then reapply those original properties to the whole range. However, within a text range, each character can have its own unique set of properties. So, remembering one set of original properties is not enough... seems I have to remember the properties of every single character in the range, the reapply character-by-character, in order to ensure that the new property application is completely undone.

When you apply a character format in the GUI, FM reliably allows an undo, restoring each affected character to its original state. Surely it isn't remembering a PropVals array for every single character (?) I'm just wondering if there is another trick here. It's entirely possible if FM is internally using another trick, it isn't one that I can feasibly replicate.

Thanks,

Russ

Script will not run with ]]> in it

forums_noreply@adobe.com — Tue, 20 Aug 2013 13:54:22 GMT

Hi,

This is just a heads up, perhaps someone could verify... if I put the character sequence ]]> anywhere within a JSX file, even within a comment, the script won't run when invoked from the toolkit window. It just hangs at the outset.

Russ

Workaround for ]]> XML export bug with schema?

forums_noreply@adobe.com — Fri, 16 Aug 2013 14:25:48 GMT

Hi,

It is a known issue that the ]]> sequence will not export properly to XML. If you are using a DTD, there is an entity-based workaround that is described here:

http://forums.adobe.com/message/3774389

The question... is there a workaround when using schema? I'm unable to figure it out.

Thanks,

Russ

ANN: WS Utilities 2.00 (FM plugin) release

forums_noreply@adobe.com — Tue, 21 May 2013 14:36:34 GMT

Hi,

I'd like to announce the release of v2.00 of our West Street

Utilities plugin for FM 8, 9, 10, and 11, structured or unstructured.

This release adds a variety of features that make the plugin much more

useful than before. To learn more and/or download a fully-functional

trial version, please visit:

http://www.weststreetconsulting.com/WSC_Utils.htm

Thanks,

Russ

FDK - Add custom modeless dialog to workspace

forums_noreply@adobe.com — Wed, 27 Feb 2013 18:55:51 GMT

(cross-posted to framedev and Framers, having no luck getting an answer)

Hi,

Has anyone successfully added their own dialog to a workspace, then gotten it to

appear when that workspace is selected or reset? The FDK doc implies that this

can be done, but I can't figure it out. I open my dialog box, save the

workspace, but it doesn't come back when I reset the workspace.

I actually did not expect that to work, because there has to be some other hook

where I respond by executing the proper code to launch the box. FM couldn't know

what that code would be. But, I can't figure out how to work the notifications.

In particular, I can't figure out FA_Note_Dialog_Create at all.

Thanks,

Russ

Missing menu commands in FM11

forums_noreply@adobe.com — Thu, 27 Dec 2012 18:24:12 GMT

Hi,

FM11, structured, original release (not patched), Win XP

I have begin to notice a number of commands that have disappeared from FM menus with version 11, including:

Format > Font

Format > Paragraph

Format > Style

Format > Characters

Format > Paragraphs

Table > Custom Ruling And Shading

I first noticed this when I needed to undo some wacky ruling and shading that came in with a table pasted from MS Word. I could get the ruling and shading pod using the keyboard shortcut (Esc t x) but just cannot get it to appear in the Table menu. I am in the WYSIWYG view and it doesn't matter whether a structured or unstructured document is active.

Does anyone know what I'm overlooking here? Did somebody decide that I don't need these functionalities because I have the product interface set to structured?

Thanks,

Russ

How to reliably close a palette window

forums_noreply@adobe.com — Thu, 18 Oct 2012 21:51:30 GMT

Hi,

I'm trying to figure out how to positively close a palette window that has both an X in the upper right corner and a Close button. The reason is that I want to use the Window.find() method to determine if the window already exists when someone attempts to launch it, such that duplicate palettes cannot be produced, for example

var graphicUtilsDlg = Window.find ("palette", "My Graphic Utilities");

if(graphicUtilsDlg != null) return;

So, I define this palette as graphicUtilsDlg, but before I do, I call the method above to see if a current instance exists.

On the palette, I have a Close button tied to the following callback:

graphicUtilsDlg.closeBtn.onClick = function()

{

graphicUtilsDlg.close();

graphicUtilsDlg = null;

};

...and the following callback which is invoked by the close() method above and also when the X is clicked:

graphicUtilsDlg.onClose = function()

{

graphicUtilsDlg = null;

};

It works fine when I click the Close button. The window closes and the next attempt to open it works normally. However, it does not work properly when I click the X button. It takes two attempts before the window opens again. Somehow, the find() method is returning an object the first time, but not the second time.

Anyway, I know this is a bit windy and complex, but does anyone have any expertise here?

Thanks,

Russ

Can't add a new menu

forums_noreply@adobe.com — Thu, 18 Oct 2012 13:35:25 GMT

Hi,

(FM10, Win XP)

Following the example in the scripting guide to add a menu with ES, I just can't get it to work. I expect the menu to appear after I run the script, which it does when I run the equivalent with the FDK. What am I missing here?

var fmMainMenu = app.GetNamedMenu("!MakerMainMenu") ;

var newMenu = fmMainMenu.DefineAndAddMenu("MyMenu1", "MyMenu1");

I tried adding a command to the menu and get no errors, but the new menu still does not appear.

Thanks,

Russ

Setting and getting a drop down list selection

forums_noreply@adobe.com — Fri, 03 Aug 2012 20:58:42 GMT

Hi,

This is a general ES question, but since I'm working with FM, I'll try here first.

I am able to create dropdown lists with ES and set/get the current selection, but I'm not clear on why it is working the way it does. It seems that when I set the selection, it uses an index of the current items, but when I get the selection, it gets the actual value.

Consider this sample, with its comments:

//create the dropdown, for the dlg dialog

dlg.dropDown = dlg.add("dropdownlist", undefined, [10, 20, 30]);

//this sets the current value in the box to 30

dlg.dropDown.selection = 2;

//however, this reports 30, not 2

alert(dlg.dropDown.selection);

Does anybody know about this? Is it true that it is an index when set, and a value when gotten? I couldn't find anything in the documentation about it.

Thanks,

Russ

Syntax errors with ES freeze/hang FM

forums_noreply@adobe.com — Tue, 31 Jul 2012 18:18:16 GMT

Hi,

I keep bumping into situations where a small syntax error causes FM to freeze, like there is a modal dialog open except there is no dialog. For example:

doc = app.ActiveDoc();

...this is wrong because of the parenthesis, but rather than throwing any errors, FM just freezes and I can't get it unfrozen, except to kill it with the Task Manager. Is there a way to prevent this freeze or at least thaw it out? It's becoming tiresome to restart FM and reset locks, etc. with every little typo.

Thanks,

Russ

Can't get graphic import parameters to work

forums_noreply@adobe.com — Tue, 31 Jul 2012 19:31:58 GMT

Hi,

I'm trying to import a graphic by reference at a set DPI (222). The following code sample imports the graphic, but ignores the DPI setting. Can anyone see what is wrong? A few notes:

- I wrote an FDK equivalent and it worked fine, following the exact same methodology.

- The GetImportDefaultParams() populates an array of about 45 members and GetPropIndex() retrieves unique indexes, suggesting that those parts are working

- Upon experimentation, I find that parms[index].PropIdent is always undefined, which seems weird.

Thanks.

var doc = app.ActiveDoc;

var tl = new TextLoc();

tl.obj = doc.FirstSelectedGraphicInDoc;

if(!tl.obj.ObjectValid) tl.obj = doc.MainFlowInDoc.FirstTextFrameInFlow.FirstPgf;

tl.offset = 0;

var parms = GetImportDefaultParams();

index = GetPropIndex (parms, Constants.FS_GraphicDpi);

parms[index].TypedVal = 222;

index = GetPropIndex (parms, Constants.FS_FitGraphicInSelectedRect);

parms[index].TypedVal = false;

var returnParms = new PropVals();

doc.Import(tl, "C:\\temp\\delete\\222_dpi.jpg", parms, returnParms);

Passing an FDK object to ES

forums_noreply@adobe.com — Tue, 29 May 2012 20:19:08 GMT

Hi,

As an FDK developer, I'm finding more and more reasons for interaction between API clients and ES scripts. For the most part, everything works very well, but I've run across an issue with CallClient() that I'm not able to figure out.

In summary, I want to somehow return a document object from a client to ES. It is simple to return an FDK object handle (F_ObjHandleT) to other FDK clients (and to ES), but I can't see any way to convert an FDK object handle to an ES document object. For example, in my F_ApiNotify() FDK code, I can put something like this:

F_ObjHandleT docId;

docId = F_ApiGetId(0, FV_SessionId, FP_ActiveDoc);

return (IntT)docId;

...and CallClient will get back the document ID. This is simple to work with if I made the call from another FDK client, but I don't know what to do with the ID within ES.

For objects within documents, you can get around this by returning a unique ID (FP_Unique) of the object instead, which ES can readily convert back to an object with GetUniqueObject(). However, there is apparently no such property or method at the document level.

Interestingly, it seems that you can go the other direction; that is, from an ES object to an object handle, using the 'id' property, as in:

var oDoc = app.ActiveDoc;

alert(oDoc.id);

I don't know how reliable this is, though, as it seems to be undocumented. Anyway, what I want to do is go in reverse, so that a client can return something that uniquely identifies an open document.

Any ideas?

Thanks in advance,

Russ

Set zoom levels crash?

forums_noreply@adobe.com — Fri, 27 Apr 2012 13:20:57 GMT

Hi,

FM10.0.1.402, WinXP, structured interface.

When I try to set the zoom levels (Zoom Menu Options), I reliably get a crash, although the new settings are saved. A colleague is also reporting this. Can someone verify, before I submit a bug report? We both have lots of custom addins running, so it would be good to get a "clean" opinion.

Russ

PDF text flow is different than original FM flow

forums_noreply@adobe.com — Wed, 14 Dec 2011 14:02:33 GMT

Hi,

A general question here for the PDF gurus. In some cases, the text flow in an FM-generated PDF is different than the original flow in the FM file. For example, a line that bumps to the next page in the FM doc might squeeze onto the previous page in the PDF. From a style perspective, there is no problem, as the general layout seems to adhere to the template. However, what is happening to me is that the targets to xrefs are moving to different pages, making the page numbers in the xref text incorrect.

As I investigate further, the root cause appears to be a change in the way that text wraps within table cells (and maybe anywhere else). In the PDF, wrapping is slightly less stringent, occasionally allowing an extra word per line. Eventually, this eliminates a whole line altogether, moving everything else in the flow one line up.

If anyone has any insight to this, I'd be most appreciative. I could possibly post some sample files, but it would not be particularly easy. I'm using FM10.0.1.402 on Windows XP, structured documents. To make a PDF, I use the Save As PDF command at the book level.

Thanks,

Russ

XML import deletes whitespace after xref element

forums_noreply@adobe.com — Thu, 29 Sep 2011 14:57:54 GMT

Hi,

FM10 not patched, WinXP SP3

I've bumped into a very serious problem that I am able to replicate, but not solve. When I import (custom) XML, any whitespace following <xref> elements is deleted. I don't know if it exclusive to crossreference elements or any no-content elements... but for sure it is happening with xrefs.

Here is a zip with sample files with which I am able to replicate this. The XML file has two <xref>s separated by "and". When you import the XML (using the DTD, rules, and template provided), the whitespace before the "and" is deleted.

http://www.weststreetconsulting.com/downloads/test.zip

I disabled all my personal plugins and all DITA plugins that I could find, same thing.

I don't know if anyone has the time to look at this, but I'd be very appreciative if anyone could confirm the problem. This has caused a real mess in my source files that I can go fix using non-breaking spaces, but this is really a pain and very much suboptimal.

Thanks,

Russ

FM10 - Can't save structured docs to FM9 format?

forums_noreply@adobe.com — Wed, 21 Sep 2011 02:38:47 GMT

Hi,

I need a sanity check here before reporting a bug. With FM10 (not patched), I still get an FM10 document when I Save As to Document 9.0 (*.fm), but only with structured documents. Unstructured docs seem to convert fine. I'm assuming they are still FM10... at least that's what FM9 is telling me, and I get no warning when opening in FM10. Furthermore, opening the file in a text editor shows the initial text <MakerFile 10.0>. I'm on Win XP, SP3.

Thanks,

Russ

Urgent problem - FM crashes on startup

forums_noreply@adobe.com — Tue, 30 Aug 2011 20:35:08 GMT

Hi,

I was doing some FDK work with FM10 to troubleshoot a crash, nothing unusual there. But after one particular crash, now FM10 suddenly crashes every time on startup. What's more, my installation of FM9 now crashes on startup too. I have FM 7.2 installed also... it does not crash.

I disabled all my API clients, deleted everything out of the Windows user profile area, and restarted the computer... no joy. Both FM9 and FM10 crash when the splash screen reaches "Localization." Both applications were installed as part of the respective TCS and neither was fully patched.

Can anybody think of anything I can delete or reset to try to fix this? I had originally thought to try reinstalling, but as I see FM9 crashing too, I'm wondering if I should bother with that. Is there something that each of these applications shares that could have gotten corrupted?

This puts me in a real pickle. I would be enormously grateful if anyone had any ideas at all. I'll likely try a reinstall anyway but I thought I'd give this a shot first.

Thanks,

Russ

Can't upgrade FM9 to 9.0.4

forums_noreply@adobe.com — Tue, 01 Mar 2011 14:22:27 GMT

Hi,

When I try to run the 9.0.4 installer, I get the message:

"You do not have correct version [sic] of FM install [sic] on your system. This patch installer will work only with Version 9 p250 build. Patch installer will quit now."

Help > About says Version 9.0p250.

Anybody have any advice? Thanks.

Russ

FM9 crash with DITA cross-reference dialog open

forums_noreply@adobe.com — Wed, 02 Jun 2010 18:36:54 GMT

Hi,

I'm looking for any insight on this apparent bug with the FM-DITA package, perhaps one of its authors will swing by and be able to comment. I'm basically trying to confirm that it is FM-DITA... more specifically, the cross-reference dialog box/pod.

The crash occurs when you attempt to create a new document with File > New > Document AND the template you use is already open AND the DITA cross-reference dialog is open. So, you would do something like this:

- Open a DITA file (i've been using binary FMs to diagnose, don't know what happens with XML) and get the DITA cross-reference dialog open somehow

- Go to File > New > Document and navigate to that same file in the file system

- Select that file and click New, then crash.

The problem occurs whether the dialog is showing or if it is "hidden"; ie, you just clicked the X in the corner. In FM9, that doesn't really close an FDK dialog, it just hides it, but it is somewhere behind the scenes trying to do whatever it is supposed to do.

This crash also occurs when you perform a comparable action with the FDK (that is, using F_ApiOpen() with parameters set up to open a file copy). That is how I stumbled upon it... one of the things my AXCM plugin does is duplicate files before filtering actions and a user started getting crashes consistently. It was a bit confounding at first, because all the debugger showed me was a crash at F_ApiOpen() (and a bunch of stack stuff that I don't understand). I finally tracked it down to this other plugin, I think.

Russ

Problem exporting graphics to XML - dpi vs. impsize

forums_noreply@adobe.com — Mon, 02 Nov 2009 13:48:20 GMT

Hi,

FM 7.2b128, exporting XML using schema.

I've had a structured app that I've used for a while that exports an impsize attribute (which I want) and does not export the dpi. The read/write rule is:

element "image"
{
is fm graphic element;
attribute "impsize" is fm property import size;
attribute "impby" is fm property import by reference or copy;
attribute "sideways" is fm property sideways;
attribute "impang" is fm property import angle;
attribute "xoffset" is fm property horizontal offset;
attribute "yoffset" is fm property vertical offset;
attribute "position" is fm property position;
attribute "align" is fm property alignment;
attribute "cropped" is fm property cropped;
attribute "float" is fm property floating;
attribute "width" is fm property width;
attribute "height" is fm property height;
attribute "angle" is fm property angle;
attribute "nsoffset" is fm property near-side offset;
}

However, I've been making some schema/EDD updates and other changes and suddenly impsize is no longer exported, only dpi. I can't figure out anything I might have changed to cause this to happen. In the documentation, it suggests that I should put in a "specify size as" rule, so I did that, but I still can't get the impsize back unless I put in a rule to drop the dpi, such as:

element "image"
{
is fm graphic element;
writer facet default
{
specify size in in;
}
attribute "impsize" is fm property import size;
attribute "dpi" drop;
attribute "impby" is fm property import by reference or copy;
attribute "sideways" is fm property sideways;
attribute "impang" is fm property import angle;
attribute "xoffset" is fm property horizontal offset;
attribute "yoffset" is fm property vertical offset;
attribute "position" is fm property position;
attribute "align" is fm property alignment;
attribute "cropped" is fm property cropped;
attribute "float" is fm property floating;
attribute "width" is fm property width;
attribute "height" is fm property height;
attribute "angle" is fm property angle;
attribute "nsoffset" is fm property near-side offset;
}

So, is this is working, but is it the right way to do it? Did I just get lucky before that impsize was exported instead of dpi?

Thanks,

Russ

ANN: WS Utilities (new plugin) released

forums_noreply@adobe.com — Thu, 22 Oct 2009 11:05:03 GMT

Hi,

We've just released a new plugin called West Street Utilities which currently adds a host of new features for graphics management. These features include the ability to compare graphics in a file system against your FM source files, to see what is used and where. For more information, see:

http://www.weststreetconsulting.com/WSC_Utils.htm

Unlike our other plugins, this one is not structure-oriented and can be used on any FM 7, 8, or 9 file.

Thanks,

Russ Ward

Owner, WSC

ANN: WS Structure Tools 2.0 is released

forums_noreply@adobe.com — Tue, 08 Sep 2009 20:17:19 GMT

Hi,

West Street Consulting is pleased to announce the release of its Structure Tools plugin, version 2.0. This version includes a new modeless attribute editor that significantly speeds up the process of editing attribute values, with a variety of amenities such as multiple element support, alphabetization, and tokenized values. The software is not free; however, a fully-functional shareware version is available for you to try it out. For more information, please visit www.weststreetconsulting.com.

Thanks,
Russ Ward
Owner

ANN: AXCM 2.0 (formerly ABCM) released

forums_noreply@adobe.com — Fri, 28 Aug 2009 02:09:58 GMT

Finally, after a number of hurdles, AXCM 2.0 has been released. Among other features, this version provides a new ability to construct schemes using XPath expressions, a powerful expansion of conditional evaluation options. It is supported on structured FM 7, 8, and 9 for Windows only. It is still completely free. For more information and/or to download, please visit www.weststreetconsulting.com. Thank you.

Russ (owner, WSC)

Can't make a PDF from a 40" x 24" template

forums_noreply@adobe.com — Wed, 15 Jul 2009 02:09:22 GMT

PDF gurus,

I have a doc with a page size of 40" x 24" that I can't seem to convert to PDF. When I Save As PDF, I get the correct page size but an empty document. When I print to postscript and distill, I get an 8.5x11 block of the original file. Not reduced, just a letter-sized block taken out of the center, looking correct for the small bit of the file that was captured.

Have I exceeded some limitation here or am I doing something wrong? I've tried it on FM7, 8, and 9 with the same results. FWIW, all fonts in the doc are 125pt or bigger and all text is white with a big black frame behind it.

I've attached the file in FM7 format if anyone is interested.

Thanks,

Russ

InsetPlus 2.1 is now available

forums_noreply@adobe.com — Wed, 03 Dec 2008 02:44:11 GMT

Hi,

InsetPlus 2.1 for structured FrameMaker is now released, including some important usability enhancements that have made it a much better tool. If you are a current user of the software, I'd encourage you to take a look at it. InsetPlus is free. For more information, visit:

http://www.weststreetconsulting.com/WSC_InsetPlus.htm

Best regards,
Russ Ward (Owner, West Street Consulting)

FDK: Restrict ability to edit an element's contents

forums_noreply@adobe.com — Fri, 21 Nov 2008 19:31:42 GMT

(cross-posted to the Yahoo frame_dev list)

Hi,

Is there a way to reliably restrict any kind of editing of an element's contents? I've played around with mouse-clicks and text selections and I am able to get an element to become selected with a mouse-click most anywhere within it, but it is not full-proof. For example, on the initial click, you can still drag graphics and elements around, edit attributes, etc.

The reason for my question is that I am enhancing InsetPlus to act more like native text insets and there is a user who wants them to behave exactly like them. I'm not sure if this is possible with the FDK.

Thanks,
Russ

XML file considered "Unknown File Type"

forums_noreply@adobe.com — Wed, 18 Jun 2008 10:52:56 GMT

Hi,

I have XML files that lack an XML declaration. Part of the import process, though, is an XSLT stylesheet that adds one through standard XSLT output (ie, omit-xml-declaration="no"). However, Frame still decides that it is an unknown file type and forces me to select "XML" in that dialog box.

When I run an XML file through the stylesheet manually (with another processor), I see the declaration added. Furthermore, the externally-transformed file imports without a hitch.

Any ideas why the declaration is not recognized when added by XSLT during the import process? More importantly, any ideas how to get around this?

Thanks,
Russ

"Unwrap" CDATA with XSLT

forums_noreply@adobe.com — Thu, 12 Jun 2008 20:41:00 GMT

Hi,

I know this isn't necessarily a FrameMaker question, but it is a place where I know people. So forgive me for asking it here.

I have some CDATA sections in an XML file that contain markup that I want to be parsed eventually, and I want to be able to extract it with the markup intact. Can I do this with XSLT, or does the nature of CDATA negate the use of retrieving the markup with an XML-parser-dependent technology?

Here's a sample element (element tags replaced with curly braces)

{documentation}{![CDATA[{p}Some text{/p}]]}{/documentation}

Is there any way I can get that p element out of there with XSLT, without excaping any of the characters, so it is parsable markup in the output?

[{p}Some text{/p}

Thanks,
Russ

Cool scrolling tip with wheel mouse

forums_noreply@adobe.com — Tue, 03 Jun 2008 23:19:55 GMT

Maybe everybody in the world knows this already, but I've never heard or seen in mentioned anywhere, and every time I use it, I think the world needs to know.

With my Microsoft wheel mouse, if I hold the Shift key and use the wheel to scroll a document, the document moves super fast. At 100% zoom, it seems to jump about a page with each wheel "notch." Ever since I discovered it accidentally, I use it regularly to scan through documents in a speedy fashion. I'm using Windows XP and it seems to work on all versions of FM through v8.0.

If you already knew this, sorry for wasting your time. It seems somewhat unique to FrameMaker... I don't know of any other applications that do it.

Russ

How to set the JavaHelp viewer

forums_noreply@adobe.com — Thu, 21 Feb 2008 15:00:13 GMT

Hi,

Robohelp 7, Windows XP, installed with the TCS

How do you point RoboHelp to a different JavaHelp viewer instance after it has been set initially? I was first using JavaHelp 1, but then installed JavaHelp 2, and I want to switch between the two for viewing, as I compile for the different versions. The only way I found to do it was to change the path to the active viewer which causes RoboHelp to lose it and to ask you again where it is.

And by the way, I looked in the help for this and I got some whacked out non-scrollable window that seemed to search the Adobe website, rather than provide help. Am I doing something wrong? It didn't look like a help system at all.

Thanks,
Russ

Can't display the Structure View window

forums_noreply@adobe.com — Mon, 17 Dec 2007 22:41:01 GMT

A post from Jerry Casher 12/17/07, typical of this problem:

I'm working with FrameMaker 7.0 windows XP and for some reason can no longer display the structure view with a document open. The buttons at the upper right of the screen all work fine, except the "Display structure view" button. I've tried the shortcut also (Esc+F i v), but that doesn't work either. I've minimized the active window to see if the Structure view window is underneath it, but it is not there.