📄 mruflist.txt
字号:
TdfsMRUFileList v2.67
Description:
A component that greatly simplifies adding MRU file lists to menus.
Features:
Defineable maximum number of items to be maintained in the list.
Automatic removal of item when selected, or not.
Items can exist on selected menu, or on submenu of selected menu.
Contact Information:
The lateset version will always be available on the web at:
http://www.delphifreestuff.com
If you have any questions, comments or suggestions, please use the Delphi
Free Stuff Support Forum at:
http://www.delphifreestuff.com/discus/
If, for some reason, you can not use the web-based support forum, you can
email me at bstowers@delphifreestuff.com. However, the support forum will
always take precedence over direct email since it provides a resource that
others can use when they have a problem. Every message posted to the forum
is emailed directly to this account, so emailing me directly will not get
your message to me any faster. It will only make the message less important
for me to respond to since only one person (you) is benefiting from it
instead of everyone interested. Having said all that, please do email me
directly if it is regarding something that isn't really support related,
i.e. just to say thanks (as novel as that idea is).
Installation:
Delphi 1:
* Select the 'Options | Install Components' menu item.
* In the Install Components dialog, click the Add button.
* In the Add Module dialog, enter the full path name of the component's
registration unit (the unit that ends with 'Reg.pas', i.e.
'BrowseDrReg.pas') and click OK.
* In the Add Module dialog, click OK.
* The component library will be rebuilt and a new tab named 'DFS' will
be available on the Component Palette.
Delphi 2, C++Builder 1:
* Select the 'Component | Install' menu item.
* In the Install Components dialog, click the Add button.
* In the Add Module dialog, enter the full path name of the component's
registration unit (the unit that ends with 'Reg.pas', i.e.
'BrowseDrReg.pas') and click OK.
* In the Add Module dialog, click OK.
* The component library will be rebuilt and a new tab named 'DFS' will be
available on the Component Palette.
Delphi 3, 4, 5, C++Builder 3 & 4:
* Do one of the following:
+ Create a new package by selecting File | New and choosing Package from
the New tab in the dialog.
+ Open an existing package file. I suggest you do this if you already
have a package that you like to use for small, third party components.
I specifically have a package named "3rdParty.dpk" that I use for
small components that come from other people. Or, if you are using
several of my components, you might create a "DFS.dpk" package and
use it for all of my DFS components.
* In the resulting package window, click the Add button.
* In the Add dialog, on the Add Unit tab, enter the full path name of the
component's registration unit (the unit that ends with 'Reg.pas', i.e.
'BrowseDrReg.pas') and click OK.
* You may want to add the other source files (*.pas) to the package as
well in the same manner as you did the registration unit. While this is
not required, not doing it will cause compiler warnings when the package
is compiled. The component will function fine either way, but I
personally find the warnings very irritating and am not happy until
every compiler warning and hint is gone.
* If this package is new, or it has never been installed, click the
Install button in the package window. If this package is already
installed in Delphi, click the Compile button.
C++Builder 5 and up:
* Perform the "Delphi 3 and up, C++Builder 3 and up" steps above, except
for the last step (Compile or Install).
* Select the package the component has been added to, and choose
Project | Edit Option Source to open the package options in the editor.
* In the entry for PFLAGS, add the "-LUvcl50" option. For example:
<PFLAGS value="-$YD -$W -$O -v -JPHNE -M -LUvcl50"/>
* Perform the final step from above, Compile or Install.
* For Borland's official word on this situation, open the C++Builder help
file and search the index for "dsgnintf.dcu" and see the "Compiling
packages with DsgnIntf" section.
Delphi 6 and up:
* Perform the "Delphi 3, 4, 5, C++Builder 3 & 4" steps above, except
for the last step (Compile or Install).
* Add the DesignIDE package to the Requires list of the package into which
the component is being installed.
* Perform the final step from above, Compile or Install.
* This is necessary because of changes to the design-time support units
introduced in Delphi 6. For complete information, see the Del6New.hlp
file in your Delphi 6 Help directory. In the index, search for
"upgrade issues" and in the resulting list of topics, select the
"DsgnIntf renamed and related changes" topic.
Known Issues:
* The component doesn't work well with the TMenuBar component (from Borland's
downloads page). I can find no reason for it, as TMenuBar is quite simple.
The problem must lie in either TMenu or TToolBar, and how I do things.
Revision History:
2.67: + Changing RemoveObsoleteName, ClearItemName, ShowRemoveObsolete or
ShowClearItem properties didn't have any effect at run-time until the
MRU list was rebuilt.
+ Updated for Delphi 6 compatibility. See updated install directions
above.
2.66: + Updated for C++Builder 5 compatibility.
2.65: + Fixed nasty bug that caused AVs on exit.
+ If more than 10 items were in the list, the '&' shortcut would be
screwed up (i.e. &10 conflicted with &1, &11, &12, etc.). Thomas
Weinert sent me a nice fix for this: 1 through 0 are used, followed
by A through Z. After that, no shortcut is given.
2.64: + Fixed nasty bug that caused the component to load mru items at design
time. This led to all sorts of nastiness. Still not sure how that
snuck in.
2.63: + It's *really* D5 compatible now. Small change between the D5 eval
version and the real, shipping D5 version broke it.
2.62: + There was an issue with auto loading not always working the way you
would expect, especially when using INI files. Fixed.
2.61: + Classname changed.
+ D5 compatibility.
2.60: + Two new events, OnCreateMRUItem and OnDestroyMRUItem. These events
fire, surprisingly enough, when an MRU menu item has been created
(and had it's properties set) or when an item is about to be destroyed.
You can use these events to do things like set the ImageIndex property
(in D4) of the menu item. You could also allocate some memory to be
associcated with an item in OnCreateMRUItem, and free that memory in
OnDestroyMRUItem. In anticipation of the question I'm about to be
asked 50 times, you can tell MRU items that are "real" items (i.e. a
file the user has closed) from the "helper" MRU items (like the
seperator items and Remove Obsolete commands) by checking to see if the
Item.ItemNumber is greater than zero. If it is, it's a "real" item.
I chose this approach over a property that exposes the menu items
themselves because the menu items change so much. That is, if you just
had a property that contained all of the menu items, you'd have to know
when things changed so that you could go back and walk that list
resetting things like ImageIndex. This method seems simpler from both
a usage (you) and implementation (me) standpoint.
2.50: + Ugo Bernasconi added the MRUDisplay property. I've extended it a bit,
and here's how it works:
mdFullPath: Same behavior as prior versions.
mdFileNameExt: Displays just the file name and extension.
mdFileNameOnly: Displays just the file name.
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -