Wn7? I think few people will understand this function. The library is a bit like a large folder, but it is a little different from the folder. It is relatively powerful. Therefore, today I will give you a comprehensive introduction to the library in win7.
First, the similarities and differences with ordinary folders
From the above interface, we can see that the library seems to be similar to the traditional folder. Indeed, from a certain perspective, libraries and folders do have many similarities. As with folders, you can also include a variety of sub-libraries and files in the library. But it's essentially different from folders. Files or subfolders saved in a folder are stored in the same place. The files stored in the library can come from all over the world. For example, it can be from an associated file on the user's computer or from a file on a removable disk. Although this difference is small, it is the most essential difference between traditional folders and libraries.
In fact, the management of the library is closer to the shortcut. The user can use the specific storage location of the file or folder. Manage them all by linking them to a library. In this case, all the files that the user needs to know can be seen in the library (as long as the user adds these files or folders to the library in advance). In other words, the objects in the library are a snapshot of various folders and files. The library does not actually store files, providing a faster management method. For example, the user has some working documents mainly in the D disk and the mobile hard disk on the computer. For the convenience of future work, the user can place the files in the D drive and the mobile hard disk into the library. When you need to use it, just open the library directly (provided that the mobile hard disk is connected to the user host), and you do not need to locate the mobile hard disk.
Second, after the deletion can not be re-joined is a loophole
As shown above, the author first added a folder WinXP on the hard disk to the library. The way to add a folder to the library is very simple, just select the target folder, then click the button, click “include to the library” However, when I was testing, I found an organ problem. If you add this folder to the library, then delete the WinXP folder in the library. Then re-add this folder to the library. However, at this time the system prompts "Already WinXP is included in the library", and this folder will not be displayed in the library. However, the WinXP file in the library has actually been deleted.
Then, if the WinXP file exists in the library, and then add this file to the library, you can create it successfully. Only the name of the library will change to WinXP(2). It can be seen that this error is not caused by repeatedly adding a folder to the library. Because according to the test, the system allows the same folder to be added to the library multiple times. The reason for this error may be that there is a problem with the display in the library. The folders that have been added to the library cannot be displayed properly due to some special operations (such as deleting and then adding).
Third, delete the impact of the actual folder on the library file
As shown above, the author has a WinXP folder in the hard disk, and then this folder is included in the library. Now I will delete the WinXP folder on this hard disk. At this point, what is the impact on the WinXP folder in the library? First, the author double-click to open the WinXP folder in the library, you can still open. It can be seen that there are some differences between the management of library files and the management of shortcuts. If it is a shortcut, when the user deletes the original file, the shortcut will not open, and the user will confirm the accuracy of the path. In the library, you can still open the library files whose original folders have been deleted. There is nothing in the library that was originally saved. The most amazing thing is that although the original folder back is deleted, you can add files to the WinXP library in the library file, such as creating a new folder. Then, where is the newly added content library stored? At this time, the author opened the location of the original WinXP folder and found that a new WinXP file was created in the old place. This is automatically created by the operating system, which saves our newly created folder in the library.
Fourth, the shared files on the network can not be added to the library
Then the shared folder on the network can also be added to the library for management? I consulted the relevant technical information. According to Microsoft's official documentation, shared files on the network can be added to the library, but when the library is opened, the speed will be slower due to network reasons. However, after the author's test, it seems to be unworkable. For example, I have created a new folder on other hosts and set it to share. Then connect this file to the Windows 7 host. I want to add this shared file to the library, but the operating system prompts the error message "This folder cannot be included because it is a shared file instead of an index".
But the author still does not give up, just map this shared file to a network drive. Then create a new folder in this network drive “ new folder & rdquo;. Unfortunately, it is still not possible to add this folder to the library. The author dragged the newly created folder into the library by dragging, and still displays the above error message: This folder cannot be included because it is a shared file instead of an index. After several tests, the author finally died. In the version currently available in Windows 7, it is not yet possible to add shared folders on the network to the library.
Five, the library and the actual folder can not be equivalent
If you add a WinXP folder to the library first, then there will be another font in the library called WinXP. Note that the font library WinXP in the library is not the same as the actual stored folder WinXP. Some operations on the font library WinXP will not affect the actual WinXP folder. If you can in the library, some folders are packaged into the library. If the font WinXP is selected, then right click on the property. In the dialog that opens we can see a button that contains the folder & rdquo;. After clicking this button, we can add some existing folders in the current hard disk to this WinXP library. However, although some folders are added to the library in the font WinXP library, this has no effect on the actual stored folder WinXP. In other words, it is not because the user adds a folder to the library Winxp, but also copies the contents of that folder to the WinXP folder. It can be seen that adding a folder to the library, although the name is the same by default, but the two are not the same thing. One is the actual stored folder and the other is the name of the library. The two are irrelevant.
Sixth, sharing in the library
In the library, you can perform some maintenance and operation on the files contained in the library. For example, you can share files in a library. However, it seems that there are still a lot of troubles in its real implementation. For example, in the WinXP library, I created a new folder "Test shared folder". Then select this folder, right click and select Share. However, there is less content available for users to choose from here, only a few options such as “Nobody”, HomegroupRead, HomegroupRead/Write, and specific personnel. There are some English words in these options, and there may be certain files in the translation. The author selects “specific personnel" put this "test shared folder" setting a share. However, in the library, there is no shared flag displayed on this "test shared folder". However, the author has checked the original folder, and then the folder has a shared logo. It can be seen that the sharing settings of the files in the library can be reflected in the original folder. Unfortunately, the shared logo is not displayed in the folders already shared in the library, which is more or less regrettable. Later, after testing, it was found to be a display problem. The shared icon will only be displayed if the library needs to be closed and then reopened. If the share is cancelled, the library must be reopened to cancel the icon. But in its corresponding folder, you can see the effect immediately. This is easy to cause misunderstanding. To this end, I suggest that Microsoft, although not a big thing in the display of icons in this regard, but has great guiding significance for users. In terms of display, it is best to be as timely as a normal folder. Instead of updating the icon the next time you reopen it. In addition, if you want to make complex sharing settings, it is best to open the properties dialog box after setting the folder in the library. Here you can make detailed settings for some of the permissions control. This is much more detailed than setting the Share dialog directly.
This tutorial introduces the knowledge of win7 library from beginning to end. Everyone doesn't know what it feels like? I don't think I have known it before, but it doesn't matter. I can use it after reading it today. I hope it is right. Everyone is useful.
Note: "Library" is a somewhat virtual concept. Storing files (clips) into the library does not actually copy the files to the "library" location, but in the "library" function. In the "register" & rdquo; the location of those files (clip) to be managed by Windows, therefore, the content stored in the library, in addition to their self-occupied disk space, almost no additional disk space, and delete the library And its content does not affect those real files.