Skip to main content
K.Daube
Community Expert
Community Expert
April 20, 2017
Answered

FM-14: Tool bar flyout definition not working anymore

  • April 20, 2017
  • 1 reply
  • 515 views

I have posted this in the beta-test forum, but this may be a better place...

In FM-13 the tool bar has these buttons (in FM-14 I'm not yet successfull to see the icons, but the 'ordinary' buttons work):

FM-14: Using a button which leads to a flyout definition (as used successfully in FM-13) I get the error:

FrameMaker
No expression selected in an equation.

With all due respect: this is nonsense. The current location for the all of the intended functions must be in a paragraph, not in an equation. The code seems to be scrambled: I do not get this error, if the cursor is in an Equation for the first two cases (RulerAlignMenu, RulerTAbsMenu), but a tilt for the third case (RulerPgfActionsMenu)

In the menu is defined:

*** Ruler Align Menu ******************************
<ReservedMenu !RulerAlignMenu <Label Alignment>>
    <Add LeftPara         <Menu !RulerAlignMenu>>
    <Add CenterPara       <Menu !RulerAlignMenu>>
    <Add RightPara        <Menu !RulerAlignMenu>>
    <Add FullyJustifyPara <Menu !RulerAlignMenu>>

[etb Commands]
<Command ETBTabLeft           <Definition \x906>  <ReservedLabel Short &Left Tab> <Mode All>>
<Command ETBTabCenter         <Definition \x907>  <ReservedLabel Short &Center Tab> <Mode All>>
<Command ETBTabRight          <Definition \x908>  <ReservedLabel Short &Right Tab> <Mode All>>
<Command ETBTabDecimal        <Definition \x909>  <ReservedLabel Short &Decimal Tab> <Mode All>>

<Command ETBParaTopOfPage     <Definition \x28A>  <Label Place Pgf at Top of Page>  >
<Command ETBParaTopOfLeftPage <Definition \x28C>  <Label Place Pgf at Top of Left Page>  >
<Command ETBParaTopOfRightPage <Definition \x28D> <Label Place Pgf at Top of Right Page>  >
<Command ETBParaTopOfColumn   <Definition \x28B>  <Label Place Pgf at Top of Column> <KeySeqLabel   Shift+F11> >
<Command ETBParaAnywhere      <Definition \x28E>  <Label Place Pgf Anywhere> <KeySeqLabel   Shift+F12>>

[etb Ruler Menus]
<ReservedMenu !RulerTabsMenu  <Label Tab Stop Type>>
   <Add ETBTabLeft                      <Menu !RulerTabsMenu>>
   <Add ETBTabCenter                    <Menu !RulerTabsMenu>>
   <Add ETBTabRight                     <Menu !RulerTabsMenu>>
   <Add ETBTabDecimal                   <Menu !RulerTabsMenu>>

<ReservedMenu !RulerPgfActionsMenu <Label Pgf Operationss>>
   <Add ParaUpdateFormat                <Menu !RulerPgfActionsMenu>>
   <Add ParaNewFormat                   <Menu !RulerPgfActionsMenu>>
   <Add ParagraphFormatDesigner         <Menu !RulerPgfActionsMenu>>
   <Add ParagraphCatalog                <Menu !RulerPgfActionsMenu>>
   <Add Separator1                      <Menu !RulerPgfActionsMenu>>
   <Add ETBParaTopOfPage                <Menu !RulerPgfActionsMenu>>
   <Add ETBParaTopOfRightPage           <Menu !RulerPgfActionsMenu>>
   <Add ETBParaTopOfLeftPage            <Menu !RulerPgfActionsMenu>>
   <Add ETBParaTopOfColumn              <Menu !RulerPgfActionsMenu>>
   <Add ETBParaAnywhere                 <Menu !RulerPgfActionsMenu>>

In the tool bar this is defined:

<!-- !RulerAlignMenu is located in fminit\maker\menus.cfg -->
        <FLYOUT command="!RulerAlignMenu" tooltip="Text alignment">
            <images base="P_TextAlignLeft_Md"/>
        </FLYOUT>
<!--- RulerTabsMenu is located in fminit\configui\customui.cfg -->
        <FLYOUT command="!RulerTabsMenu" tooltip="Tab types">
            <images base="P_TabLeft"/>
        </FLYOUT>
<!--- RulerPgfActionsMenu is located in fminit\configui\customui.cfg -->
        <FLYOUT command="!RulerPgfActionsMenu" tooltip="Paragraph actions">
            <images base="etb-icons\para-actions"/>
        </FLYOUT>

I see that the word flyout is used extensively in the menu (even in FM_13), for example:

      <Menu FlyoutConditionalText <Label Conditional Text>>
      <Menu FlyoutTrackTextEdits <Label Track Text Edits>>

But in the standard tool bars of FM-14 it is exists only for the this:

        <FLYOUT command="SpecialSymbolsPopup">
            <images base="S_SPECIALSYMBOLS"/>
        </FLYOUT>

and this

    <FLYOUT command="DirectionSymbolsPopup">
      <images base="S_ARABICSYMBOLS"/>
    </FLYOUT>

What is going wrong with the flyout defintion for custom tool bars?

    This topic has been closed for replies.
    Correct answer K.Daube

    OK, but I don't think you're going to get much input from regular FM users on a topic like this in this forum - I was just offering to move it over...


    Concerning  this bug  FRMAKER-2764

    It turns out that the flyouts use a different mechanism in FM-14 compared to FM-13:
    A new command with parameters handles this kind of UI element. Hence I must define my command as:

    <Command ETBPgfAlignPopup    <Label  ETB paragraph alignment>
                                  <Definition \x914>
                                  <Param ETBPgfAlignMenu>>


    And specify the approptirate menu contents (as before, but reserved menu not required):

    <Menu ETBPgfAlignMenu <Label Alignment>>
        <Add LeftPara        <Menu ETBPgfAlignMenu>>
        <Add CenterPara      <Menu ETBPgfAlignMenu>>
        <Add RightPara        <Menu ETBPgfAlignMenu>>
        <Add FullyJustifyPara <Menu ETBPgfAlignMenu>>


    And use the command in the tool bar:

            <FLYOUT command="ETBPgfAlignPopup" tooltip="Text alignment">
                <images base="S_TEXT_ALIGN_LEFT"/>
            </FLYOUT>

    So I requested to close the bug report.

    1 reply

    Jeff_Coatsworth
    Community Expert
    Community Expert
    April 20, 2017

    Isn't this more of a Scripting question Klaus?

    K.Daube
    Community Expert
    K.DaubeCommunity ExpertAuthor
    Community Expert
    April 21, 2017

    Jeff, this goes under "customising FrameMaker". Only the menu files (menu.cfg) and tool bar files (xxx.xml) are affected. If this does not work, then scripting would probably also not work in this area.

    Jeff_Coatsworth
    Community Expert
    Community Expert
    April 21, 2017

    OK, but I don't think you're going to get much input from regular FM users on a topic like this in this forum - I was just offering to move it over...