I am developing an custom FileBrowserContentProvider for the Image Manager dialog of RadEditor and I encounterd some problems :
I am using version 2008.1.415.20 of the RadControls for ASPNET AJAX Q1 2008 and IE6
- For most build in skins the "Image Manager" button in the Image Manager dialog is not placed correctly.
- When selecting the "Image Properties" dialog in RadEditor, the OK and Cancel buttons are not displayed in the Image Properties window.
- When I use a my custom FileBrowserContentProvider and open the "Image Editor" from the "Image Manager" dialog I have the following problems :
- Clicking "Save" in the "Image Editor" gives a message box with "Object reference not set to an instance of an object." when using a custom FileBrowserContentProvider. When using the standard provider all works well.
- At first the image is displayed correctly in the "Image Editor", however after making some modifications and clicking "Restore Image", only an empty image placeholder is shown. One has to right click on the placeholder and select "Show Image" in order to display the image itself.
All of these problems are also present in the demo's on your site (e.g. http://www.telerik.com/DEMOS/ASPNET/Prometheus/Editor/Examples/DBFileBrowserContentProvider/DefaultCS.aspx)
Do you have a sollution or work around for these problems?
Kind regards
Igor De Rycke
7 Answers, 1 is accepted
0
Hi Igor,
Straight to your questions:
Sincerely,
George
the Telerik team
Straight to your questions:
- For most build in skins the "Image Manager" button in the Image Manager dialog is not placed correctly:
Could you please clarify in which skins this problem is observed and along with this please send us screenshots?
- When selecting the "Image Properties" dialog in RadEditor, the OK and Cancel buttons are not displayed in the Image Properties window:
This problem will be fixed in the upcoming SP1 release.
- Regarding the Image Editor and custom FIleBrowserContentProvider problem:
This problem will be fixed in the upcoming SP1 release as well.
Sincerely,
George
the Telerik team
.
Instantly find answers to your questions at the new Telerik Support Center
Instantly find answers to your questions at the new Telerik Support Center
0
Igor
Top achievements
Rank 1
answered on 13 May 2008, 11:06 AM
Dear Telerik Support team,
Thanks for your response to my questions.
Included is a word document with screenshots of the RadEditor skins for which the Image Manager gives incorrect results. Some are minor (like inconsistend "look and feel") some are major (like missing buttons).
I have another remark regarding writing a custom FileBrowserContentProvider (e.g. for the Image Manager) :
When you insert an image in a path using the "Upload" screen, after uploading the file, the Image Manager calls the ResolveRootDirectoryAsTree function of the custom FileBrowserContentProvider for all root paths and not the ResolveDirectory function for the path to which the file was added !
This means that when, in order to speed up the process, you only load the direct decendants (files and folders) of the root pahts in the ResolveRootDirectoryAsTree function, the added file will not be seen in the ImageManager dialog. You actually have to recursively load the complete directory tree in the ResolveRootDirectoryAsTree. This is in contrast with what you say in the help file :
"The ContentProvider revolves around the idea of Files and Directories - these being two separate, slightly different objects. When a request comes for a particular node (if no node is specified, the root node is assumed), a hierarchical tree is generated containing information only for the direct descendents (files and folders) of the node. This "load-on-demand" AJAX based approach allows for small footprint and response time."
When you would in stead call ResolveDirectory for the path to which the file was added this would work fine. Actually when you click the delete button in the ImageManager this works fine : after delering the file ResolveDirectory is called and not ResolveRootDirectoryAsTree.
The same "problem" applies when you click the Refresh button in ImageManager : ResolveRootDirectoryAsTree is called and not ResolveDirectory with the current path. This implies that the root directory is refreshed and not the one which is currently selected, which is also not giving the expected result when you only load the direct decendants (files and folders).
Is there a way not having to recursively load the complete directory tree in the ResolveRootDirectoryAsTree function and still have the correct directory contents are uploading a file to a path or refreshing a directory ?
Kind regards,
Thanks for your response to my questions.
Included is a word document with screenshots of the RadEditor skins for which the Image Manager gives incorrect results. Some are minor (like inconsistend "look and feel") some are major (like missing buttons).
I have another remark regarding writing a custom FileBrowserContentProvider (e.g. for the Image Manager) :
When you insert an image in a path using the "Upload" screen, after uploading the file, the Image Manager calls the ResolveRootDirectoryAsTree function of the custom FileBrowserContentProvider for all root paths and not the ResolveDirectory function for the path to which the file was added !
This means that when, in order to speed up the process, you only load the direct decendants (files and folders) of the root pahts in the ResolveRootDirectoryAsTree function, the added file will not be seen in the ImageManager dialog. You actually have to recursively load the complete directory tree in the ResolveRootDirectoryAsTree. This is in contrast with what you say in the help file :
"The ContentProvider revolves around the idea of Files and Directories - these being two separate, slightly different objects. When a request comes for a particular node (if no node is specified, the root node is assumed), a hierarchical tree is generated containing information only for the direct descendents (files and folders) of the node. This "load-on-demand" AJAX based approach allows for small footprint and response time."
When you would in stead call ResolveDirectory for the path to which the file was added this would work fine. Actually when you click the delete button in the ImageManager this works fine : after delering the file ResolveDirectory is called and not ResolveRootDirectoryAsTree.
The same "problem" applies when you click the Refresh button in ImageManager : ResolveRootDirectoryAsTree is called and not ResolveDirectory with the current path. This implies that the root directory is refreshed and not the one which is currently selected, which is also not giving the expected result when you only load the direct decendants (files and folders).
Is there a way not having to recursively load the complete directory tree in the ResolveRootDirectoryAsTree function and still have the correct directory contents are uploading a file to a path or refreshing a directory ?
Kind regards,
0
Hi Igor,
Thank you so much for your detailed RadEditor bug report. We will make heavy use of it in the further improvement of that particular control.
As a notice of gratitude, I've added 1000 Telerik points in your account.
All the best,
Martin Ivanov
the Telerik team
Thank you so much for your detailed RadEditor bug report. We will make heavy use of it in the further improvement of that particular control.
As a notice of gratitude, I've added 1000 Telerik points in your account.
All the best,
Martin Ivanov
the Telerik team
.
Instantly find answers to your questions at the new Telerik Support Center
Instantly find answers to your questions at the new Telerik Support Center
0
Luc Pettett
Top achievements
Rank 1
answered on 05 Jun 2008, 12:31 PM
Hello Telerik team,
We are also facing these issues which Igor identified. The most obvious problem in IE 6 is in the upload screen. The 'Upload' and 'Cancel' buttons are missing! Also back in the Main page for the 'Image Manager' the 'Image Editor' button is in the wrong location - it is floating above the file browser.
We are on a tight deadline (just 2 weeks left) and IE 6 support is one of our requirements so I would love to see a fix soon. Do you have any idea as to when we can expect to see SP1?
Looking forward to hearing from you!
Luc
We are also facing these issues which Igor identified. The most obvious problem in IE 6 is in the upload screen. The 'Upload' and 'Cancel' buttons are missing! Also back in the Main page for the 'Image Manager' the 'Image Editor' button is in the wrong location - it is floating above the file browser.
We are on a tight deadline (just 2 weeks left) and IE 6 support is one of our requirements so I would love to see a fix soon. Do you have any idea as to when we can expect to see SP1?
Looking forward to hearing from you!
Luc
0
Hi Luc Pettett,
These issues will be fixed with the upcoming SP2 in about 10 days.
All the best,
Martin Ivanov
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
These issues will be fixed with the upcoming SP2 in about 10 days.
All the best,
Martin Ivanov
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Luc Pettett
Top achievements
Rank 1
answered on 25 Jun 2008, 12:00 PM
Any news as to when we should expect SP2? I'm looking forward to seeing it.
Sorry to be pushy but it's been 10 days longer than your predicted date and we are getting close to our deadlines.
Luc
Sorry to be pushy but it's been 10 days longer than your predicted date and we are getting close to our deadlines.
Luc
0
Hello Luc Pettett,
RadControls for ASP.NET AJAX was released about a week ago on 19th of June. You can download the files from the downloads section of your Client.net account.
Kind regards,
Georgi Tunev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
RadControls for ASP.NET AJAX was released about a week ago on 19th of June. You can download the files from the downloads section of your Client.net account.
Kind regards,
Georgi Tunev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center