Windows open/save dialog history




















So I'm guessing a confused IP table somewhere. I'm off to play with using fixed IP addresses and lease expiries in the LAN part of the new router's config to see if that makes it easier for XP to handle closed connections. Office Office Exchange Server. Not an IT pro? Windows Client. Sign in. United States English.

Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Windows 7 Networking. Sign in to vote. Both bit and bit systems are supported. Version 1. This feature only works for existing files.

In order to start using it, simply run the executable file - OpenSaveFilesView. The 'Order' Column The 'Order' column shows you the order that you opened the files. By default, the dialog box creates a zero-length test file to determine whether a new file can be created in the selected directory. If you enable a hook procedure, the dialog box notifies your hook procedure when a network sharing violation occurs for the file name specified by the user.

In this case, the dialog box returns the name of the link file rather than the name of the file referenced by the link file. You can customize an Open or Save As dialog box by providing a hook procedure, a custom template, or both. However, the Explorer-style and old-style versions of the dialog boxes differ in their use of custom templates and hook procedures.

The default title for both Explorer-style and old-style dialog boxes is either " Open " or " Save As. These registry entries affect only the dialog boxes displayed for the user associated with the registry hive. To hide features of Explorer-style Open and Save As dialog boxes, an administrator can set the values in the following table under this subkey:. The contents of the Places bar are determined by the contents of the following subkey:.

You can customize an Explorer-style Open or Save As dialog box by providing a hook procedure, a custom template, or both. If you provide a hook procedure for an Explorer-style dialog box, the system creates a dialog box that is a child of the default dialog box. The hook procedure acts as the dialog procedure for the child dialog box. This child dialog box is based on the custom template, or on a default template if none is provided.

For more information, see Explorer-Style Custom Templates. An Explorer-style hook procedure receives a variety of messages while the dialog box is open. These include the following:. In addition, there is a set of messages that you can send to an Explorer-style dialog box to get information or to control the behavior and appearance of the dialog box. You can use some of these messages to control the behavior of the dialog box.

In response to this message, the hook procedure can use the SetWindowLong function to reject the selected name and force the dialog box to remain open. The code member in the header of this structure contains one of the following notification messages. To retrieve information about the status of the dialog box or to control the behavior and appearance of the dialog box, the hook procedure can send the following messages to the dialog box.

Typically, if you provide additional controls, you must also provide an Explorer-style hook procedure to process messages for the new controls. To make room for the new controls, the system expands the default dialog box by the width and height of the custom dialog box. By default, all controls from the custom dialog box are positioned below the controls in the default dialog box. However, you can override this default positioning by including a static text control in your custom dialog box template and assigning it the control identifier value of stc This value is defined in the Dlgs.

In this case, the system uses the control as the point of reference for determining where to position the new controls. All new controls above and to the left of the stc32 control are positioned the same amount above and to the left of the controls in the default dialog box.

New controls below and to the right of the stc32 control are positioned below and to the right of the default controls.

In general, each new control is positioned so that it has the same position relative to the default controls as it had to the stc32 control. To make room for these new controls, the system adds space to the left, right, bottom, and top of the default dialog box as needed. The system requires the hook procedure to process all messages intended for the custom dialog box and therefore sends the same window messages to the hook procedure as to any other dialog box procedure.

Note the letter that corresponds to the item you want to delete from the list and remember it. To delete an item, right-click on the name for that item and select Delete. A warning dialog box displays to be sure you want to delete the value. It is alright to delete these values. However, be careful when deleting values and keys in the registry.

Click Yes to continue. Now, you must remove the letter for the item you deleted from the MRU list. Double-click the MRUList value. Delete the letter that corresponded with the item you deleted from the string of letters in the Value data edit box. Click OK. There are a couple of methods for disabling the Run dialog box history list.

If you want to preserve the list, in case you want to enable the history again later, use the registry method described in this section. Later in this article, we show you an easier method for disabling the history list.

However, the list of commands in the history will be lost. To disable the Run dialog box history using the registry, open the Registry Editor as described earlier in this article. Navigate, again, to the following key. You are returned to the Permissions dialog box.

Notice that all the values including the MRUList value are gone from the list on the right side of the Registry Editor window. They are not actually gone, but hidden. Close the Registry Editor and open the Run dialog box. Notice that the Open drop-down list that usually contains the history of commands entered is now empty. When you enter commands, they will not be kept in the history list.

The list will remain empty. If you want to restore the history list on the Run dialog box, open the Registry Editor again and navigate to the same key mentioned earlier. Close the dialog box. Now, we will show you the easier way of deleting and disabling the Run dialog box history.



0コメント

  • 1000 / 1000