A couple of strange issues I just can't get sorted out:
1) I use RadWindow forms for data-editing all over the place, and my MasterPage for the form contains a RadSplitter with a top pane for the form and the buttom pane for the commands ("Insert", "Update", etc). If I put a RadFileExplorer in the top pane then:
- With width=100% - the border around the control is correct, but the grid extends beyond the border of the control width-wise and the addressbox does not go to 100%
- With width=640px - the border and the addressbox are correct, but the grid still extends beyond the border of the control width-wise
- With height=100% - the border of the control looks like it's about 100px high, and both the treeview and the grid extend beyond the border of the control height-wise
- With height=340px - the border shows the correct height, but both the tree and the grid still extend beyond their restrictions
My work-around so far has been to create a form that uses a different MasterPage (in fact, no MasterPage) that mimics the design of all my other forms, but this introduces a longer-term problem in maintainability. In the short-term though, problem #2 is far more urgent.
2) I set all FileBrowsers properties programatically - both those that are used by the built-in dialogs of the RadEditor as well as any RadFileExplorers that I use. In setting up the configuration for either one, they pass through the same set of functions on the server for specifiying ViewPaths, UploadPaths, DeletePaths, etc. The problem that I'm seeing is that a user can open a DocumentManager from the toolbar of an Editor and they have the expected read/write permissions to root-level folders and sub-folders. However, when that same user visits my form with a RadFileExplorer, which has the exact same paths, they cannot write to any sub-folder, however they can write to the root folder; and they can read all folders just like in the DocumentManager.
My work-around is that I have to tell my users who are managing their documents that they have to go to a completely unrelated area of the site so that they can use the RadEditor's Document Manager for uploading, then return back to their initial page to select that file for use. I'm hoping that's enough information for the Telerik Guru's to test out because the project is fairly huge and creating a small test project at this point is rather cumbersome. Thanks,
Shaun.