tiny marker window (WAS: SOLVED Index Problems)
Murray Moore wrote: > To make these entries easier for me to read and edit in the tiny > index marker window You might want to check into emDEX (an add-on utility) for indexing in FrameMaker. It allows you to customize the size of the marker box itself along with the font used in the marker box. In addition, you can customize ten different radio buttons in the emDEX marker box to contain ten different strings so that, with the press of the button (or a customized shortcut key combination), you can type in <$startrange>, etc. painlessly. emDEX also provides a preview window that allows you to view the index as it's being built. URL: http://www.emdex.ca/ Lucie Haskins
Re: tiny marker window (WAS: SOLVED Index Problems)
Murray Moore wrote: > To make these entries easier for me to read and edit in the tiny > index marker window You might want to check into emDEX (an add-on utility) for indexing in FrameMaker. It allows you to customize the size of the marker box itself along with the font used in the marker box. In addition, you can customize ten different radio buttons in the emDEX marker box to contain ten different strings so that, with the press of the button (or a customized shortcut key combination), you can type in <$startrange>, etc. painlessly. emDEX also provides a preview window that allows you to view the index as it's being built. URL: http://www.emdex.ca/ Lucie Haskins ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: tiny marker window (WAS: SOLVED Index Problems)
This is a decent idea, but it has pitfalls. I could explain the reasons why, but they are very technical. You will find, though, that if you're not careful when you modify the dialog box with ResHacker, you'll lose some of the UI. ResHacker assumes that the UI is static, so that the dialog box displays only what you see in the DLL. However, dialog boxes can contain controls that are set up as the program runs. You could re-size the dialog box or controls in ResHacker and then find that you've unintentionally hidden another part of the UI that you didn't see. I discovered this the hard way, and therefore gave up on ResHacker. If you just change fonts, you should be OK; just don't change the size of anything. I have no idea why FM engineers haven't changed the index marker dialog or the font size. I think it has to be no more than a 10-minute job. Joe Joe Malin Technical Writer (408)625-1623 [EMAIL PROTECTED] www.tuvox.com The views expressed in this document are those of the sender, and do not necessarily reflect those of TuVox, Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stuart Rogers Sent: Friday, August 04, 2006 1:30 PM To: Murray Moore Cc: framers@lists.frameusers.com Subject: tiny marker window (WAS: SOLVED Index Problems) Murray Moore wrote: > To make these entries easier for me to read and edit in the tiny > index marker window I too strongly encourage you to get IXGen or another indexing tool. But if that is not possible, you can save your eyesight by getting hold of ResHacker.exe at http://www.angusj.com/resourcehacker/ and using it to modify the characteristics of the marker dialog boxes. The file you want to modify (after backing it up!!) is fmdlg.dll in your installation\fminit folder. Look for EDIT_MARKERS and INS_MARKER and change the font size to something comfortable (I use 10 instead of the default 8). If you have Show Dialog selected, it's easy to drag the borders of the dialog box and its various components to a larger size as well. ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
tiny marker window (WAS: SOLVED Index Problems)
This is a decent idea, but it has pitfalls. I could explain the reasons why, but they are very technical. You will find, though, that if you're not careful when you modify the dialog box with ResHacker, you'll lose some of the UI. ResHacker assumes that the UI is static, so that the dialog box displays only what you see in the DLL. However, dialog boxes can contain controls that are set up as the program runs. You could re-size the dialog box or controls in ResHacker and then find that you've unintentionally hidden another part of the UI that you didn't see. I discovered this the hard way, and therefore gave up on ResHacker. If you just change fonts, you should be OK; just don't change the size of anything. I have no idea why FM engineers haven't changed the index marker dialog or the font size. I think it has to be no more than a 10-minute job. Joe Joe Malin Technical Writer (408)625-1623 jmalin at tuvox.com www.tuvox.com The views expressed in this document are those of the sender, and do not necessarily reflect those of TuVox, Inc. -Original Message- From: framers-bounces+jmalin=tuvox@lists.frameusers.com [mailto:framers-bounces+jmalin=tuvox.com at lists.frameusers.com] On Behalf Of Stuart Rogers Sent: Friday, August 04, 2006 1:30 PM To: Murray Moore Cc: framers at lists.frameusers.com Subject: tiny marker window (WAS: SOLVED Index Problems) Murray Moore wrote: > To make these entries easier for me to read and edit in the tiny > index marker window I too strongly encourage you to get IXGen or another indexing tool. But if that is not possible, you can save your eyesight by getting hold of ResHacker.exe at http://www.angusj.com/resourcehacker/ and using it to modify the characteristics of the marker dialog boxes. The file you want to modify (after backing it up!!) is fmdlg.dll in your installation\fminit folder. Look for EDIT_MARKERS and INS_MARKER and change the font size to something comfortable (I use 10 instead of the default 8). If you have Show Dialog selected, it's easy to drag the borders of the dialog box and its various components to a larger size as well.
tiny marker window (WAS: SOLVED Index Problems)
Murray Moore wrote: > To make these entries easier for me to read and edit in the tiny > index marker window I too strongly encourage you to get IXGen or another indexing tool. But if that is not possible, you can save your eyesight by getting hold of ResHacker.exe at http://www.angusj.com/resourcehacker/ and using it to modify the characteristics of the marker dialog boxes. The file you want to modify (after backing it up!!) is fmdlg.dll in your installation\fminit folder. Look for EDIT_MARKERS and INS_MARKER and change the font size to something comfortable (I use 10 instead of the default 8). If you have Show Dialog selected, it's easy to drag the borders of the dialog box and its various components to a larger size as well. HTH, -- Stuart Rogers Technical Communicator Phoenix Geophysics Limited Toronto, ON, Canada +1 (416) 491-7340 x 325 srogers phoenix-geophysics com "Computers in the future may weigh no more than 1.5 tons." --Popular Mechanics, 1949 Get Firefox! http://tinyurl.com/8q9c5
SOLVED Index Problems
It's a long-standing and well-documented bug that manual line breaks are not permitted in markers. But the problems that are usually reported are much more drastic than what you have been seeing (things like application crashes when generating/updating an index). But because it's hard to see in the marker window if/when there is a line break present, this is yet another strong argument in favor of using a marker interface enhancement like IXgen (my tool of choice) or IndexTools. Any of these tools make line breaks much more obvious than the standard marker dialog. My opinions only; I don't speak for Intel. Fred Ridder Intel Parsippany, NJ >From: "Murray Moore" >To: >Subject: SOLVED Index Problems >Date: Fri, 4 Aug 2006 14:20:00 -0400 > >My problems were: >* A ghost text entry >* Page numbers displaying under the Symbols heading, e.g. 8, 14, 22, 65, >68, 100 > >The ghost text entry disappeared in the course of deleting the page >numbers. > >The cause of the superfluous page numbers was inconsistent styles of index >markers. > >In my index, columns and buttons appear twice. > >Before I updated the index, the index markers were this style: > >button: name of button: name of window; button name: name of window > >To make these entries easier for me to read and edit in the tiny index >marker window, I changed: > >button: name of button: name of window; button name: name of window > >to: > >button: name of button: name of window; >button name: name of window > >The cause of the display of the orphan page numbers under Symbols is that I >did not change every index entry. One style of marker was followed by the >other style of marker, like this: > >button: name of button: name of window; button name: name of window > >button: name of button: name of window; >button name: name of window > >Using Ctrl + Alt and click, I returned every index marker of this style: > >button: name of button: name of window; >button name: name of window > >to this style: > >button: name of button: name of window; button name: name of window > >And FrameMaker was no longer confused. > >/\/\ >Murray >Mississauga _ Is your PC infected? Get a FREE online computer virus scan from McAfee? Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
SOLVED Index Problems
My problems were: * A ghost text entry * Page numbers displaying under the Symbols heading, e.g. 8, 14, 22, 65, 68, 100 The ghost text entry disappeared in the course of deleting the page numbers. The cause of the superfluous page numbers was inconsistent styles of index markers. In my index, columns and buttons appear twice. Before I updated the index, the index markers were this style: button: name of button: name of window; button name: name of window To make these entries easier for me to read and edit in the tiny index marker window, I changed: button: name of button: name of window; button name: name of window to: button: name of button: name of window; button name: name of window The cause of the display of the orphan page numbers under Symbols is that I did not change every index entry. One style of marker was followed by the other style of marker, like this: button: name of button: name of window; button name: name of window button: name of button: name of window; button name: name of window Using Ctrl + Alt and click, I returned every index marker of this style: button: name of button: name of window; button name: name of window to this style: button: name of button: name of window; button name: name of window And FrameMaker was no longer confused. /\/\ Murray Mississauga
SOLVED Index Problems
You can do a search on /p in "Marker Text". That's the quickest way I know of = Grant Hogarth Senior Technical Writer Equis International Equis International - A Reuters Company TZ: Mountain (GMT -7) Reuters Messaging: grant.hogarth.reuters.com at reuters.net (t) +1 801 270 3180 | (o) +1 801 265 9996| (f) +1 801 265 3999 Get the latest news at Reuters.com -Original Message- From: framers-bounces+grant.hogarth=reuters@lists.frameusers.com [mailto:framers-bounces+grant.hogarth=reuters.com at lists.frameusers.com] On Behalf Of Fred Ridder Sent: Friday, August 04, 2006 12:31 PM To: m.moore at csdcsystems.com; framers at lists.frameusers.com Subject: RE: SOLVED Index Problems It's a long-standing and well-documented bug that manual line breaks are not permitted in markers. But the problems that are usually reported are much more drastic than what you have been seeing (things like application crashes when generating/updating an index). But because it's hard to see in the marker window if/when there is a line break present, this is yet another strong argument in favor of using a marker interface enhancement like IXgen (my tool of choice) or IndexTools. Any of these tools make line breaks much more obvious than the standard marker dialog. My opinions only; I don't speak for Intel. Fred Ridder Intel Parsippany, NJ >From: "Murray Moore" >To: >Subject: SOLVED Index Problems >Date: Fri, 4 Aug 2006 14:20:00 -0400 > >My problems were: >* A ghost text entry >* Page numbers displaying under the Symbols heading, e.g. 8, 14, 22, >65, 68, 100 > >The ghost text entry disappeared in the course of deleting the page >numbers. >The cause of the superfluous page numbers was inconsistent styles of >index markers. > >In my index, columns and buttons appear twice. > >Before I updated the index, the index markers were this style: >button: name of button: name of window; button name: name of window >To make these entries easier for me to read and edit in the tiny index >marker window, I changed: >button: name of button: name of window; button name: name of window >to: >button: name of button: name of window; button name: name of window >The cause of the display of the orphan page numbers under Symbols is >that I did not change every index entry. One style of marker was >followed by the other style of marker, like this: >button: name of button: name of window; button name: name of window >button: name of button: name of window; button name: name of window >Using Ctrl + Alt and click, I returned every index marker of this style: >button: name of button: name of window; button name: name of window >to this style: >button: name of button: name of window; button name: name of window >And FrameMaker was no longer confused. > >/\/\ >Murray >Mississauga
tiny marker window (WAS: SOLVED Index Problems)
Murray Moore wrote: To make these entries easier for me to read and edit in the tiny index marker window I too strongly encourage you to get IXGen or another indexing tool. But if that is not possible, you can save your eyesight by getting hold of ResHacker.exe at http://www.angusj.com/resourcehacker/ and using it to modify the characteristics of the marker dialog boxes. The file you want to modify (after backing it up!!) is fmdlg.dll in your installation\fminit folder. Look for EDIT_MARKERS and INS_MARKER and change the font size to something comfortable (I use 10 instead of the default 8). If you have Show Dialog selected, it's easy to drag the borders of the dialog box and its various components to a larger size as well. HTH, -- Stuart Rogers Technical Communicator Phoenix Geophysics Limited Toronto, ON, Canada +1 (416) 491-7340 x 325 srogers phoenix-geophysics com "Computers in the future may weigh no more than 1.5 tons." --Popular Mechanics, 1949 Get Firefox! http://tinyurl.com/8q9c5 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: SOLVED Index Problems
You can do a search on /p in "Marker Text". That's the quickest way I know of = Grant Hogarth Senior Technical Writer Equis International Equis International - A Reuters Company TZ: Mountain (GMT -7) Reuters Messaging: [EMAIL PROTECTED] (t) +1 801 270 3180 | (o) +1 801 265 9996| (f) +1 801 265 3999 Get the latest news at Reuters.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fred Ridder Sent: Friday, August 04, 2006 12:31 PM To: [EMAIL PROTECTED]; framers@lists.frameusers.com Subject: RE: SOLVED Index Problems It's a long-standing and well-documented bug that manual line breaks are not permitted in markers. But the problems that are usually reported are much more drastic than what you have been seeing (things like application crashes when generating/updating an index). But because it's hard to see in the marker window if/when there is a line break present, this is yet another strong argument in favor of using a marker interface enhancement like IXgen (my tool of choice) or IndexTools. Any of these tools make line breaks much more obvious than the standard marker dialog. My opinions only; I don't speak for Intel. Fred Ridder Intel Parsippany, NJ >From: "Murray Moore" <[EMAIL PROTECTED]> >To: >Subject: SOLVED Index Problems >Date: Fri, 4 Aug 2006 14:20:00 -0400 > >My problems were: >* A ghost text entry >* Page numbers displaying under the Symbols heading, e.g. 8, 14, 22, >65, 68, 100 > >The ghost text entry disappeared in the course of deleting the page >numbers. >The cause of the superfluous page numbers was inconsistent styles of >index markers. > >In my index, columns and buttons appear twice. > >Before I updated the index, the index markers were this style: >button: name of button: name of window; button name: name of window >To make these entries easier for me to read and edit in the tiny index >marker window, I changed: >button: name of button: name of window; button name: name of window >to: >button: name of button: name of window; button name: name of window >The cause of the display of the orphan page numbers under Symbols is >that I did not change every index entry. One style of marker was >followed by the other style of marker, like this: >button: name of button: name of window; button name: name of window >button: name of button: name of window; button name: name of window >Using Ctrl + Alt and click, I returned every index marker of this style: >button: name of button: name of window; button name: name of window >to this style: >button: name of button: name of window; button name: name of window >And FrameMaker was no longer confused. > >/\/\ >Murray >Mississauga ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: SOLVED Index Problems
It's a long-standing and well-documented bug that manual line breaks are not permitted in markers. But the problems that are usually reported are much more drastic than what you have been seeing (things like application crashes when generating/updating an index). But because it's hard to see in the marker window if/when there is a line break present, this is yet another strong argument in favor of using a marker interface enhancement like IXgen (my tool of choice) or IndexTools. Any of these tools make line breaks much more obvious than the standard marker dialog. My opinions only; I don't speak for Intel. Fred Ridder Intel Parsippany, NJ From: "Murray Moore" <[EMAIL PROTECTED]> To: Subject: SOLVED Index Problems Date: Fri, 4 Aug 2006 14:20:00 -0400 My problems were: * A ghost text entry * Page numbers displaying under the Symbols heading, e.g. 8, 14, 22, 65, 68, 100 The ghost text entry disappeared in the course of deleting the page numbers. The cause of the superfluous page numbers was inconsistent styles of index markers. In my index, columns and buttons appear twice. Before I updated the index, the index markers were this style: button: name of button: name of window; button name: name of window To make these entries easier for me to read and edit in the tiny index marker window, I changed: button: name of button: name of window; button name: name of window to: button: name of button: name of window; button name: name of window The cause of the display of the orphan page numbers under Symbols is that I did not change every index entry. One style of marker was followed by the other style of marker, like this: button: name of button: name of window; button name: name of window button: name of button: name of window; button name: name of window Using Ctrl + Alt and click, I returned every index marker of this style: button: name of button: name of window; button name: name of window to this style: button: name of button: name of window; button name: name of window And FrameMaker was no longer confused. /\/\ Murray Mississauga _ Is your PC infected? Get a FREE online computer virus scan from McAfee® Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
SOLVED Index Problems
My problems were: * A ghost text entry * Page numbers displaying under the Symbols heading, e.g. 8, 14, 22, 65, 68, 100 The ghost text entry disappeared in the course of deleting the page numbers. The cause of the superfluous page numbers was inconsistent styles of index markers. In my index, columns and buttons appear twice. Before I updated the index, the index markers were this style: button: name of button: name of window; button name: name of window To make these entries easier for me to read and edit in the tiny index marker window, I changed: button: name of button: name of window; button name: name of window to: button: name of button: name of window; button name: name of window The cause of the display of the orphan page numbers under Symbols is that I did not change every index entry. One style of marker was followed by the other style of marker, like this: button: name of button: name of window; button name: name of window button: name of button: name of window; button name: name of window Using Ctrl + Alt and click, I returned every index marker of this style: button: name of button: name of window; button name: name of window to this style: button: name of button: name of window; button name: name of window And FrameMaker was no longer confused. /\/\ Murray Mississauga ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
