In localizing your demo code for a RichTextBox I noticed some size mode-related inconsistencies in icon placements in the various sorts of buttons:
In Size=large, generally the icon appears above the button text. In the split button the icon is centered over and partially obscures the text. Unacceptable!
In Size=medium, generally the icon appears to the left of the text. In the Split button it appears below the text. Either is fine but should be consistent.
Also, when Size=medium and icon beside text, in all buttons I would like to see more spacing between the icon and the text; there seems to be virtually none.
With a picture of original size like this : width 2 800 and Height 1376. On the screen the picture is around 470 by 230. If I go to the Image Editor, it shows me the picture size itself but not the area size used by the picture. It is a good thing to have the original picture's dimension but we work with the dimension used in the document. So, could you do something to resize the picture used in the document.
In my samples, you'll see my picture in a document (ie1), what I see when I go in the Image Editor (ie2) and, when I go to the Resize section (ie3). Suggestion, put the original image's dimension on the top of the right corner in the resize section. The width and Height should show the dimension in the document.
Thanks a lot,
Annotation Ranges where SkipPositionBefore is set to false on the AnnotationRangeEnd cause cursor jumps when deleting content to the right of the Annotation Range. Steps to reproduce: 1. Open a job with Annotation Ranges where SkipPositionBefore is set to false on the AnnotationRangeEnd (I used the Document Protection sample in the demo app) 2. Move your cursor to the end of the range. 3. Hit the delete key Expected: The cursor remains at the end of the AnnotationRange and content to the right is deleted. Actual: Content to the right is deleted but eventually the cursor will jump to the right by one position and end up outside the Annotation Range.
After further discussion within the XAML team and more research, we decided that introducing a similar property does not align with the current idea and model of RadRichTextBox. Thus, we are declining this item.
The invalid values should be skipped and the document should be successfully imported.
When adding a comment it should be marked as created from the current user. Layer with tool tips should be added to show this information. Also comment balloons should contain it.
We need to support uneditable areas in the document flow. The closes analog in HTML is <div editableContent=false>...</div>.
MS-Word allows a user to toggle the markup and edit the document as final when track changes are enabled. This feature request is allowing something similar in RadRichTextBox.
Add support for Widow/Orphan control property of Paragraph. In Open XML specification, this is named "widowControl (Allow First/Last Line to Display on a Separate Page)". The problem is that as this property is not supported, RadRichTextBox acts as it's 'false' and also doesn't export it, but the default value is actually 'true', which causes layout differences between RadRichTextBox and MS Word.
In Word I can place text where ever I want, when I use textfields. This should also be possible with RadRichTextBox. When exporting to PDF this should result in an extra layer for the textfield.
After you have inserted a new row from the context menu of the RadRichTextBox, it becomes selected and then if you want to add a new row from the context menu again, the option is disabled. You should be able to add a new row, so the insert command must be enabled.
Provide mechanism for selecting an uri from which a dictionary can be downloaded when needed. In this way the client will download only the dictionaries that are in use. If more are needed, they will be downloaded on demand.