From e3f28b9891f9cb8b8b7dfded4fccbf6e9f658d8d Mon Sep 17 00:00:00 2001 From: StenlyGrigorov Date: Tue, 16 Dec 2025 15:23:46 +0200 Subject: [PATCH] Fix missing first character in tips, importants, and cautions --- .../dragdropmanager/dragdroppayloadmanager.md | 2 +- .../howto-draganddrop-within-radgridview.md | 4 ++-- controls/radautocompletebox/events.md | 2 +- .../features/highlightbehavior.md | 2 +- .../radautocompletebox/features/selection.md | 2 +- .../binding-support-overview.md | 2 +- .../populating-with-data/binding-to-object.md | 2 +- .../customizing-boxes-itemtemplate.md | 2 +- .../features/custom-busy-content.md | 2 +- .../features/delayed-display.md | 2 +- .../features/enabling-the-indicator.md | 2 +- .../features/progress-determination.md | 2 +- .../features/report-progress-value.md | 2 +- .../integrate-with-services-and-radwindow.md | 2 +- .../how-to/modify-default-placement.md | 4 ++-- .../styles-and-templates/overview.md | 2 +- .../setting-the-overlay-style.md | 4 ++-- .../styling-radbusyindicator.md | 4 ++-- .../styling-the-radprogressbar.md | 6 ++--- .../radbuttons/features/button-extensions.md | 4 ++-- .../features/annotations/custom-gridline.md | 6 ++--- .../features/annotations/custom-line.md | 2 +- .../features/annotations/marked-zone.md | 10 ++++----- .../features/axes/logarithmic-scale.md | 2 +- .../features/axes/striplines-and-gridlines.md | 2 +- controls/radchart/features/axes/ticks.md | 2 +- controls/radchart/features/chart-export.md | 2 +- controls/radchart/features/chart-legend.md | 10 ++++----- .../features/drill-down/hierarchical-view.md | 2 +- .../drill-down/in-multiple-chart-areas.md | 4 ++-- controls/radchart/features/export-to-pdf.md | 2 +- controls/radchart/features/filtering.md | 2 +- .../features/grouping/and-aggregation.md | 2 +- .../features/grouping/flattened-series.md | 2 +- .../features/interactivity-effects.md | 4 ++-- controls/radchart/features/negative-values.md | 2 +- controls/radchart/features/sampling.md | 4 ++-- controls/radchart/features/sorting.md | 2 +- controls/radchart/features/tooltips.md | 4 ++-- .../features/zooming-and-scrolling.md | 4 ++-- .../create-data-bound-chart.md | 2 +- .../how-to/add-annotations-in-chart-legend.md | 2 +- ...tapointmember-to-a-depenndency-property.md | 2 +- ...the-gridviews-compositefilterdescriptor.md | 2 +- .../binding-to-adonet-service.md | 2 +- .../populating-with-data/binding-to-wcf.md | 4 ++-- ...data-binding-with-manual-series-mapping.md | 2 +- .../styling-and-appearance-overview.md | 4 ++-- ...ing-and-appearance-styling-chart-legend.md | 4 ++-- ...ing-and-appearance-styling-chart-series.md | 10 ++++----- ...ling-and-appearance-styling-chart-title.md | 2 +- ...ling-and-appearance-styling-item-labels.md | 4 ++-- ...-and-appearance-styling-no-data-control.md | 2 +- ...tyling-and-appearance-styling-plot-area.md | 2 +- ...ling-and-appearance-styling-strip-lines.md | 2 +- .../styling-and-apearance-styling-gridline.md | 4 ++-- ...-and-appearance-styling-axis-item-label.md | 4 ++-- ...tyling-and-appearance-styling-axis-line.md | 6 ++--- ...-and-appearance-styling-axis-minor-tick.md | 6 ++--- ...tyling-and-appearance-styling-axis-tick.md | 8 +++---- ...yling-and-appearance-styling-axis-title.md | 6 ++--- ...tyling-and-appearance-styling-stripline.md | 4 ++-- .../templating-point-marks.md | 6 ++--- .../customizing-cartesianchart-series.md | 2 +- .../customizing-polarchart-series.md | 4 ++-- controls/radcombobox/features/edit-modes.md | 6 ++--- controls/radcombobox/features/filtering.md | 4 ++-- .../radcombobox/features/keyboard-support.md | 2 +- .../radcombobox/howto/create-a-watermark.md | 4 ++-- .../howto/open-dropdown-get-focus.md | 2 +- .../radcombobox/howto/set-character-casing.md | 2 +- .../howto/set-max-length-input-area.md | 2 +- controls/radcombobox/howto/virtualization.md | 2 +- controls/radcontextmenu/events/overview.md | 2 +- .../features/opening-on-specific-event.md | 2 +- controls/radcontextmenu/features/placement.md | 2 +- .../features/working-with-radcontext-menu.md | 4 ++-- .../binding-to-dynamic-data.md | 2 +- .../data-binding-support-overview.md | 4 ++-- .../using-static-items.md | 4 ++-- .../styles-and-templates/overview.md | 2 +- .../styling-the-context-menu.md | 8 +++---- .../template-structure.md | 2 +- .../features/add-edit-delete-buttons.md | 2 +- controls/raddatapager/localization.md | 2 +- controls/raddatetimepicker/events.md | 2 +- .../raddatetimepicker/features/date-items.md | 4 ++-- .../features/militaryparsing.md | 2 +- .../features/preview-tooltip.md | 4 ++-- .../raddatetimepicker/features/watermark.md | 2 +- .../how-to/implement-custom-parsing.md | 4 ++-- .../how-to/open-dropdown-get-focus.md | 2 +- .../how-to/select-only-picker.md | 4 ++-- controls/raddatetimepicker/localization.md | 2 +- .../styling-clock-view.md | 2 +- .../styles-and-templates/styling-overview.md | 2 +- .../styling-raddatetimepicker.md | 4 ++-- .../raddesktopalert/show-on-current-screen.md | 2 +- .../settingspane/settingspane_overview.md | 2 +- controls/raddiagram/features/services.md | 4 ++-- controls/raddocking/events/overview.md | 4 ++-- controls/raddocking/features/document-host.md | 2 +- controls/raddocking/features/drag-and-drop.md | 6 ++--- controls/raddocking/features/nesteddocking.md | 2 +- controls/raddocking/features/pane-groups.md | 6 ++--- .../features/panes/docked-floating-panes.md | 8 +++---- .../raddocking/features/panes/panes-menu.md | 2 +- .../features/panes/pinned-unpinned-panes.md | 2 +- .../features/panes/raddocumentpane.md | 2 +- .../raddocking/features/retain-pane-size.md | 2 +- .../features/save-load-layout/overview.md | 2 +- .../save-load-the-content-of-the-panes.md | 2 +- .../raddocking/features/split-container.md | 8 +++---- .../getting-started/getting-started2.md | 2 +- .../managing-docking-dynamically.md | 6 ++--- .../how-to/add-buttons-to-the-pane-headers.md | 2 +- .../add-menu-items-to-the-radpanes-menu.md | 2 +- .../how-to/implement-conditional-docking.md | 2 +- controls/raddocking/localization.md | 2 +- .../styling-the-raddocumentpane.md | 2 +- .../radexpressioneditor/getting-started.md | 2 +- controls/radexpressioneditor/localization.md | 2 +- .../features/columns/cell-template.md | 2 +- .../features/columns/highlight-template.md | 2 +- .../features/columns/selection-template.md | 2 +- .../styles-and-templates/setting-theme.md | 2 +- .../indicators/bar-indicators-basics.md | 2 +- .../radgauge/features/indicators/marker.md | 2 +- .../celltemplate-and-celledittemplate.md | 2 +- .../radgridview/columns/column-headers.md | 2 +- .../columns/columntypes/checkbox-column.md | 2 +- .../columntypes/column-types-basic-column.md | 2 +- .../columns/columntypes/image-column.md | 2 +- .../how-to/create-custom-column-editor.md | 2 +- .../columns/how-to/read-only-rows-cells.md | 2 +- .../how-to/set-sortingstate-on-column.md | 2 +- .../columns/how-to/wrap-text-column-header.md | 2 +- .../commands/keyboardcommandprovider.md | 4 ++-- controls/radgridview/events/edit.md | 4 ++-- controls/radgridview/events/export-events.md | 2 +- ...entexporting-elementexported-todocument.md | 2 +- .../elementexporting-elementexported.md | 2 +- .../events/initializing-excelml-styles.md | 2 +- .../radgridview/export/excel/export-xlsx.md | 2 +- .../export/how-to/export-string.md | 2 +- controls/radgridview/export/pdf/export-pdf.md | 2 +- controls/radgridview/features/merged-cells.md | 2 +- .../features/overview-filtering.md | 2 +- .../radgridview/features/overview-grouping.md | 2 +- .../features/overview-keyboard-support.md | 2 +- .../features/overview-lightweight-template.md | 4 ++-- .../radgridview/features/overview-sorting.md | 4 ++-- controls/radgridview/features/pinned-rows.md | 2 +- .../features/search-as-you-type.md | 2 +- controls/radgridview/filtering/basic.md | 2 +- .../faq/dataformatstring-and-filtering.md | 2 +- .../filtering/faq/datetime-filtering.md | 4 ++-- ...disable-filtering-for-a-specific-column.md | 2 +- .../radgridview/filtering/programmatic.md | 4 ++-- controls/radgridview/grouping/aggregates.md | 2 +- .../radgridview/grouping/groupingmodes.md | 2 +- .../grouping/modify-grouptemplates.md | 2 +- .../grouping/modifying-group-panel.md | 2 +- .../basic-hierarchies.md | 2 +- .../access-filtered-and-sorted-items.md | 2 +- controls/radgridview/how-to/create-tooltip.md | 2 +- .../how-to/customize-ui-programmatically.md | 2 +- ...hide-columns-outside-of-the-radgridview.md | 2 +- .../radgridview/localization/localization2.md | 2 +- controls/radgridview/overview2.md | 2 +- .../binding-to-dataset.md | 2 +- .../populating-with-data/in-memory-date.md | 2 +- .../loading-data-from-adonet-services.md | 2 +- .../loading-data-from-wcf-services.md | 6 ++--- .../loading-data-from-xml.md | 2 +- .../row-details/external-row-details.md | 2 +- controls/radgridview/row-details/overview.md | 6 ++--- .../radgridview/row-details/programming.md | 4 ++-- .../row-details/templateselector.md | 2 +- .../selection/how-to/via-checkbox.md | 4 ++-- .../selection/multiple-selection.md | 2 +- .../selection/programmatic-selection.md | 4 ++-- .../group-footer-row-styleselector.md | 2 +- .../group-row-style-selector.md | 2 +- .../groupfootercell-styleselector.md | 2 +- .../merged-cells-style-selector.md | 2 +- .../rowdetails-styleselector.md | 2 +- .../style-selectors/rowstyleselector.md | 2 +- .../modifying-default-styles.md | 8 +++---- .../stylines-and-templates-overview.md | 4 ++-- .../styles-and-templates/styling-filterrow.md | 2 +- .../styles-and-templates/styling-group-row.md | 2 +- .../styling-merged-column-headers.md | 2 +- .../styling-mergedcell.md | 4 ++-- .../cell-template-selector.md | 2 +- .../template-selectors/overview.md | 2 +- .../troubleshooting/cannot-insert-new-row.md | 2 +- .../first-row-always-selected.md | 2 +- .../reevaluation-dataoperations.md | 2 +- .../how-to/howto-custom-tool.md | 6 ++--- .../radimageeditor/tools/howto-use-crop.md | 2 +- controls/radlistbox/features/autocomplete.md | 4 ++-- .../binding-support-overview.md | 4 ++-- .../populating-with-data/binding-to-object.md | 2 +- .../features/providers/uriimageprovider.md | 2 +- .../heatures-clustering.md | 2 +- controls/radmenu/features/checkable-items.md | 6 ++--- controls/radmenu/features/click-modes.md | 2 +- controls/radmenu/features/commands.md | 2 +- controls/radmenu/features/icons.md | 4 ++-- ...p-checkable-menu-items-into-radio-group.md | 4 ++-- .../data-binding-support-overview.md | 4 ++-- .../template-and-style-selectors.md | 2 +- .../styles-and-templates/visual-states.md | 2 +- controls/radnumericupdown/getting-started.md | 2 +- controls/radoutlookbar/localization.md | 2 +- controls/radpdfviewer/getting-started.md | 4 ++-- controls/radpdfviewer/localization.md | 2 +- .../radpdfviewer/ui/document-presenters.md | 2 +- controls/radpdfviewer/ui/find-dialog.md | 2 +- .../ui/switching-icons-at-runtime.md | 2 +- controls/radpivotgrid/events/overview.md | 4 ++-- controls/radpivotgrid/features/export.md | 2 +- .../data-annotations.md | 2 +- .../localdatasourceprovider/filtering.md | 4 ++-- .../local-calc-fields.md | 2 +- .../localdatasourceprovider/sorting.md | 2 +- .../features/olap-providers/filtering-olap.md | 4 ++-- .../features/olap-providers/sorting-olap.md | 2 +- .../queryable-calc-fields.md | 2 +- .../queryable-group-filtering.md | 4 ++-- .../queryable-sorting.md | 2 +- .../features/radchartview-integration.md | 2 +- .../getting-started/getting-started.md | 2 +- .../started-understanding-pivot.md | 2 +- .../howto-set-http-access-to-sqlserver.md | 2 +- .../populating-with-data/data-adomd.md | 2 +- .../populating-with-data/data-queryable.md | 4 ++-- .../populating-with-data/data-xmla.md | 4 ++-- .../styles-and-templates/quickstyles.md | 4 ++-- .../features/collectioneditor.md | 2 +- .../features/data-annotations.md | 2 +- .../radpropertygrid/features/edit-modes.md | 2 +- controls/radpropertygrid/features/grouping.md | 4 ++-- .../features/layout-rendering-modes.md | 2 +- .../features/readonlyeditorstate.md | 2 +- .../radpropertygrid/features/scrolling.md | 8 +++---- .../radpropertygrid/features/selection.md | 4 ++-- .../features/virtualization.md | 4 ++-- .../localization/localization.md | 2 +- .../group-style-selectors.md | 2 +- .../styles-and-templates/overview.md | 2 +- .../templates-structure.md | 2 +- controls/radradialmenu/commands/radialmenu.md | 2 +- .../radradialmenu/features/contextmenu.md | 2 +- .../how-to/howto-customize-tooltip.md | 2 +- .../styles-and-templates/setting-theme.md | 2 +- .../styling-groupchrome.md | 2 +- .../document-elements/table/table-ui.md | 2 +- .../features-keyboard-support.md | 2 +- .../features-ui-virtualization.md | 2 +- .../features/clipboard-support.md | 4 ++-- .../radrichtextbox/features/code-block.md | 4 ++-- controls/radrichtextbox/features/commands.md | 6 ++--- controls/radrichtextbox/features/comments.md | 2 +- .../radrichtextbox/features/format-painter.md | 2 +- .../radrichtextbox/features/line-numbering.md | 2 +- .../features/read-only-ranges.md | 4 ++-- controls/radrichtextbox/features/search.md | 2 +- .../radrichtextbox/features/spellcheck.md | 2 +- .../features-formatting-api.md | 4 ++-- .../how-to/switching-icons-at-runtime.md | 2 +- .../how-to/update-current-color-in-ui.md | 2 +- .../import-export/docx/docxformatprovider.md | 2 +- .../import-export/features-data-providers.md | 8 +++---- .../import-export/features-import-export.md | 2 +- .../plain-text/txt-txtformatprovider.md | 2 +- .../import-export/rtf/rtfformatprovider.md | 2 +- .../applying-styles.md | 4 ++-- .../features-radrichtextboxribbonui.md | 2 +- ...pplying-formatting-table-styles-gallery.md | 2 +- controls/radscheduleview/events/overview.md | 4 ++-- .../appointments/custom-appointment.md | 4 ++-- .../features/appointments/snapappointments.md | 2 +- .../features/custom-dialogs.md | 4 ++-- .../features/inline-editing.md | 4 ++-- ...ecurrences-draggingrecurrentappointment.md | 2 +- .../recurrences-recurrencepattern.md | 22 +++++++++---------- .../recurrence/recurrences-recurrencerule.md | 2 +- .../viewdefinitions/configure-visiblerange.md | 2 +- .../radscheduleview/howto/update-resources.md | 2 +- .../styles-and-templates/appointment-style.md | 6 ++--- .../customizing-dragvisual.md | 2 +- .../styling-timeruleritems.md | 2 +- .../templating-timeruleritems.md | 2 +- .../templating-tooltip.md | 2 +- .../radslider/features/multiple-thumbs.md | 2 +- .../features/spellchecking-gridcell.md | 2 +- controls/radspellchecker/getting-started.md | 2 +- .../features/ui-data-validation.md | 2 +- .../features/ui-hidden-rows-columns.md | 4 ++-- .../ui-worksheet-editor-context-menu.md | 4 ++-- .../howto/switching-icons-at-runtime.md | 2 +- controls/radspreadsheet/localization.md | 2 +- controls/radspreadsheet/model.md | 2 +- controls/radspreadsheet/overview.md | 2 +- controls/radspreadsheet/ui-virtualization.md | 2 +- .../radtabbedwindow/styles-and-templates.md | 6 ++--- .../features/keyboard-support.md | 2 +- .../getting-started/populating-with-tabs.md | 2 +- .../populating-add-remove-tabs.md | 2 +- controls/radtilelist/features/selection.md | 2 +- .../features/intervals-formatters.md | 2 +- .../features/radtransition-data-binding.md | 2 +- ...ition-integration-with-content-controls.md | 4 ++-- .../features/radtransition-transitions.md | 4 ++-- ...ition-working-with-radtransitioncontrol.md | 8 +++---- ...radtransition-create-custom-transitions.md | 2 +- .../radtransition-getting-started.md | 4 ++-- .../radtreelistview/features/data-binding.md | 4 ++-- .../radtreelistview/features/managing-data.md | 2 +- .../radtreelistview/features/row-details.md | 2 +- .../radtreelistview/how-to/scrollintoview.md | 2 +- controls/radtreelistview/localization.md | 2 +- controls/radtreelistview/overview.md | 2 +- .../radtreeview/features/lines-support.md | 2 +- controls/radtreeview/localization.md | 2 +- controls/radwindow/features/closing.md | 2 +- .../features/minimizingmaximazing.md | 4 ++-- controls/radwindow/features/moving.md | 2 +- controls/radwindow/features/positioning.md | 4 ++-- controls/radwindow/features/window-header.md | 2 +- .../features/working-with-radwindow.md | 6 ++--- controls/radwindow/getting-started.md | 6 ++--- ...close-the-radwidnow-through-its-content.md | 6 ++--- .../use-keyboard-to-get-user-response.md | 2 +- .../how-to/use-radwindow-as-user-control.md | 2 +- 337 files changed, 497 insertions(+), 497 deletions(-) diff --git a/controls/dragdropmanager/dragdroppayloadmanager.md b/controls/dragdropmanager/dragdroppayloadmanager.md index e85583207d..1e3b20f996 100644 --- a/controls/dragdropmanager/dragdroppayloadmanager.md +++ b/controls/dragdropmanager/dragdroppayloadmanager.md @@ -112,7 +112,7 @@ In the handler method where the payload is generated you will need to attach a D } ``` ->tipThe DataConverter can convert objects from multiple types to multiple types inside its __ConvertTo()__ method. You will need to check if the format is the desired one as well as if the needed data is present. The __GetConvertToFormats()__ method should return a collection of the supported formats to convert to, so the control can accept or prevent the drop when the dragged object cannot be converted to the required format. +>tip The DataConverter can convert objects from multiple types to multiple types inside its __ConvertTo()__ method. You will need to check if the format is the desired one as well as if the needed data is present. The __GetConvertToFormats()__ method should return a collection of the supported formats to convert to, so the control can accept or prevent the drop when the dragged object cannot be converted to the required format. In the __DragInitialize__ handler itself you will need to pass to the DragDropPayloadManager an instance of the converter that will be carried by the payload within the events and used when needed: diff --git a/controls/dragdropmanager/how-to/howto-draganddrop-within-radgridview.md b/controls/dragdropmanager/how-to/howto-draganddrop-within-radgridview.md index a8c5199d5e..f3f1b3b029 100644 --- a/controls/dragdropmanager/how-to/howto-draganddrop-within-radgridview.md +++ b/controls/dragdropmanager/how-to/howto-draganddrop-within-radgridview.md @@ -674,9 +674,9 @@ Finally, you should populate your __RadGridView__ with sample data and attach t End Sub ``` ->tipYou can download a __runnable project__ on the previous example from our online SDK repository [here](https://github.com/telerik/xaml-sdk/tree/master/GridView/DragDropWithLines). +>tip You can download a __runnable project__ on the previous example from our online SDK repository [here](https://github.com/telerik/xaml-sdk/tree/master/GridView/DragDropWithLines). >You can also check the [SDK Samples Browser]({%slug sdk-samples-browser%}) that provides a more convenient approach in exploring and executing the examples in the Telerik XAML SDK repository. ->tipYou can also check the implementation of {% if site.site_name == 'Silverlight' %} [Reorder Rows demo](https://demos.telerik.com/silverlight/#GridView/RowReorder)/[Tree to Grid demo](https://demos.telerik.com/silverlight/#DragAndDrop/TreeToGrid){% endif %}{% if site.site_name == 'WPF' %} __Tree to Grid/Reorder Rows__ [WPF Demos](https://demos.telerik.com/wpf/#DragAndDrop/RowReorder){% endif %}. +>tip You can also check the implementation of {% if site.site_name == 'Silverlight' %} [Reorder Rows demo](https://demos.telerik.com/silverlight/#GridView/RowReorder)/[Tree to Grid demo](https://demos.telerik.com/silverlight/#DragAndDrop/TreeToGrid){% endif %}{% if site.site_name == 'WPF' %} __Tree to Grid/Reorder Rows__ [WPF Demos](https://demos.telerik.com/wpf/#DragAndDrop/RowReorder){% endif %}. diff --git a/controls/radautocompletebox/events.md b/controls/radautocompletebox/events.md index 55ad9babbc..b2fbe30ffa 100644 --- a/controls/radautocompletebox/events.md +++ b/controls/radautocompletebox/events.md @@ -52,4 +52,4 @@ __Example 1: Modify the collection with the found results from the event argumen } ``` ->tipYou can remove and add items from the e.Results collection or sort and filter them. +>tip You can remove and add items from the e.Results collection or sort and filter them. diff --git a/controls/radautocompletebox/features/highlightbehavior.md b/controls/radautocompletebox/features/highlightbehavior.md index d6b7973e13..e133c6c7e0 100644 --- a/controls/radautocompletebox/features/highlightbehavior.md +++ b/controls/radautocompletebox/features/highlightbehavior.md @@ -77,7 +77,7 @@ __Overriding FindHighlightedIndex__ End Function ``` ->tipIf you don't want to highlight any of the filtered items you should return __-1__ in the __FindHighlightedIndex()__ method. +>tip If you don't want to highlight any of the filtered items you should return __-1__ in the __FindHighlightedIndex()__ method. >If the returned index from the __FindHighlightedIndex()__ method goes out of range - no item will be highlighted (the index of the highlighted item will be set to -1). diff --git a/controls/radautocompletebox/features/selection.md b/controls/radautocompletebox/features/selection.md index ebc02aa172..3efda9997f 100644 --- a/controls/radautocompletebox/features/selection.md +++ b/controls/radautocompletebox/features/selection.md @@ -28,7 +28,7 @@ The __SelectedItem__ property corresponds to the item the user has selected when __SelectedItems__ is a collection of items containing all selected items in the control when SelectionMode is set to Multiple. ->importantThe __SelectedItems__ collection will always contain a single item when SelectionMode is set to Single and you change the selected item. When in Multiple selection mode, __SelectedItem__ will be set to the first item added to the selected items that is still included in the selection. +>important The __SelectedItems__ collection will always contain a single item when SelectionMode is set to Single and you change the selected item. When in Multiple selection mode, __SelectedItem__ will be set to the first item added to the selected items that is still included in the selection. **Example 1** demonstrates how to get ahold of the selected items and also determine which item was selected first when in Multiple selection mode. diff --git a/controls/radautocompletebox/populating-with-data/binding-support-overview.md b/controls/radautocompletebox/populating-with-data/binding-support-overview.md index b6df1115d1..7719906807 100644 --- a/controls/radautocompletebox/populating-with-data/binding-support-overview.md +++ b/controls/radautocompletebox/populating-with-data/binding-support-overview.md @@ -20,4 +20,4 @@ Binding to __RadAutoCompleteBox__ involves the following property: To bind the __RadAutoCompleteBox__ to a collection of business objects, you should use its __ItemsSource__ property. If you want the changes to the collection to be automatically reflected to the RadAutoCompleteBox items, the collection should implement the __INotifyCollectionChanged__ interface. There is a build-in collection in {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %}, which implements the __INotifyCollectionChanged__ interface and you could use it without making any effort - this is the generic __ObservableCollection__. However, to get a full benefit from the change notification support, your custom business objects should implement the __INotifyPropertyChanged__ interface. ->tipConsider using __ObservableCollection__ or one of the other existing collection classes like __List__, __Collection__, instead of implementing your own collection. If the scenario requires a custom collection to be implemented, use the __IList__ interface, which provides individual access by index to its items and the best performance. +>tip Consider using __ObservableCollection__ or one of the other existing collection classes like __List__, __Collection__, instead of implementing your own collection. If the scenario requires a custom collection to be implemented, use the __IList__ interface, which provides individual access by index to its items and the best performance. diff --git a/controls/radautocompletebox/populating-with-data/binding-to-object.md b/controls/radautocompletebox/populating-with-data/binding-to-object.md index c3278e9557..6fb9728f10 100644 --- a/controls/radautocompletebox/populating-with-data/binding-to-object.md +++ b/controls/radautocompletebox/populating-with-data/binding-to-object.md @@ -18,7 +18,7 @@ The following example will guide you through the process of binding your RadAuto * [Using DisplayMemberPath and TextSearchPath](#using-displaymemberpath-and-textsearchpath) ->tipBefore proceeding with this tutorial you should get familiar with the [Data Binding]({%slug radautocompletebox-populating-with-data-binding-support-overview%}) support of the RadAutoCompleteBox control. +>tip Before proceeding with this tutorial you should get familiar with the [Data Binding]({%slug radautocompletebox-populating-with-data-binding-support-overview%}) support of the RadAutoCompleteBox control. ## Binding the ItemsSource diff --git a/controls/radautocompletebox/styles-and-templates/customizing-boxes-itemtemplate.md b/controls/radautocompletebox/styles-and-templates/customizing-boxes-itemtemplate.md index 7b1b9cc703..659e56c1e5 100644 --- a/controls/radautocompletebox/styles-and-templates/customizing-boxes-itemtemplate.md +++ b/controls/radautocompletebox/styles-and-templates/customizing-boxes-itemtemplate.md @@ -38,7 +38,7 @@ The __Flag__ property should be of type string and will be bound to the __Source After that you need to create the ViewModel and populate it with some data. ->tipMore detailed information how to bind __RadAutoCompleteBox__ to an object could be found [here]({%slug radautocompletebox-populating-with-data-binding-to-object%}). +>tip More detailed information how to bind __RadAutoCompleteBox__ to an object could be found [here]({%slug radautocompletebox-populating-with-data-binding-to-object%}). Next a valid DataTemplate with the correct bindings for the __Name__ and __Flag__ property of the ItemsSource items should be created: diff --git a/controls/radbusyindicator/features/custom-busy-content.md b/controls/radbusyindicator/features/custom-busy-content.md index 2c486030a8..74e7ad8887 100644 --- a/controls/radbusyindicator/features/custom-busy-content.md +++ b/controls/radbusyindicator/features/custom-busy-content.md @@ -93,7 +93,7 @@ In the code behind you have to: * Disable the __RadBusyIndicator__ by setting its __IsBusy__ property to __False__ in a specific condition. ->tipYou can also create a [determined RadBusyIndicator]({%slug radbusyindicator-features-report-progress-value%}) control which provides a straightforward way to report a changing progress value. +>tip You can also create a [determined RadBusyIndicator]({%slug radbusyindicator-features-report-progress-value%}) control which provides a straightforward way to report a changing progress value. >In order to use the __DispatcherTimer__ and the __INotifyPropertyChanged__ interface you will need to add the following usings/imports: >* __System.ComponentModel__ diff --git a/controls/radbusyindicator/features/delayed-display.md b/controls/radbusyindicator/features/delayed-display.md index ca7598b660..4ec9bc8126 100644 --- a/controls/radbusyindicator/features/delayed-display.md +++ b/controls/radbusyindicator/features/delayed-display.md @@ -35,7 +35,7 @@ __Defining RadBusyIndicator and a Button as content__ Finally, in the code-behind you have to handle the click event for the button and activate the __RadBusyIndicator__ control: ->tipTo read more about enabling the __RadBusyIndicator__ look [here]({%slug radbusyindicator-features-enabling-the-indicator%}). +>tip To read more about enabling the __RadBusyIndicator__ look [here]({%slug radbusyindicator-features-enabling-the-indicator%}). __Enable RadBusyIndicator__ diff --git a/controls/radbusyindicator/features/enabling-the-indicator.md b/controls/radbusyindicator/features/enabling-the-indicator.md index 752b783615..a67330aa4f 100644 --- a/controls/radbusyindicator/features/enabling-the-indicator.md +++ b/controls/radbusyindicator/features/enabling-the-indicator.md @@ -22,7 +22,7 @@ You can data bind this property in any way that suits your custom logic. The __R __RadBusyIndicator__ also gives you the __IsBusyIndicationVisible__ property. It is a read only boolean property which value will be equal to __True__ whenever the __RadBusyIndicator__ is enabled and the busy content is still visualized. ->tipTo read more about the possible scenarios where you can use the __IsBusyIndicationVisible__ property, [look here]({%slug radbusyindicator-how-to-restore-the-focus%}). +>tip To read more about the possible scenarios where you can use the __IsBusyIndicationVisible__ property, [look here]({%slug radbusyindicator-how-to-restore-the-focus%}). ## See Also diff --git a/controls/radbusyindicator/features/progress-determination.md b/controls/radbusyindicator/features/progress-determination.md index f9cdd9a75e..4d98c90f39 100644 --- a/controls/radbusyindicator/features/progress-determination.md +++ b/controls/radbusyindicator/features/progress-determination.md @@ -20,7 +20,7 @@ The default scenario is the second one - the __RadBusyIndicator__ is indetermine If you need a determined __RadBusyIndicator__ you have to set the value of the __IsIndeterminated__ property to __False__. In this case you can modify the __ProgressValue__ property, which will indicate how much of the predefined time have already elapsed. You can set its value through XAML or code-behind. However, to get the most out of it, you have to bind it to a percentage value (between 0 and 100) indicating the state of the ongoing process. ->tipRead more about reporting the current stage of loading via the __ProgressValue__ property [here]({%slug radbusyindicator-features-report-progress-value%}). +>tip Read more about reporting the current stage of loading via the __ProgressValue__ property [here]({%slug radbusyindicator-features-report-progress-value%}). Here is an example of creating a determined __RadBusyIndicator__ control: diff --git a/controls/radbusyindicator/features/report-progress-value.md b/controls/radbusyindicator/features/report-progress-value.md index 8f68c9099f..0b3939b68e 100644 --- a/controls/radbusyindicator/features/report-progress-value.md +++ b/controls/radbusyindicator/features/report-progress-value.md @@ -34,7 +34,7 @@ __Setting IsIndeterminate__ Notice that you have also defined the __ProgressValue__ property. For the purpose of this example, by using data binding you have bound it to a property named in the same way located in the code-behind. Through this binding you will be changing this property to report any shifts in the __RadBusyIndicator's__ progress value. ->tipYou can further change the default way of the progress changes notifications by customizing the [Busy Content]({%slug radbusyindicator-features-custom-busy-content%}). +>tip You can further change the default way of the progress changes notifications by customizing the [Busy Content]({%slug radbusyindicator-features-custom-busy-content%}). In the code behind you have to: diff --git a/controls/radbusyindicator/how-to/integrate-with-services-and-radwindow.md b/controls/radbusyindicator/how-to/integrate-with-services-and-radwindow.md index 1a88115ae6..75f612070a 100644 --- a/controls/radbusyindicator/how-to/integrate-with-services-and-radwindow.md +++ b/controls/radbusyindicator/how-to/integrate-with-services-and-radwindow.md @@ -22,7 +22,7 @@ Here is a snapshot of the final result: * The first thing you have to do is to declare the __RadWindow__ and set its content to be the __RadBusyIndicator__ content control as long as you want to show the indicator over the __RadWindow__ control. ->tipWe will create __RadWindow__ as a user control, the approach is explained in details [here]({%slug radwindow-how-to-use-radwindow-as-user-control%}). +>tip We will create __RadWindow__ as a user control, the approach is explained in details [here]({%slug radwindow-how-to-use-radwindow-as-user-control%}). __RadWindow declaration__ diff --git a/controls/radbusyindicator/how-to/modify-default-placement.md b/controls/radbusyindicator/how-to/modify-default-placement.md index 663ffaaf22..91099757dc 100644 --- a/controls/radbusyindicator/how-to/modify-default-placement.md +++ b/controls/radbusyindicator/how-to/modify-default-placement.md @@ -10,13 +10,13 @@ position: 0 # Modify the default placement ->tipBefore reading this topic, you might find it useful to get familiar with the [Template Structure of the RadBusyIndicator]({%slug radbusyindicator-styles-and-templates-template-structure%}) control. +>tip Before reading this topic, you might find it useful to get familiar with the [Template Structure of the RadBusyIndicator]({%slug radbusyindicator-styles-and-templates-template-structure%}) control. This topic will show you how to change the default placement of the __RadBusyIndicator__ busy content. By default it appears centered on top of the actual content. In some scenarios you may need to align it differently. In order to do this you will have to slightly modify the __RadBusyIndicator's__ default template. * The first thing you have to do is to generate the __RadBusyIndicator's__ default template. Load your project in Expression Blend and open the User Control that holds the __RadBusyIndicator__. In the 'Objects and Timeline' pane select the __RadBusyIndicator__ you want to style. From the menu choose *Object -> Edit Template -> Edit a Copy*. You will be prompted for the name of the style and where to be placed. ->tipIf you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed.After clicking 'OK', Expression Blend will generate the default style of the __RadBusyIndicator__ control in the __Resources__ section of your User Control. +>tip If you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed.After clicking 'OK', Expression Blend will generate the default style of the __RadBusyIndicator__ control in the __Resources__ section of your User Control. * Navigate to the "Indicator" element, which as it is described in the [template structure]({%slug radbusyindicator-styles-and-templates-template-structure%}) is of type __Border__ and hosts the __RadBusyIndicator's__ progress bar and busy content. diff --git a/controls/radbusyindicator/styles-and-templates/overview.md b/controls/radbusyindicator/styles-and-templates/overview.md index 551d78e90e..cc05b2b0a8 100644 --- a/controls/radbusyindicator/styles-and-templates/overview.md +++ b/controls/radbusyindicator/styles-and-templates/overview.md @@ -14,7 +14,7 @@ This section is intended to give you a broad understanding of the possible ways >To learn about how to change the control's theme using Implicit Styles, please read the common [Setting a Theme (Using Implicit Styles)]({%slug styling-apperance-implicit-styles-overview%}) topic. ->tipTo learn how to edit the default ControlTemplates read the common topic about [Editing Control Templates]({%slug styling-apperance-editing-control-templates%}). +>tip To learn how to edit the default ControlTemplates read the common topic about [Editing Control Templates]({%slug styling-apperance-editing-control-templates%}). You can modify the look of the __RadBusyIndicator__ by either changing some of the resources exposed by the API, or by modifying its __ControlTemplate__. In the control template you are allowed to reorder the template parts and to add your own elements. However, when changing the control template you should be careful to include all required parts. diff --git a/controls/radbusyindicator/styles-and-templates/setting-the-overlay-style.md b/controls/radbusyindicator/styles-and-templates/setting-the-overlay-style.md index a705fcf8a9..a9a44c5721 100644 --- a/controls/radbusyindicator/styles-and-templates/setting-the-overlay-style.md +++ b/controls/radbusyindicator/styles-and-templates/setting-the-overlay-style.md @@ -10,7 +10,7 @@ position: 4 # Setting the OverlayStyle ->tipBefore reading this topic, you might find it useful to get familiar with the [Template Structure of the RadBusyIndicator]({%slug radbusyindicator-styles-and-templates-template-structure%}) control. +>tip Before reading this topic, you might find it useful to get familiar with the [Template Structure of the RadBusyIndicator]({%slug radbusyindicator-styles-and-templates-template-structure%}) control. The __RadBusyIndicator__ exposes a __OverlayStyle__ property which allows you to apply a style to the __Rectangle__ element overlaying the __RadBusyIndicator's__ content while the indicator is active. @@ -62,7 +62,7 @@ __OverlayStyle declaration__ >Notice that in the __OverlayStyle__ the __Opacity__ property is also specified. As a result if the __RadBusyIndicator__ had any content, it would still be visible while the indicator was active. ->tipYou can remove the __RadBusyIndicator__ busy content's background by setting the control's __Background__ property to __Transparent__. +>tip You can remove the __RadBusyIndicator__ busy content's background by setting the control's __Background__ property to __Transparent__. __Remove the BusyContent's Background__ diff --git a/controls/radbusyindicator/styles-and-templates/styling-radbusyindicator.md b/controls/radbusyindicator/styles-and-templates/styling-radbusyindicator.md index 266665f900..2d24778a1a 100644 --- a/controls/radbusyindicator/styles-and-templates/styling-radbusyindicator.md +++ b/controls/radbusyindicator/styles-and-templates/styling-radbusyindicator.md @@ -10,7 +10,7 @@ position: 2 # Styling the RadBusyIndicator ->tipBefore reading this topic, you might find it useful to get familiar with the [Template Structure of the RadBusyIndicator]({%slug radbusyindicator-styles-and-templates-template-structure%}) control. +>tip Before reading this topic, you might find it useful to get familiar with the [Template Structure of the RadBusyIndicator]({%slug radbusyindicator-styles-and-templates-template-structure%}) control. The __RadBusyIndicator__ exposes a __Style__ property which allows you to modify its appearance. @@ -26,7 +26,7 @@ This topic will show you how to perform the second one. To copy the default styles, load your project in Expression Blend and open the User Control that holds the __RadBusyIndicator__. In the 'Objects and Timeline' pane select the __RadBusyIndicator__ you want to style. From the menu choose *Object -> Edit Style -> Edit a Copy*. You will be prompted for the name of the style and where to be placed. ->tipIf you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. +>tip If you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. After clicking 'OK', Expression Blend will generate the default style of the __RadBusyIndicator__ control in the __Resources__ section of your User Control. The properties available for the style will be loaded in the 'Properties' pane and you will be able to modify their default values. You can also edit the generated XAML in the XAML View or in Visual Studio. diff --git a/controls/radbusyindicator/styles-and-templates/styling-the-radprogressbar.md b/controls/radbusyindicator/styles-and-templates/styling-the-radprogressbar.md index 7dc8a3460e..dce8823da3 100644 --- a/controls/radbusyindicator/styles-and-templates/styling-the-radprogressbar.md +++ b/controls/radbusyindicator/styles-and-templates/styling-the-radprogressbar.md @@ -10,7 +10,7 @@ position: 3 # Styling the RadProgressBar ->tipBefore reading this topic, you might find it useful to get familiar with the [Template Structure of the RadBusyIndicator]({%slug radbusyindicator-styles-and-templates-template-structure%}) control. +>tip Before reading this topic, you might find it useful to get familiar with the [Template Structure of the RadBusyIndicator]({%slug radbusyindicator-styles-and-templates-template-structure%}) control. The __RadBusyIndicator__ exposes a __ProgressBarStyle__ property which allows you to modify the control's progress bar default appearance. @@ -24,7 +24,7 @@ You have two options: To copy the default styles, load your project in Expression Blend and open the User Control that holds the __RadBusyIndicator__. In the 'Objects and Timeline' pane select the __RadBusyIndicator__ you want to style. From the menu choose *Object -> Edit Style -> Edit a Copy*. You will be prompted for the name of the style and where to be placed. ->tipIf you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. +>tip If you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. After clicking 'OK', Expression Blend will generate the default style of the __RadBusyIndicator__ control in the __Resources__ section of your User Control. The properties available for the style will be loaded in the 'Properties' pane and you will be able to modify their default values. You can also edit the generated XAML in the XAML View or in Visual Studio. @@ -52,7 +52,7 @@ Here is the result: ## Create a custom ProgressBar Style ->tipRead more about the __RadProgressBar__ [here]({%slug radprogressbar-overview%}). +>tip Read more about the __RadProgressBar__ [here]({%slug radprogressbar-overview%}). >When you choose to create a custom __ProgressBarStyle__ you will lose the __RadBusyIndicator's__ default template. diff --git a/controls/radbuttons/features/button-extensions.md b/controls/radbuttons/features/button-extensions.md index b4f6d0474e..c3a919db28 100644 --- a/controls/radbuttons/features/button-extensions.md +++ b/controls/radbuttons/features/button-extensions.md @@ -16,7 +16,7 @@ The Telerik suite provides built-in extensions that can change different behavio * __HandleMouseWheelWhenOpen:__ A boolean property that gets or sets if the **MouseWheel** event is handled while a drop-down content of a drop-down button is open. By setting this property to **true** you won't be able to scroll your page while the drop-down content is open. The default value is **false**. ->importantThis property can be set on the following controls: __RadDropDownButton, RadSplitButton, RadColorPicker, RadTimeSpanPicker, RadDateTimePicker, RadBreadCrumb__. +>important This property can be set on the following controls: __RadDropDownButton, RadSplitButton, RadColorPicker, RadTimeSpanPicker, RadDateTimePicker, RadBreadCrumb__. __Example 1: Set HandleMouseWheelWhenOpen attached property__ ```XAML @@ -40,7 +40,7 @@ __Example 1: Set HandleMouseWheelWhenOpen attached property__ ``` ->importantThis property is not supported when the control (for example, RadDropDownButton) has its __KeepOpen__ property set to __True__. +>important This property is not supported when the control (for example, RadDropDownButton) has its __KeepOpen__ property set to __True__. ## DropDownButtonExtensions diff --git a/controls/radchart/features/annotations/custom-gridline.md b/controls/radchart/features/annotations/custom-gridline.md index dafbf5aa35..7789d4a605 100644 --- a/controls/radchart/features/annotations/custom-gridline.md +++ b/controls/radchart/features/annotations/custom-gridline.md @@ -16,13 +16,13 @@ position: 1 The Custom Gridline allows you to place a vertical or horizontal gridline at a specific place in your __ChartArea__. This allows you to mark a specific value on the __Y-Axis__ and/or the __X-Axis__, which can, for example, serve as a border value. In order to place the Custom GridLine you have to add a __CustomGridLine__ object to the __Annotations__ collection of the __ChartArea__. You also have to set either its __XIntercept__ or __YIntercept__ properties. These properties allow you to specify the value of the X- and Y-Axis, for which the gridline should be placed. ->tipYou can place more than one __CustomGridLine__ in your __ChartArea__. +>tip You can place more than one __CustomGridLine__ in your __ChartArea__. >The __XIntercept__ and the __YIntercept__ are of type __double__. Therefore, if the respective axis displays __DateTime__ values, you have to pass converted to OLE Automation dates to them. For more information see [DateTime.ToOADate()](http://msdn.microsoft.com/en-us/library/system.datetime.tooadate(VS.95).aspx). In order to customize the appearance of the __CustomGridLine__ you can simply set its __Stroke__ (will change its color) and its __StrokeThickness__ (will change the thickness of the line). ->tipIf you have multiple y-axes, you can specify to which the __CustomGridLine__ should be applied by setting the __x:Name__ value of the appropriate __Y-Axis__ to the __YAxisName__ property of the __CustomGridLine__. +>tip If you have multiple y-axes, you can specify to which the __CustomGridLine__ should be applied by setting the __x:Name__ value of the appropriate __Y-Axis__ to the __YAxisName__ property of the __CustomGridLine__. Here is an example: @@ -102,5 +102,5 @@ Additional customizations can be done via the __ElementStyle__ property. It gets ->tipThis can be done in code behind too. +>tip This can be done in code behind too. ![{{ site.framework_name }} RadChart ](images/RadChart_Features_Annotations_CustomGridLine_02.png) diff --git a/controls/radchart/features/annotations/custom-line.md b/controls/radchart/features/annotations/custom-line.md index 49af561457..f98351e1b2 100644 --- a/controls/radchart/features/annotations/custom-line.md +++ b/controls/radchart/features/annotations/custom-line.md @@ -14,7 +14,7 @@ position: 0 The __Custom Line__ annotation allows you to place a straight line at a specific place in your __Chart Area__. In order to place the __Custom Line__ you have to add a __CustomLine__ object to the __Annotations__ collection of the __ChartArea__. You also have to use its__Slope and YIntercept__properties. ->tipYou can place more than one __CustomLine__ in your __ChartArea__. +>tip You can place more than one __CustomLine__ in your __ChartArea__. In order to define the line you have to set the __Slope__ and/or the __YIntercept__ properties. The function which draws the custom line is __y = mx + b__, where '__m__' is the __Slope__ and '__b__' is __YIntercept__. diff --git a/controls/radchart/features/annotations/marked-zone.md b/controls/radchart/features/annotations/marked-zone.md index 161c6737e5..84230d13d7 100644 --- a/controls/radchart/features/annotations/marked-zone.md +++ b/controls/radchart/features/annotations/marked-zone.md @@ -16,13 +16,13 @@ position: 2 The Marked Zone feature allows you to place a rectangle inside the __ChartArea__. This allows you to mark a specific part of it, in order to easily look at all the data that belongs to this area. In order to creat a Marked Zone you have to use the __MarkedZone__ class and add an instance of it to the __Annotations__ collection of the __ChartArea__. You also have to set its __StartY__ and __EndY__ properties for a rectangle that spans along the entire X-Axis, or the __StartX__ and __EndX__ properties for a rectangle that spans along the entire Y-Axis, or set the four properties at once in order to create a rectangle that is limited in both directions. ->tipYou can place more than one __MarkedZone__in your __ChartArea__. +>tip You can place more than one __MarkedZone__in your __ChartArea__. >The __StartX, EndX, StartY__ and __EndY__ are of type __double__. Therefore, if the respective axis displays __DateTime__ values, you have to pass converted to OLE Automation dates to them. For more information see [DateTime.ToOADate()](http://msdn.microsoft.com/en-us/library/system.datetime.tooadate(VS.95).aspx). In order to customize the appearance of the __MarkedZone__ you can simply set its __Background__ property, __Stroke__ (will change its color) and its __StrokeThickness__ (will change the thickness of the line). ->tipIf you have multiple y-axes, you can specify to which the __MarkedZone__ should be applied by setting the __x:Name__ value of the appropriate __Y-Axis__ to the __YAxisName__ property of the __MarkedZone__. +>tip If you have multiple y-axes, you can specify to which the __MarkedZone__ should be applied by setting the __x:Name__ value of the appropriate __Y-Axis__ to the __YAxisName__ property of the __MarkedZone__. The following code snippet demonstrates a RadChart with LineSeries that will be used as base for adding MarkedZones over: @@ -162,7 +162,7 @@ Here is an example of a marked zone that is limited in both directions. ->tipThis can be done in code behind too! +>tip This can be done in code behind too! ![{{ site.framework_name }} RadChart ](images/RadChart_Features_Annotations_MarkedZone_02.png) @@ -197,7 +197,7 @@ The Marked Zones can overlap each other. In such case their __Z-Index__ will be ->tipThis can be done in code behind too! +>tip This can be done in code behind too! ![{{ site.framework_name }} RadChart ](images/RadChart_Features_Annotations_MarkedZone_03.png) @@ -237,5 +237,5 @@ Additional customizations can be done via the __ElementStyle__ property. It gets ->tipThis can be done in code behind too! +>tip This can be done in code behind too! ![{{ site.framework_name }} RadChart ](images/RadChart_Features_Annotations_MarkedZone_04.png) diff --git a/controls/radchart/features/axes/logarithmic-scale.md b/controls/radchart/features/axes/logarithmic-scale.md index 03766c8c05..e6f1979214 100644 --- a/controls/radchart/features/axes/logarithmic-scale.md +++ b/controls/radchart/features/axes/logarithmic-scale.md @@ -70,6 +70,6 @@ Here is the same __RadChart__, but this time with logarithmic Y-Axis. ->tipYou can use the __LogarithmBase__ property of the __AxisY__ to modify the base on which the logarithmic function for the axis is calculated. +>tip You can use the __LogarithmBase__ property of the __AxisY__ to modify the base on which the logarithmic function for the axis is calculated. ![{{ site.framework_name }} RadChart ](images/RadChart_Features_Axes_Logarithmic_Scale_02.png) diff --git a/controls/radchart/features/axes/striplines-and-gridlines.md b/controls/radchart/features/axes/striplines-and-gridlines.md index 46045a85fb..38a8299b29 100644 --- a/controls/radchart/features/axes/striplines-and-gridlines.md +++ b/controls/radchart/features/axes/striplines-and-gridlines.md @@ -12,7 +12,7 @@ position: 4 In order to improve the readiness of the chart, you can use __strip lines__ and __grid lines__. Besides, for [Y-Axis]({%slug radchart-features-axes-y-axis%}) you can also show grid lines for the minor ticks. ->tipTo learn more about the visual elements of the __RadChart__, read the [Visual Structure]({%slug radchart-general-information-visual-structure%}) topic. +>tip To learn more about the visual elements of the __RadChart__, read the [Visual Structure]({%slug radchart-general-information-visual-structure%}) topic. The strip lines and grid lines are part of the axes. Therefore, to control the visibility of the grid/strip lines you have to use one of the following properties: diff --git a/controls/radchart/features/axes/ticks.md b/controls/radchart/features/axes/ticks.md index f35b984819..00995fa6b9 100644 --- a/controls/radchart/features/axes/ticks.md +++ b/controls/radchart/features/axes/ticks.md @@ -24,7 +24,7 @@ To control the visibility of the ticks you have to use one fo the following prop * __MinorTickPointMultiplier__ - specifies the number of minor ticks per major tick, i.e the number of the minor ticks between two major ticks. The number of ticks is always equal to the (__MinorTickPointMultiplier__ - 1) as the multiplier rerpesents the count of chuks defined by the minor ticks between two major ticks. For example in order to have 3 chunks the Axis will need 2 minor ticks to allocate them. ->tipTo learn how to modify the appearance of the axis' ticks read the [Styling the Axes]({%slug radchart-styling-and-appearance-styling-axes-overview%}) section. +>tip To learn how to modify the appearance of the axis' ticks read the [Styling the Axes]({%slug radchart-styling-and-appearance-styling-axes-overview%}) section. These properties are available for both the x- and the y-axis. Here is an example of hiding the major ticks of the x-axis and configuring it to display 2 minor ticks between each two major ones. diff --git a/controls/radchart/features/chart-export.md b/controls/radchart/features/chart-export.md index f74480cb17..dd1f249881 100644 --- a/controls/radchart/features/chart-export.md +++ b/controls/radchart/features/chart-export.md @@ -24,7 +24,7 @@ __RadChart__ allows you to export the chart in several file formats: * __Xps__ - XML Paper Specification file. Use __RadChart.ExportToXps(Stream)__. ->tipIn WPF there are overloads for the methods listed above, which take as parameter the name of the file you want to export to, instead of a stream. This allows you to easily export your chart directly to a file. +>tip In WPF there are overloads for the methods listed above, which take as parameter the name of the file you want to export to, instead of a stream. This allows you to easily export your chart directly to a file. The following example demonstrates how to export __RadChart__ to ExcelML file format. diff --git a/controls/radchart/features/chart-legend.md b/controls/radchart/features/chart-legend.md index efee1848c3..4f91a99f25 100644 --- a/controls/radchart/features/chart-legend.md +++ b/controls/radchart/features/chart-legend.md @@ -14,7 +14,7 @@ position: 14 __ChartLegend__ is used to provide information about the charts shown on the chart area. The __ChartLegend__ has __Header__, usually some text and items - one for each chart series. ->tipTo see how to style and template __ChartLegend__ take a look at the [Styling the Chart Legend]({%slug radchart-styling-and-appearance-styling-chart-legend%}) topic. +>tip To see how to style and template __ChartLegend__ take a look at the [Styling the Chart Legend]({%slug radchart-styling-and-appearance-styling-chart-legend%}) topic. This topic will make you familiar with the following things: @@ -61,9 +61,9 @@ In order to have legend items generated automatically, you have to use the prope ->tipBy default, the __RadChart.DefaultView.ChartLegend__ is associated with the __RadChart.DefaultView.ChartArea__. However, if you predefine the __DefaultView__ (like it was done in the XAML above), be sure that the __ChartArea__ has its property __LegendName__ set to the name of the newly created __ChartLegend__. Otherwise, your legend items will not be auto generated. +>tip By default, the __RadChart.DefaultView.ChartLegend__ is associated with the __RadChart.DefaultView.ChartArea__. However, if you predefine the __DefaultView__ (like it was done in the XAML above), be sure that the __ChartArea__ has its property __LegendName__ set to the name of the newly created __ChartLegend__. Otherwise, your legend items will not be auto generated. ->tipIf you want to set the legend title only, it is better to do it in the code-behind not in the XAML, because you will have to predefine the whole [visual structure]({%slug radchart-general-information-visual-structure%}) of the chart's default view. +>tip If you want to set the legend title only, it is better to do it in the code-behind not in the XAML, because you will have to predefine the whole [visual structure]({%slug radchart-general-information-visual-structure%}) of the chart's default view. ```C# this.radChart.DefaultView.ChartLegend.UseAutoGeneratedItems = true; @@ -143,11 +143,11 @@ The __SeriesDefinitions__ expose the __LegendDisplayMode__ property, which allow * __SeriesLabel__ - this will display an item for each series in your __RadChart__. ->tipThe default value is different depending on the type of the series. +>tip The default value is different depending on the type of the series. Here is an example of how the legend looks, when the __LegednDisplayMode__ of the __DefaultSeriesDeifinition__ is set to __DataPointLabel__. ->tipWhen using dynamic data and you want the __LegednDisplayMode__ to be set to __DataPointLabel__, you have to create an __ItemMapping__ for the __LegendLabel__ property of the __DataPoint__. More information about __ItemMappings__ can be found [here]({%slug radchart-populating-with-data-data-binding-with-manual-series-mapping%}). +>tip When using dynamic data and you want the __LegednDisplayMode__ to be set to __DataPointLabel__, you have to create an __ItemMapping__ for the __LegendLabel__ property of the __DataPoint__. More information about __ItemMappings__ can be found [here]({%slug radchart-populating-with-data-data-binding-with-manual-series-mapping%}). diff --git a/controls/radchart/features/drill-down/hierarchical-view.md b/controls/radchart/features/drill-down/hierarchical-view.md index e56be13d64..a4e7e38890 100644 --- a/controls/radchart/features/drill-down/hierarchical-view.md +++ b/controls/radchart/features/drill-down/hierarchical-view.md @@ -75,7 +75,7 @@ Here is an example of a data with two levels of hierarchy. The data contains the ->tipThe __Sum()__ extension method is available via the __System.Linq__ namespace. +>tip The __Sum()__ extension method is available via the __System.Linq__ namespace. diff --git a/controls/radchart/features/drill-down/in-multiple-chart-areas.md b/controls/radchart/features/drill-down/in-multiple-chart-areas.md index faade738db..e7e64d74c8 100644 --- a/controls/radchart/features/drill-down/in-multiple-chart-areas.md +++ b/controls/radchart/features/drill-down/in-multiple-chart-areas.md @@ -20,7 +20,7 @@ This is the other of displaying the drill down charts via the __RadChart__ contr In order to use multiple chart areas in your __RadChart__ you have to disable the default layout. This is done by setting the __UseDefaultLayout__ property of the __RadChart__ to __False__. ->tipTo learn more about using multiple chart areas read [this topic]({%slug radchart-features-multiple-cahrt-areas%}). +>tip To learn more about using multiple chart areas read [this topic]({%slug radchart-features-multiple-cahrt-areas%}). Now you are able to define more than one chart area inside the __RadChart__ control. Here is a sample structure of a __Grid__ that holds two __ChartAreas__. @@ -45,7 +45,7 @@ Now you are able to define more than one chart area inside the __RadChart__ cont The definition of the __ChartHierarchicalViewDescriptor__ objects is the same as in the [Hierarchical View]({%slug radchart-features-drill-down-hierarchical-view%}) topic, with the excpetion that each of the SeriesMapping objects is associated with the respective chart area. ->tipYou can associate multiple __SeriesMapping__ objects belonging to different __ChartHierarchicalViewDescriptor__ objects to one and the same __ChartArea__. You just have to set their __ChartAreaName__ property to the respective chart area's name. +>tip You can associate multiple __SeriesMapping__ objects belonging to different __ChartHierarchicalViewDescriptor__ objects to one and the same __ChartArea__. You just have to set their __ChartAreaName__ property to the respective chart area's name. diff --git a/controls/radchart/features/export-to-pdf.md b/controls/radchart/features/export-to-pdf.md index 47eaaf50dd..ef9879b1d2 100644 --- a/controls/radchart/features/export-to-pdf.md +++ b/controls/radchart/features/export-to-pdf.md @@ -14,7 +14,7 @@ position: 32 This help topic will demonstrate how to export RadChart and RadGridView controls to PDF document simultaneously. For the purpose you should build the export-to-image functionality and export the image to PDF using our [Documents Format Providers](http://www.telerik.com/help/silverlight/radrichtextbox-features-import-export.html) (also part of the RadControls for Silverlight suite). ->tipA sample project demonstrating Exporting RadChart to PDF can be found in the end of this [blogpost](http://blogs.telerik.com/blogs/posts/11-06-16/pdf-export-with-radchart-for-silverlight.aspx). +>tip A sample project demonstrating Exporting RadChart to PDF can be found in the end of this [blogpost](http://blogs.telerik.com/blogs/posts/11-06-16/pdf-export-with-radchart-for-silverlight.aspx). Basically, all you need to do is construct a document model based on the contents you want to export, and then pass the document to the __PdfFormatProvider__. This way you can combine the output of several controls into a single document export. To export the chart part of the document: diff --git a/controls/radchart/features/filtering.md b/controls/radchart/features/filtering.md index a6a85eb5da..09dbb0af98 100644 --- a/controls/radchart/features/filtering.md +++ b/controls/radchart/features/filtering.md @@ -32,7 +32,7 @@ Here is an example of a chart without filter descriptors. Here is an example of implementing filtering. ->tipTo use the __ChartFilterDescriptors__ in XAML you have to declare the following namespace: +>tip To use the __ChartFilterDescriptors__ in XAML you have to declare the following namespace: diff --git a/controls/radchart/features/grouping/and-aggregation.md b/controls/radchart/features/grouping/and-aggregation.md index f3387512bc..b536228f5c 100644 --- a/controls/radchart/features/grouping/and-aggregation.md +++ b/controls/radchart/features/grouping/and-aggregation.md @@ -83,7 +83,7 @@ __RadChart__ allows you to define grouping and aggregation for each series separ The following example, considering the sample data above, demonstrates how to use grouping with bar chart: ->tipIn order to use the grouping feature, you have to declare the following namespace: +>tip In order to use the grouping feature, you have to declare the following namespace: diff --git a/controls/radchart/features/grouping/flattened-series.md b/controls/radchart/features/grouping/flattened-series.md index 9e3a689aca..20f61f5556 100644 --- a/controls/radchart/features/grouping/flattened-series.md +++ b/controls/radchart/features/grouping/flattened-series.md @@ -16,7 +16,7 @@ Sometimes when the grouping and aggregation get applied you might want to flatte Here is a __RadChart__ declaration before setting the __ShouldFlattenSeries__ property to __True__. ->tipTo learn more about __DateTime Grouping__ read [here]({%slug radchart-features-datetime-grouping%}). +>tip To learn more about __DateTime Grouping__ read [here]({%slug radchart-features-datetime-grouping%}). diff --git a/controls/radchart/features/interactivity-effects.md b/controls/radchart/features/interactivity-effects.md index 30c97053d4..551df4ab92 100644 --- a/controls/radchart/features/interactivity-effects.md +++ b/controls/radchart/features/interactivity-effects.md @@ -84,13 +84,13 @@ For example if __HoverScope__ is set to __InteractivityScope.Series__ for a give ![{{ site.framework_name }} RadChart with Hover Effect](images/RadChart_Features_InteractivityEffects_010.png) ->tipIn order to enable the interactivity functionality you need to first set the interactivity scope for hover, selection, or both. The notion of "interactivity scope" specifies whether the chart control should interpret the interactivity action (selection or hover) on series level (if applicable), or on item level (if applicable). +>tip In order to enable the interactivity functionality you need to first set the interactivity scope for hover, selection, or both. The notion of "interactivity scope" specifies whether the chart control should interpret the interactivity action (selection or hover) on series level (if applicable), or on item level (if applicable). >__InteractivityScope.Item__ is not supported for series that do not render separate items (__Line__, __Spline__, __Area__, __Range__, and __all their stacked versions__). __InteractivityScope.Series__ is not supported for radial series (__Pie__ and __Doughnut__). There is one additional setting related to hover effects that can be set on global level - __RadChart.HoverActivationDelay__. This property gets or sets the delay before the hover effect is activated (by default there is no delay and the hover effect becomes active immediately). ->tipYou could check out an online example [here](https://demos.telerik.com/silverlight/#Chart/InteractivityEffects). +>tip You could check out an online example [here](https://demos.telerik.com/silverlight/#Chart/InteractivityEffects). ## Complete Demo Code diff --git a/controls/radchart/features/negative-values.md b/controls/radchart/features/negative-values.md index 7d2e5baf93..d3a6d3eafd 100644 --- a/controls/radchart/features/negative-values.md +++ b/controls/radchart/features/negative-values.md @@ -22,7 +22,7 @@ You can see that in this type of scenarios the main X and Y Axes don't get trans In order to control the visibility of the plot area's axes you can use the __PlotAreaAxisVisibility__ property, which is available both for the x- and the y-axis. Setting the __AxisX's__ proeprty to __Collapsed__ will make the __y-axis__ of the plot area collapsed and respectively setting the __AxisY's__ property to __Collapsed__ will make the __x-axis__ of the plot area collapsed. As you can notice the __PlotAreaVisibility__ property controls the other dimension's plot area axis visibility. This is because you can decide whether you need to show the horizontal axis within the plot area only when the vertical one's range contains both positive and negative values. For example, when AxisY ranges from -10 to 10 you can decide if you need to see the X axis within the plot area. ->tipThe __PlotAreaAxisLabelsVisibility__ applies to the labels of the plot area axes. +>tip The __PlotAreaAxisLabelsVisibility__ applies to the labels of the plot area axes. Here is an example with hiding the y-axis of the plot area. diff --git a/controls/radchart/features/sampling.md b/controls/radchart/features/sampling.md index 3e3ce98be6..e8722844b2 100644 --- a/controls/radchart/features/sampling.md +++ b/controls/radchart/features/sampling.md @@ -26,7 +26,7 @@ Determining the number of __DataPoints__ to be displayed is done by setting the ``` ->tipSet the __SamplingThreshold__ to __0__ to disable the feature. +>tip Set the __SamplingThreshold__ to __0__ to disable the feature. The way in which __RadChart__ combines the __DataPoints__ depends on the value of the __SamplingFunction__ property of the SamplingSettings. @@ -65,7 +65,7 @@ Here is an example: ## Custom Sampling Functions ->tipCustom sampling functions are implemented in the same manner as [GridView's custom aggregating functions](https://demos.telerik.com/silverlight/#GridView/CustomAggregates). +>tip Custom sampling functions are implemented in the same manner as [GridView's custom aggregating functions](https://demos.telerik.com/silverlight/#GridView/CustomAggregates). The following sample code will demonstrate how to create a standard deviation function for the Range of numbers 0 - 1000 and creates ScatterSeriesDefinition with the result from this function. diff --git a/controls/radchart/features/sorting.md b/controls/radchart/features/sorting.md index f2f2d26e10..954e1f43e2 100644 --- a/controls/radchart/features/sorting.md +++ b/controls/radchart/features/sorting.md @@ -32,7 +32,7 @@ Here is an example of a chart without sorting descriptors. Here is an example of implementing sorting. ->tipTo use the __ChartSortDescriptors__ in XAML you have to declare the following namespace: +>tip To use the __ChartSortDescriptors__ in XAML you have to declare the following namespace: diff --git a/controls/radchart/features/tooltips.md b/controls/radchart/features/tooltips.md index b99dd75d8c..90bbd564de 100644 --- a/controls/radchart/features/tooltips.md +++ b/controls/radchart/features/tooltips.md @@ -507,7 +507,7 @@ The snapshot below shows the customized tooltip: If you need more information about label formatting take a look at the [Format Expressions]({%slug radchart-features-format-expressions%}) topic. ->tipTo be able to show the ToolTip content separated on new line in XAML you should use the hexidecimally encoded value " " to represent the "\n" literal. +>tip To be able to show the ToolTip content separated on new line in XAML you should use the hexidecimally encoded value " " to represent the "\n" literal. ## Customizing Tooltip Content @@ -782,7 +782,7 @@ As you can see, the new instance of __StockToolTipControl__ is created, initiali ![{{ site.framework_name }} RadChart ](images/RadChart_Features_ToolTips_20.png) ->tipCheck out how a [Drill Down Chart]({%slug radchart-how-to-drill-down-chart%}) is created using customized tooltip. +>tip Check out how a [Drill Down Chart]({%slug radchart-how-to-drill-down-chart%}) is created using customized tooltip. ## See Also diff --git a/controls/radchart/features/zooming-and-scrolling.md b/controls/radchart/features/zooming-and-scrolling.md index fdcb694942..44d0a59a3f 100644 --- a/controls/radchart/features/zooming-and-scrolling.md +++ b/controls/radchart/features/zooming-and-scrolling.md @@ -38,11 +38,11 @@ Besides the __Sampling__, the __RadChart__ provides you with __Zooming__ and __S * __ScrollOnly__ - only scrolling is enabled. ->tipThe __ZoomScrollingSetting__ exposes a __PropertyChanged__ event which allows you to execute your custom logic, when a certain property has changed. +>tip The __ZoomScrollingSetting__ exposes a __PropertyChanged__ event which allows you to execute your custom logic, when a certain property has changed. To apply the __ZoomScrollingSettings__ you have to set them to the __ZoomScrollingSettingsX__ and/or the __ZoomScrollingSettingsY__ of the __ChartArea__. ->tipCombining the Zooming feature with the Sampling feature can be very useful. +>tip Combining the Zooming feature with the Sampling feature can be very useful. Here is an example. diff --git a/controls/radchart/getting-started/create-data-bound-chart.md b/controls/radchart/getting-started/create-data-bound-chart.md index 9e9a8495a3..ca24898f93 100644 --- a/controls/radchart/getting-started/create-data-bound-chart.md +++ b/controls/radchart/getting-started/create-data-bound-chart.md @@ -252,7 +252,7 @@ The __X-axis__ can be further customized by replacing the month numbers (1, 2, 3 And here is the same chart but this time showing month names as categories for the __X-axis__ instead of the month numbers. ![{{ site.framework_name }} RadChart ](images/RadChart_GettingStarted_DataBoundChart_04.png) ->tipTo make the x-Axis labels more readable you can use one of the label features provided by the __XAxis__ class. For more information read [here]({%slug radchart-features-axes-x-axis%}). +>tip To make the x-Axis labels more readable you can use one of the label features provided by the __XAxis__ class. For more information read [here]({%slug radchart-features-axes-x-axis%}). If you need further customizations of the chart you can take a look at some of the following topics: diff --git a/controls/radchart/how-to/add-annotations-in-chart-legend.md b/controls/radchart/how-to/add-annotations-in-chart-legend.md index 5afcadc73f..41f08636f8 100644 --- a/controls/radchart/how-to/add-annotations-in-chart-legend.md +++ b/controls/radchart/how-to/add-annotations-in-chart-legend.md @@ -60,7 +60,7 @@ The following help article will demonstrate how to customize the Chart Legend so ->tipThe ChartLegendItem style may be different for the older versions of the RadChart +>tip The ChartLegendItem style may be different for the older versions of the RadChart ##### 3. Create a sample Chart and add CustomGridLine by applying the CustomGridLine Style: diff --git a/controls/radchart/how-to/howto-binding-datapointmember-to-a-depenndency-property.md b/controls/radchart/how-to/howto-binding-datapointmember-to-a-depenndency-property.md index 4101f5bc9c..7ccbdd447d 100644 --- a/controls/radchart/how-to/howto-binding-datapointmember-to-a-depenndency-property.md +++ b/controls/radchart/how-to/howto-binding-datapointmember-to-a-depenndency-property.md @@ -123,7 +123,7 @@ Here is the final result: ![{{ site.framework_name }} RadChart ](images/RadChart_HowToDependencyProperty.PNG) ->tipYou should move the focus out of the Text box in Silverlight to be able to see the new value of the Bar. +>tip You should move the focus out of the Text box in Silverlight to be able to see the new value of the Bar. ## See Also diff --git a/controls/radchart/how-to/howto-filter-radchart-using-the-gridviews-compositefilterdescriptor.md b/controls/radchart/how-to/howto-filter-radchart-using-the-gridviews-compositefilterdescriptor.md index 89eb05697e..7fc7f0a488 100644 --- a/controls/radchart/how-to/howto-filter-radchart-using-the-gridviews-compositefilterdescriptor.md +++ b/controls/radchart/how-to/howto-filter-radchart-using-the-gridviews-compositefilterdescriptor.md @@ -354,7 +354,7 @@ The code-behind: End Class ``` ->tipThe code snippets above were taken from a Silverlight project but are absolutely applicable for WPF scenarios. +>tip The code snippets above were taken from a Silverlight project but are absolutely applicable for WPF scenarios. The bound non-filtered data looks like this: ![{{ site.framework_name }} RadChart ](images/RadChart_HowToOriginal.PNG) diff --git a/controls/radchart/populating-with-data/binding-to-adonet-service.md b/controls/radchart/populating-with-data/binding-to-adonet-service.md index c3d0822ad5..f3802229a8 100644 --- a/controls/radchart/populating-with-data/binding-to-adonet-service.md +++ b/controls/radchart/populating-with-data/binding-to-adonet-service.md @@ -112,7 +112,7 @@ Add a reference to your ADO.NET Data Service. ->tipFor more information about how to add a reference to an ADO.NET Data Service and how to create a new instance of the exposed entity, take a look at the [Consuming ADO.NET Data Service](http://www.telerik.com/help/silverlight/consuming-data-ado-net-data-service.html) topic. +>tip For more information about how to add a reference to an ADO.NET Data Service and how to create a new instance of the exposed entity, take a look at the [Consuming ADO.NET Data Service](http://www.telerik.com/help/silverlight/consuming-data-ado-net-data-service.html) topic. Add the following code which will make the initial load of the objects. diff --git a/controls/radchart/populating-with-data/binding-to-wcf.md b/controls/radchart/populating-with-data/binding-to-wcf.md index 2dcb273933..1dad2bd89f 100644 --- a/controls/radchart/populating-with-data/binding-to-wcf.md +++ b/controls/radchart/populating-with-data/binding-to-wcf.md @@ -87,7 +87,7 @@ Now build the project before continuing. * Add a reference to your WCF Service. ->tipFor more information about how to add a reference to a WCF Service and how to create a new instance of a WCF Service client, take a look at the [Consuming WCF Service](http://www.telerik.com/help/silverlight/consuming-data-wcf-service.html) topic. +>tip For more information about how to add a reference to a WCF Service and how to create a new instance of a WCF Service client, take a look at the [Consuming WCF Service](http://www.telerik.com/help/silverlight/consuming-data-wcf-service.html) topic. * Switch to the code-behind and create a new instance of your WCF Service client. @@ -221,7 +221,7 @@ This section will show you how to populate your __RadChart__ control in a MVVM m ->tipFor more information about how to add a reference to a WCF Service and how to create a new instance of a WCF Service client, take a look at the [Consuming WCF Service](http://www.telerik.com/help/silverlight/consuming-data-wcf-service.html) topic. +>tip For more information about how to add a reference to a WCF Service and how to create a new instance of a WCF Service client, take a look at the [Consuming WCF Service](http://www.telerik.com/help/silverlight/consuming-data-wcf-service.html) topic. * Add the following code in the constructor of the __NorthwindDataSource__. It will make the initial load of all __Products__ from the database: diff --git a/controls/radchart/populating-with-data/data-binding-with-manual-series-mapping.md b/controls/radchart/populating-with-data/data-binding-with-manual-series-mapping.md index c6a14d9c70..826e7cccce 100644 --- a/controls/radchart/populating-with-data/data-binding-with-manual-series-mapping.md +++ b/controls/radchart/populating-with-data/data-binding-with-manual-series-mapping.md @@ -413,7 +413,7 @@ The purpose of this tutorial is to show you how to use __RadChart__ with __Manua 3 . In order to map to such kind of business objects, you have to create a new instance of __SeriesMapping__. Set the __SeriesMapping.SeriesDefinition__ property to the chart type you want to use - in this case __CandleStickSeriesDefinition__. ->tipYou can find a full list of supported chart types [here]({%slug radchart-features-chart-types-2d-charts%}). +>tip You can find a full list of supported chart types [here]({%slug radchart-features-chart-types-2d-charts%}). diff --git a/controls/radchart/styles-and-templates/styling-and-appearance-overview.md b/controls/radchart/styles-and-templates/styling-and-appearance-overview.md index 965c197ef8..1354174331 100644 --- a/controls/radchart/styles-and-templates/styling-and-appearance-overview.md +++ b/controls/radchart/styles-and-templates/styling-and-appearance-overview.md @@ -16,11 +16,11 @@ position: 0 This section is intended to give you a broad understanding of the possible ways in which you can change the visual appearance of the __RadChart__. There is also comprehensive information about its __ControlTemplates__. You will need this information if you want to customize their appearance. ->tipTo learn how to change the control's theme, please read the common [Theming](http://www.telerik.com/help/silverlight/common-styling-apperance-setting-theme.html) topic. +>tip To learn how to change the control's theme, please read the common [Theming](http://www.telerik.com/help/silverlight/common-styling-apperance-setting-theme.html) topic. You can modify the look of the __RadChart__ by either changing some of the resources exposed by the API, or by modifying its __ControlTemplates__. In the control template you are allowed to reorder the template parts and to add your own elements. However, when changing the control template you should be careful to include all required parts. ->tipTo learn more about templating the __RadControls__ read the [common topic](http://www.telerik.com/help/silverlight/common-styling-appearance-edit-control-templates-blend.html) regarding templating. +>tip To learn more about templating the __RadControls__ read the [common topic](http://www.telerik.com/help/silverlight/common-styling-appearance-edit-control-templates-blend.html) regarding templating. >Note that when changing the __ControlTemplate__ you should include all required parts. Even if your code compiles, some of the functionality may be subject to impact due to the omission of the required parts. The required parts are usually marked with the prefix "__PART__". diff --git a/controls/radchart/styles-and-templates/styling-and-appearance-styling-chart-legend.md b/controls/radchart/styles-and-templates/styling-and-appearance-styling-chart-legend.md index ea606f3357..21d1daab0d 100644 --- a/controls/radchart/styles-and-templates/styling-and-appearance-styling-chart-legend.md +++ b/controls/radchart/styles-and-templates/styling-and-appearance-styling-chart-legend.md @@ -30,11 +30,11 @@ When working in Expression Blend, the namespaces that are needed will be added a Load your project in Expression Blend and open the User Control that holds the __RadChart__. You have to use a dummy controls in order to get the default styles. To create one find the __ChartLegend__ or the __ChartLegendItem__ control in the 'Assets' pane and draw one on the art board. In the 'Objects and Timeline' pane select the control, you've drawn and from the menu choose *Object -> Edit Style -> Edit a Copy*. You will be prompted for the name of the style and where to be placed. ->tipIf you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. +>tip If you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. After clicking 'OK', Expression Blend will generate the default value for the selected __Style__ in the __Resources__ section of your User Control. The properties available for the style will be loaded in the 'Properties' pane and you will be able to modify their default values. You can also edit the generated XAML in the XAML View or in Visual Studio. ->tipTo change the fill of the legend item's marker set the __MarkerFill__ property of the __CHhrtLegendItem__ through its __Style__. For the stroke of the marker use the __Stroke__ property of the __ChartLegendItem__. {% if site.site_name == 'Silverlight' %} +>tip To change the fill of the legend item's marker set the __MarkerFill__ property of the __CHhrtLegendItem__ through its __Style__. For the stroke of the marker use the __Stroke__ property of the __ChartLegendItem__. {% if site.site_name == 'Silverlight' %} If you go to the 'Resources' pane, you will see an editable list of resources generated together with the style and used by it. In this list you will find the brushes, styles and templates needed to change the visual appearance of the targeted control__.__Their names indicate to which part of the appearance they are assigned.{% endif %}{% if site.site_name == 'Silverlight' %} diff --git a/controls/radchart/styles-and-templates/styling-and-appearance-styling-chart-series.md b/controls/radchart/styles-and-templates/styling-and-appearance-styling-chart-series.md index 71701db03c..ab150618cc 100644 --- a/controls/radchart/styles-and-templates/styling-and-appearance-styling-chart-series.md +++ b/controls/radchart/styles-and-templates/styling-and-appearance-styling-chart-series.md @@ -49,7 +49,7 @@ The second way is to define a style and set it through the __SeriesStyles__ comp >Using this type of styling only the series elements will get customized, the item labels and the legend items will remain with their default appearance. ->tipBy setting the __Styles__ this way, they will get applied to every series of this type. In order to use styles and apply them to certain series you can combine the two methods. This is done by setting them to the __SeriesDefinition.ItemStyle__ property for item-drawn series or the __SeriesDefinition.SeriesStyle__ property for self-drawn series. +>tip By setting the __Styles__ this way, they will get applied to every series of this type. In order to use styles and apply them to certain series you can combine the two methods. This is done by setting them to the __SeriesDefinition.ItemStyle__ property for item-drawn series or the __SeriesDefinition.SeriesStyle__ property for self-drawn series. * To create a style for the __Self-Drawing Series__ (Line, StackedLine, Spline, StackedSpline, Area, StackedArea, StackedArea100, SplineArea, StackedSplineArea, StackedSplineArea100, Range, SplineRange) you have to create a style that targets the __SelfDrawingSeries__ class in the __Telerik.Windows.Controls.Charting__ namespace. @@ -125,7 +125,7 @@ Here is an example: ![{{ site.framework_name }} RadChart ](images/RadChart_StylingChartSeries_03.png) ->tipTo learn how to change the foreground of the item's label when using styles take a look at the [Styling the Item Labels]({%slug radchart-styling-and-appearance-styling-item-labels%}) topic. +>tip To learn how to change the foreground of the item's label when using styles take a look at the [Styling the Item Labels]({%slug radchart-styling-and-appearance-styling-item-labels%}) topic. ## Styling Series via PaletteBrushes @@ -138,7 +138,7 @@ The __RadChart__ exposes two __BrushCollections__: ->tipThe __PaletteBrushes__ property is independent of the series type. +>tip The __PaletteBrushes__ property is independent of the series type. >The __PaletteBrush__ collection on the __ChartArea__ level takes precedence over the one on the __RadChart__ level and the latter takes precedence over the theme resources. @@ -226,7 +226,7 @@ or ![{{ site.framework_name }} RadChart ](images/RadChart_StylingChartSeries_05.png) ->tipYou can set the __PaletteBrushesUseSolidColors__ property to true so that those Themes that have *Gradient* colors will have their Gradients set to the SolidColors as given in the Palette. Such themes are *Vista*, *Summer* and *Windows7*. For comparison you may take a look at the following two pictures: +>tip You can set the __PaletteBrushesUseSolidColors__ property to true so that those Themes that have *Gradient* colors will have their Gradients set to the SolidColors as given in the Palette. Such themes are *Vista*, *Summer* and *Windows7*. For comparison you may take a look at the following two pictures: * PaletteBrushesUseSolidColors = *False* and Theme is set to Vista: @@ -276,7 +276,7 @@ Here is an example: ->tipThe Default Style is different for RadChart with version older than Q1 2010. +>tip The Default Style is different for RadChart with version older than Q1 2010. diff --git a/controls/radchart/styles-and-templates/styling-and-appearance-styling-chart-title.md b/controls/radchart/styles-and-templates/styling-and-appearance-styling-chart-title.md index 1adeb9f71d..3fc3a1200a 100644 --- a/controls/radchart/styles-and-templates/styling-and-appearance-styling-chart-title.md +++ b/controls/radchart/styles-and-templates/styling-and-appearance-styling-chart-title.md @@ -38,7 +38,7 @@ When working in Expression Blend, the namespaces that are needed will be added a Load your project in Expression Blend and open the User Control that holds the __RadChart__. You have to use a dummy control in order to get the default style. To create one find the __ChartTitle__ control in the 'Assets' pane and draw one on the art board. In the 'Objects and Timeline' pane select the __ChartTitle__, you've drawn and from the menu choose *Object -> Edit Style -> Edit a Copy*. You will be prompted for the name of the style and where to be placed. ->tipIf you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. +>tip If you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. After clicking 'OK', Expression Blend will generate the default style of the __ChartTitle__ control in the __Resources__ section of your User Control. The properties available for the style will be loaded in the 'Properties' pane and you will be able to modify their default values. You can also edit the generated XAML in the XAML View or in Visual Studio.{% if site.site_name == 'Silverlight' %} diff --git a/controls/radchart/styles-and-templates/styling-and-appearance-styling-item-labels.md b/controls/radchart/styles-and-templates/styling-and-appearance-styling-item-labels.md index f4c13d249a..ed12ab828a 100644 --- a/controls/radchart/styles-and-templates/styling-and-appearance-styling-item-labels.md +++ b/controls/radchart/styles-and-templates/styling-and-appearance-styling-item-labels.md @@ -18,11 +18,11 @@ The item labels are part of the series definition items and are represented by t Open your __RadChart__ project in Expression Blend and select the __RadChart__ you want to modify. On the same scene you should place a __SeriesItemLabel__ control, that will be used as a dummy. To do so choose the 'Assets' tab. From the *Controls -> All* section select the __SeriesItemLabel__ control. With your mouse create a new instance of the control on the scene. Now select the newly created control and from the menu select *Object -> Edit Style -> Edit Copy*. You will be prompted for the name of the style and where to be placed within your application. ->tipIf you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. +>tip If you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. After clicking the OK button, a style with target type __SeriesItemLabel__ will be created and the properties for this type will be loaded in the 'Properties' pane. Modify them untill you get the desired appearance. ->tipYou can also set the __Style__ for the __Label's__ border via the __LabelStyle__ property and the __Style__ for the __Label's__ connector via the __ConnectorStyle__ property. +>tip You can also set the __Style__ for the __Label's__ border via the __LabelStyle__ property and the __Style__ for the __Label's__ connector via the __ConnectorStyle__ property. You can modify every one of the properties available for the styles. After that set the created style to the __DefaultSeriesDefinition__ of your __RadChart__ and delete the dummy control. diff --git a/controls/radchart/styles-and-templates/styling-and-appearance-styling-no-data-control.md b/controls/radchart/styles-and-templates/styling-and-appearance-styling-no-data-control.md index dbeb62bba0..253984072f 100644 --- a/controls/radchart/styles-and-templates/styling-and-appearance-styling-no-data-control.md +++ b/controls/radchart/styles-and-templates/styling-and-appearance-styling-no-data-control.md @@ -38,7 +38,7 @@ When working in Expression Blend, the namespaces that are needed will be added a Load your project in Expression Blend and open the User Control that holds the __RadChart__. You have to use a dummy control in order to get the default style. To create one find the __NoDataControl__ control in the 'Assets' pane and draw one on the art board. In the 'Objects and Timeline' pane select the __NoDataControl__, you've drawn and from the menu choose *Object -> Edit Style -> Edit a Copy*. You will be prompted for the name of the style and where to be placed. ->tipIf you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. +>tip If you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. After clicking 'OK', Expression Blend will generate the default style of the __NoDataControl__ control in the __Resources__ section of your User Control. The properties available for the style will be loaded in the 'Properties' pane and you will be able to modify their default values. You can also edit the generated XAML in the XAML View or in Visual Studio.{% if site.site_name == 'Silverlight' %} diff --git a/controls/radchart/styles-and-templates/styling-and-appearance-styling-plot-area.md b/controls/radchart/styles-and-templates/styling-and-appearance-styling-plot-area.md index 28090ec5b9..741bde5344 100644 --- a/controls/radchart/styles-and-templates/styling-and-appearance-styling-plot-area.md +++ b/controls/radchart/styles-and-templates/styling-and-appearance-styling-plot-area.md @@ -18,7 +18,7 @@ The plot area is part of the chart area and is represented by the __ClipPanel__ Open your __RadChart__ project in Expression Blend and select the __RadChart__ you want to modify. On the same scene you should place a __ClipPanel__ control, that will be used as a dummy. To do so choose the 'Assets' tab. From the *Controls -> All* section select the __ClipPanel__ control. With your mouse create a new instance of the control on the scene. Now select the newly created control and from the menu select *Object -> Edit Style -> Create Empty*. You will be prompted for the name of the style and where to be placed within your application. ->tipIf you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. +>tip If you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. After clicking the "OK" button, a style with target type __ClipPanel__ will be created. In the 'Properties' pane the properties available for the style will be loaded. You can modify them to get the desired appearance. diff --git a/controls/radchart/styles-and-templates/styling-and-appearance-styling-strip-lines.md b/controls/radchart/styles-and-templates/styling-and-appearance-styling-strip-lines.md index e656bba9ba..e8e4c4af3e 100644 --- a/controls/radchart/styles-and-templates/styling-and-appearance-styling-strip-lines.md +++ b/controls/radchart/styles-and-templates/styling-and-appearance-styling-strip-lines.md @@ -58,7 +58,7 @@ To be able to modify the colors of these lines you should use the following Styl ->tipYou should turn StripLines visibility on so that you will be able to see them. +>tip You should turn StripLines visibility on so that you will be able to see them. diff --git a/controls/radchart/styles-and-templates/styling-the-axes/styling-and-apearance-styling-gridline.md b/controls/radchart/styles-and-templates/styling-the-axes/styling-and-apearance-styling-gridline.md index 947226974a..7a69c2d5fa 100644 --- a/controls/radchart/styles-and-templates/styling-the-axes/styling-and-apearance-styling-gridline.md +++ b/controls/radchart/styles-and-templates/styling-the-axes/styling-and-apearance-styling-gridline.md @@ -32,7 +32,7 @@ Open your __RadChart__ project in Expression Blend. To add the dummy __Line__ co To go back to the design view select *View -> Active Document View -> Design View* from the menu. In the 'Objects and Timeline' pane select the newly created __Line__ control. And select *Object -> Edit Style -> Create Empty* from the menu*. *You will be prompted for the name of the style and where to be placed within your application. ->tipIf you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. +>tip If you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. After clicking the OK button, a style with target type __Line__ will be created and the properties for this type will be loaded in the 'Properties' pane. Modify them until you get the desired appearance. @@ -51,7 +51,7 @@ After finishing with the changes, it is time to set the style. It can be set onl ->tipTo show the grid lines for a particular axis you have to set its __MajorGridLinesVisibility__ property to __Visible__. Read more about grid lines [here]({%slug radchart-features-axes-striplines-and-gridlines%}). +>tip To show the grid lines for a particular axis you have to set its __MajorGridLinesVisibility__ property to __Visible__. Read more about grid lines [here]({%slug radchart-features-axes-striplines-and-gridlines%}). Here is a snapshot of the sample result. diff --git a/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-item-label.md b/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-item-label.md index 71ffac5a30..2347b2f878 100644 --- a/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-item-label.md +++ b/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-item-label.md @@ -14,7 +14,7 @@ position: 6 ## ->tipThe approach below allow you more completely to change the appearance of the axis item label, but if you want to change only the foreground of it, you can use the __AxisForeground__ property of the __RadChart.Note__ that the value of this property will get applied to all of the axis item labels and all of the axis titles. +>tip The approach below allow you more completely to change the appearance of the axis item label, but if you want to change only the foreground of it, you can use the __AxisForeground__ property of the __RadChart.Note__ that the value of this property will get applied to all of the axis item labels and all of the axis titles. The axis item labels are part of the chart axis and are represented by the __TextBlock__ control. To create a style for them in Expression Blend use a dummy control and after modifying it, set it to the __AxisStyles__ complex property of the __Axis__. @@ -34,7 +34,7 @@ Open your __RadChart__ project in Expression Blend. To add the dummy __TextBlock To go back to the design view select *View -> Active Document View -> Design View* from the menu. In the 'Objects and Timeline' pane select the newly created __TextBlock__ control. And select *Object -> Edit Style -> Create Empty* from the menu*. *You will be prompted for the name of the style and where to be placed within your application. ->tipIf you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. +>tip If you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. After clicking the OK button, a style with target type __TextBlock__ will be created and the properties for this type will be loaded in the 'Properties' pane. Modify them until you get the desired appearance. diff --git a/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-line.md b/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-line.md index d18f9239c4..7f3837d52b 100644 --- a/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-line.md +++ b/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-line.md @@ -12,7 +12,7 @@ position: 1 ->tipThe approach below allow you more completely to change the appearance of the axis lines, but if you want to change only the color of it, you can use the __AxisElementBrush__ property of the __RadChart.Note__ that the value of this property will get applied to all of the axes and all of the tick lines as well. +>tip The approach below allow you more completely to change the appearance of the axis lines, but if you want to change only the color of it, you can use the __AxisElementBrush__ property of the __RadChart.Note__ that the value of this property will get applied to all of the axes and all of the tick lines as well. The axis line is part of the chart axis and is represented by the __Line__ control. To create a style for it in Expression Blend use a dummy control and after modifying it, set it to the __AxisStyles__ complex property of the __Axis__. @@ -32,7 +32,7 @@ Open your __RadChart__ project in Expression Blend. To add the dummy __Line__ co To go back to the design view select *View -> Active Document View -> Design View* from the menu. In the 'Objects and Timeline' pane select the newly created __Line__ control. And from the menu select *Object -> Edit Style -> Create Empty. *You will be prompted for the name of the style and where to be placed within your application. ->tipIf you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. +>tip If you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. After clicking the OK button, a style with target type __Line__ will be created and the properties for this type will be loaded in the 'Properties' pane. Modify them until you get the desired appearance. @@ -84,7 +84,7 @@ Sometimes, when clicking on the XAxis label, one may need to alter some of the a - + diff --git a/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-minor-tick.md b/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-minor-tick.md index fd6ed9d4b0..af0bd85f53 100644 --- a/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-minor-tick.md +++ b/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-minor-tick.md @@ -29,7 +29,7 @@ Open your __RadChart__ project in Expression Blend. To add the dummy __Line__ co To go back to the design view select *View -> Active Document View -> Design View* from the menu. In the 'Objects and Timeline' pane select the newly created __Line__ control. And select *Object -> Edit Style -> Create Empty* from the menu*. *You will be prompted for the name of the style and where to be placed within your application. ->tipIf you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. +>tip If you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. After clicking the OK button, a style with target type __Line__ will be created and the properties for this type will be loaded in the 'Properties' pane. Modify them until you get the desired appearance. @@ -50,9 +50,9 @@ After finishing with the changes, it is time to set the style to the __MinorTick ->tipSetting the styles for the y-axis is done analogically via the __AxisY__ property of the __ChartArea__. +>tip Setting the styles for the y-axis is done analogically via the __AxisY__ property of the __ChartArea__. ->tipTo learn how to style the primary ticks take a look at the [Styling the Axis Tick]({%slug radchart-styling-and-appearance-styling-axis-tick%}) topic. +>tip To learn how to style the primary ticks take a look at the [Styling the Axis Tick]({%slug radchart-styling-and-appearance-styling-axis-tick%}) topic. ![{{ site.framework_name }} RadChart ](images/RadChart_StylingAxisMinorTickLines_03.png) Here is the final XAML for the __Styles:__ diff --git a/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-tick.md b/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-tick.md index 5e5a6ee4a2..aef5685759 100644 --- a/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-tick.md +++ b/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-tick.md @@ -14,7 +14,7 @@ position: 2 ## ->tipThe approach below allow you more completely to change the appearance of the tick lines, but if you want to change only the color of it, you can use the __AxisElementBrush__ property of the __RadChart.Note__ that the value of this property will get applied to all of the axes and all of the tick lines as well. +>tip The approach below allow you more completely to change the appearance of the tick lines, but if you want to change only the color of it, you can use the __AxisElementBrush__ property of the __RadChart.Note__ that the value of this property will get applied to all of the axes and all of the tick lines as well. The axis tick lines are part of the chart axis and are represented by the __Line__ control. To create a style for them in Expression Blend use a dummy control and after modifying it, set it to the __AxisStyles__ complex property of the __Axis__. @@ -33,7 +33,7 @@ Open your __RadChart__ project in Expression Blend. To add the dummy __Line__ co To go back to the design view select *View -> Active Document View -> Design View* from the menu. In the 'Objects and Timeline' pane select the newly created __Line__ control. And select *Object -> Edit Style -> Create Empty* from the menu*. *You will be prompted for the name of the style and where to be placed within your application. ->tipIf you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. +>tip If you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. After clicking the OK button, a style with target type __Line__ will be created and the properties for this type will be loaded in the 'Properties' pane. Modify them until you get the desired appearance. @@ -54,9 +54,9 @@ After finishing with the changes, it is time to set the style to the __TickLineS ->tipSetting the styles for the y-axis is done analogically via the __AxisY__ property of the __ChartArea__. +>tip Setting the styles for the y-axis is done analogically via the __AxisY__ property of the __ChartArea__. ->tipTo learn how to style the minor ticks take a look at the [Styling the Minor Tick]({%slug radchart-styling-and-appearance-styling-axis-minor-tick%}) topic. +>tip To learn how to style the minor ticks take a look at the [Styling the Minor Tick]({%slug radchart-styling-and-appearance-styling-axis-minor-tick%}) topic. ![{{ site.framework_name }} RadChart ](images/RadChart_StylingAxisTicks_03.png) Here is the final XAML for the __Styles__: diff --git a/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-title.md b/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-title.md index d2c7e7f23c..dc266946c7 100644 --- a/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-title.md +++ b/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-axis-title.md @@ -14,7 +14,7 @@ position: 7 ## ->tipThe approach below allow you more completely to change the appearance of the axis item label, but if you want to change only the foreground of it, you can use the __AxisForeground__ property of the __RadChart.Note__ that the value of this property will get applied to all of the axis item labels and all of the axis titles. +>tip The approach below allow you more completely to change the appearance of the axis item label, but if you want to change only the foreground of it, you can use the __AxisForeground__ property of the __RadChart.Note__ that the value of this property will get applied to all of the axis item labels and all of the axis titles. The axis title is part of the chart axis and is represented by the __AxisTitle__ control. To style it in Expression Blend use a dummy control to create the style and after modifying it, set it to the __RadChart__. @@ -22,7 +22,7 @@ Open your __RadChart__ project in Expression Blend. On the same scene you should With your mouse create a new instance of the control on the scene. Now select the newly created control and select *Object -> Edit Style -> Edit Copy* from the menu. You will be prompted for the name of the style and where to be placed within your application. ->tipIf you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. +>tip If you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. After clicking the OK button a style with target type __AxisTitle__ will be created and the properties for this type will be loaded in the 'Properties' pane. Modify them until you get the desired appearance. @@ -45,7 +45,7 @@ After finishing with the changes it is time to set the style. It can be set only ->tipThe title for a particular axis can be set through its __Title__ property. Read more about axes [here]({%slug radchart-features-axes-overview%}). +>tip The title for a particular axis can be set through its __Title__ property. Read more about axes [here]({%slug radchart-features-axes-overview%}). ![{{ site.framework_name }} RadChart ](images/RadChart_StylingAxisTitle_10.png) diff --git a/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-stripline.md b/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-stripline.md index 824f1690f9..ed6be01476 100644 --- a/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-stripline.md +++ b/controls/radchart/styles-and-templates/styling-the-axes/styling-and-appearance-styling-stripline.md @@ -33,7 +33,7 @@ Open your __RadChart__ project in Expression Blend. To add the dummy __Rectangle To go back to the design view select *View -> Active Document View -> Design View* from the menu. In the 'Objects and Timeline' pane select the newly created __Rectangle__ control. And select *Object -> Edit Style -> Create Empty* from the menu*. *You will be prompted for the name of the style and where to be placed within your application. ->tipIf you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. +>tip If you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. After clicking the OK button, a style with target type __Rectangle__ will be created and the properties for this type will be loaded in the 'Properties' pane. Modify them until you get the desired appearance. @@ -52,7 +52,7 @@ After finishing with the changes it is time to set the style. It can be set only ->tipTo show the strip lines for a particular axis you have to set its __StripLinesVisibility__ property to __Visible__. Read more about strip lines [here]({%slug radchart-features-axes-striplines-and-gridlines%}). +>tip To show the strip lines for a particular axis you have to set its __StripLinesVisibility__ property to __Visible__. Read more about strip lines [here]({%slug radchart-features-axes-striplines-and-gridlines%}). Here is a snapshot of the sample result: ![{{ site.framework_name }} RadChart ](images/RadChart_StylingAxisStripLines_04.png) diff --git a/controls/radchart/styles-and-templates/templating-point-marks.md b/controls/radchart/styles-and-templates/templating-point-marks.md index 73288ff4ba..bb3ffec34f 100644 --- a/controls/radchart/styles-and-templates/templating-point-marks.md +++ b/controls/radchart/styles-and-templates/templating-point-marks.md @@ -16,11 +16,11 @@ position: 13 There is a set of predefined __PointMark__ shapes, but you are allowed to create your own via templating the __PointMark__ control. To learn more about the predefined shapes and how to manipulate them take a look at the [Chart Point Marks]({%slug radchart-features-chart-point-marks%}) topic. ->tipTo learn more about styling the point marks read [here]({%slug radchart-styling-and-appearance-styling-point-marks%}). +>tip To learn more about styling the point marks read [here]({%slug radchart-styling-and-appearance-styling-point-marks%}). To template and change the shape of the mark point you have to use Expression Blend. Open the UserControl containing your __RadChart__ in it. You have to use a dummy control to create a template for the point mark. Go to the Assets tab and from Controls -> All select the __PointMark__ control. Draw an instance of it on the scene, next to your __RadChart__ control. Select the __PointMark__ control that you've just created and right-click on it. Form the context menu select Edit Template -> Edit a Copy. You will be prompted for the name of the style and where to be placed within your application. ->tipIf you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. +>tip If you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. After clicking the OK button, a style with target type __PointMark__ will be created and the Expression Blend will bring you into editing the control's template. @@ -68,7 +68,7 @@ You can see that the __Data__ property of the __Path__ is not set. Create the da ->tipTo learn more about creating shapes via the Path class in {% if site.site_name == 'Silverlight' %}Silverlight{% if site.site_name == 'WPF' %}WPF{% endif %}{% endif %} read [here](http://msdn.microsoft.com/en-us/library/cc189041%28VS.95%29.aspx)[here](http://msdn.microsoft.com/en-us/library/ms752293.aspx). +>tip To learn more about creating shapes via the Path class in {% if site.site_name == 'Silverlight' %}Silverlight{% if site.site_name == 'WPF' %}WPF{% endif %}{% endif %} read [here](http://msdn.microsoft.com/en-us/library/cc189041%28VS.95%29.aspx)[here](http://msdn.microsoft.com/en-us/library/ms752293.aspx). After that set the created __PointMark__ style to the __DefaultSeriesDefinition__ of your __RadChart__ and delete the dummy controls. diff --git a/controls/radchartview/styles-and-templates/customizing-cartesianchart-series.md b/controls/radchartview/styles-and-templates/customizing-cartesianchart-series.md index a18e8ec8ba..715be76832 100644 --- a/controls/radchartview/styles-and-templates/customizing-cartesianchart-series.md +++ b/controls/radchartview/styles-and-templates/customizing-cartesianchart-series.md @@ -304,7 +304,7 @@ This series expose the following styling properties: ![radchartview-styles-and-templates-Area Series-Range Area Shape Style](images/radchartview-styles-and-templates-RangeAreaSeries-AreaShapeStyle.png) ->tipRangeSeries expose several additional properties you can use to style its appearance: __Stroke__, __StrokeThickness__, __Fill__, __DashArray__. +>tip RangeSeries expose several additional properties you can use to style its appearance: __Stroke__, __StrokeThickness__, __Fill__, __DashArray__. ### StepAreaSeries diff --git a/controls/radchartview/styles-and-templates/customizing-polarchart-series.md b/controls/radchartview/styles-and-templates/customizing-polarchart-series.md index ad293ddc7c..acf1b3db71 100644 --- a/controls/radchartview/styles-and-templates/customizing-polarchart-series.md +++ b/controls/radchartview/styles-and-templates/customizing-polarchart-series.md @@ -115,7 +115,7 @@ This series expose the __DefaultVisualStyle__ property. It is of type __Style__ ``` ->tipSince __Q1 2014__ all series exposing the __DefaultVisualStyle__ property, also expose the __DefaultVisualStyleSelector__ property. It is of type [StyleSelector](http://msdn.microsoft.com/en-us/library/system.windows.controls.styleselector(v=vs.110).aspx) and gets or sets custom style-selection logic for a style that can be applied to each generated element. +>tip Since __Q1 2014__ all series exposing the __DefaultVisualStyle__ property, also expose the __DefaultVisualStyleSelector__ property. It is of type [StyleSelector](http://msdn.microsoft.com/en-us/library/system.windows.controls.styleselector(v=vs.110).aspx) and gets or sets custom style-selection logic for a style that can be applied to each generated element. ![radchartview-styles-and-templates-Polar Point Series-Default Visual Style](images/radchartview-styles-and-templates-PolarPointSeries-DefaultVisualStyle.png) @@ -136,7 +136,7 @@ This series expose the __DefaultVisualStyle__ property. It is of type __Style__ ``` ->tipSince __Q1 2014__ all series exposing the __DefaultVisualStyle__ property, also expose the __DefaultVisualStyleSelector__ property. It is of type [StyleSelector](http://msdn.microsoft.com/en-us/library/system.windows.controls.styleselector(v=vs.110).aspx) and gets or sets custom style-selection logic for a style that can be applied to each generated element. +>tip Since __Q1 2014__ all series exposing the __DefaultVisualStyle__ property, also expose the __DefaultVisualStyleSelector__ property. It is of type [StyleSelector](http://msdn.microsoft.com/en-us/library/system.windows.controls.styleselector(v=vs.110).aspx) and gets or sets custom style-selection logic for a style that can be applied to each generated element. ![radchartview-styles-and-templates-Radar Point Series-Default Visual Style](images/radchartview-styles-and-templates-RadarPointSeries-DefaultVisualStyle.png) diff --git a/controls/radcombobox/features/edit-modes.md b/controls/radcombobox/features/edit-modes.md index f0a39ea813..7df8cfe9b5 100644 --- a/controls/radcombobox/features/edit-modes.md +++ b/controls/radcombobox/features/edit-modes.md @@ -22,11 +22,11 @@ In order to make your __RadComboBox__ editable, you should set its __IsEditable_ ``` ->tipWhen making your __RadComboBox__ editable, you could better distinguish the benefit of the [AutoComplete]({%slug radcombobox-features-autocomplete%}). +>tip When making your __RadComboBox__ editable, you could better distinguish the benefit of the [AutoComplete]({%slug radcombobox-features-autocomplete%}). By default, the __RadComboBox__ is non-editable. Which means that its __Input Area__ is hidden. ->tipIf your __RadComboBox__ is non-editable, you could still benefit from the [AutoComplete]({%slug radcombobox-features-autocomplete%}) feature, but instead of autocomplete your items will be auto-selected. +>tip If your __RadComboBox__ is non-editable, you could still benefit from the [AutoComplete]({%slug radcombobox-features-autocomplete%}) feature, but instead of autocomplete your items will be auto-selected. >When your __RadComboBox__ is editable and has ItemTemplate defined, you should set the [telerik:TextSearch.TextPath]({%slug radcombobox-features-selection%}) property to point to the required property of the bussiness object which will be shown in the input field. @@ -42,7 +42,7 @@ __Example 1: Setting the IsEditable and IsReadOnly to True__ ``` ->tipSetting the __RadComboBox__'s __IsReadOnly__ property to __True__ will affect the __RadComboBox__ only when it is __editable__. +>tip Setting the __RadComboBox__'s __IsReadOnly__ property to __True__ will affect the __RadComboBox__ only when it is __editable__. ## StaysOpenOnEdit diff --git a/controls/radcombobox/features/filtering.md b/controls/radcombobox/features/filtering.md index 9406ab7f00..200bf07805 100644 --- a/controls/radcombobox/features/filtering.md +++ b/controls/radcombobox/features/filtering.md @@ -53,7 +53,7 @@ Start your demo and write "al" in the __input box__. Now only items containing t ![{{ site.framework_name }} RadComboBox Items Only Containing "al"](images/RadComboBox_Features_Filtering_020.png) ->importantPlease, notice that if there aren't any filtered items and you move the focus out of __RadComboBox__ the entered search text will be cleared. In order to prevent the text from clearing you need to set the __UpdateTextOnLostFocus__ property which was introduced with the SP1 Q2 2015 version of UI for {% if site.site_name == 'WPF' %}WPF{% endif %}{% if site.site_name == 'Silverlight' %}Silverlight{% endif %} to __False__. +>important Please, notice that if there aren't any filtered items and you move the focus out of __RadComboBox__ the entered search text will be cleared. In order to prevent the text from clearing you need to set the __UpdateTextOnLostFocus__ property which was introduced with the SP1 Q2 2015 version of UI for {% if site.site_name == 'WPF' %}WPF{% endif %}{% if site.site_name == 'Silverlight' %}Silverlight{% endif %} to __False__. >The text filtering feature of __RadComboBox__ works only while the drop-down is open (it filters the visible items in the drop-down). You can also set the __OpenDropDownOnFocus__ property to __True__ which automatically opens the drop-drop when the controls is focused. @@ -72,7 +72,7 @@ Start your demo and write "al" in the __input box__. Now only items, which text ![{{ site.framework_name }} RadComboBox Items Only Starting with "al"](images/RadComboBox_Features_Filtering_030.png) ->importantWhen RadComboBox is virtualized the filtering is not supported. +>important When RadComboBox is virtualized the filtering is not supported. ## See Also diff --git a/controls/radcombobox/features/keyboard-support.md b/controls/radcombobox/features/keyboard-support.md index 13032ca7a1..edf93f4a63 100644 --- a/controls/radcombobox/features/keyboard-support.md +++ b/controls/radcombobox/features/keyboard-support.md @@ -36,7 +36,7 @@ Using the keyboard you can perform some of the most common tasks. This section d * When the dropdown of the __RadComboBox__ is __closed__, then pressing the __Home\End__ keys will change the __selected item__ to the first\last item in the list. ->tipPressing the __Home\End__ keys will affect the __selected\highlighted__ item only when the __IsEditable__ property is set to __False__. +>tip Pressing the __Home\End__ keys will affect the __selected\highlighted__ item only when the __IsEditable__ property is set to __False__. * __PageUp\PageDown__ - the __PageUp__ and __PageDown__ keys have one main function: pressing __PageUp__ or __PageDown__ will open the dropdown when it is __closed__. If the dropdown of the __RadComboBox__ is __opened__, then pressing any of these keys will change the __highlighted item__. diff --git a/controls/radcombobox/howto/create-a-watermark.md b/controls/radcombobox/howto/create-a-watermark.md index a83e19ac6a..61ffd67fdb 100644 --- a/controls/radcombobox/howto/create-a-watermark.md +++ b/controls/radcombobox/howto/create-a-watermark.md @@ -28,7 +28,7 @@ __Example 1: Setting the EmptyText property__ ![NonEditable RadComboBox with EmptyText displayed](images/ComboBox_EmptyText_2.png) ->tipIf the __IsEditable__ property of the RadComboBox is set to __True__ and the control has focus the __EmptyText__ is not displayed. +>tip If the __IsEditable__ property of the RadComboBox is set to __True__ and the control has focus the __EmptyText__ is not displayed. ## EmptySelectionBoxTemplate @@ -53,4 +53,4 @@ __Example 2: Set the EmptySelectionBoxTemplate property__ #### __Figure 2: RadComboBox with EmptySelectionBoxTemplate in the Office2016 theme__ ![RadComboBox with EmptySelectionBoxTemplate](images/ComboBox_EmptySelectionBoxTemplate.png) ->tipThe __EmptySelectionBoxTemplate__ property only works if the RadComboBox is in non-editable mode, i.e its __IsEditable__ property is set to __False__. Otherwise, the __EmptyText__ will be applied. +>tip The __EmptySelectionBoxTemplate__ property only works if the RadComboBox is in non-editable mode, i.e its __IsEditable__ property is set to __False__. Otherwise, the __EmptyText__ will be applied. diff --git a/controls/radcombobox/howto/open-dropdown-get-focus.md b/controls/radcombobox/howto/open-dropdown-get-focus.md index 5bd97564d2..373f5382cf 100644 --- a/controls/radcombobox/howto/open-dropdown-get-focus.md +++ b/controls/radcombobox/howto/open-dropdown-get-focus.md @@ -18,7 +18,7 @@ __RadComboBox__'s API gives you the ability to open the __DropDown__ when the co ``` ->tipThe default value of the __RadComboBox__'s __OpenDropDownOnFocus__ property is __False__. +>tip The default value of the __RadComboBox__'s __OpenDropDownOnFocus__ property is __False__. ## See Also diff --git a/controls/radcombobox/howto/set-character-casing.md b/controls/radcombobox/howto/set-character-casing.md index ad7ef5672d..07b6f964d7 100644 --- a/controls/radcombobox/howto/set-character-casing.md +++ b/controls/radcombobox/howto/set-character-casing.md @@ -108,4 +108,4 @@ Finally set the property in XAML. ``` ->tipNote that you have to set the __RadComboBox__'s __IsEditable__ property to __True__. +>tip Note that you have to set the __RadComboBox__'s __IsEditable__ property to __True__. diff --git a/controls/radcombobox/howto/set-max-length-input-area.md b/controls/radcombobox/howto/set-max-length-input-area.md index a5babf3406..46428883e1 100644 --- a/controls/radcombobox/howto/set-max-length-input-area.md +++ b/controls/radcombobox/howto/set-max-length-input-area.md @@ -192,7 +192,7 @@ Finally set the property in XAML: ``` ->tipNote that you have to set the __RadComboBox__'s __IsEditable__ property to __True__. +>tip Note that you have to set the __RadComboBox__'s __IsEditable__ property to __True__. ## See Also * [Enable\Disable RadComboBoxItems]({%slug radcombobox-howto-enable-disable-radcombobox-items%}) diff --git a/controls/radcombobox/howto/virtualization.md b/controls/radcombobox/howto/virtualization.md index baf5780c80..06fb22c603 100644 --- a/controls/radcombobox/howto/virtualization.md +++ b/controls/radcombobox/howto/virtualization.md @@ -29,7 +29,7 @@ In some scenarios it is required to load thousands of items in a __RadComboBox__ ``` ->importantWhen RadComboBox is virtualized the filtering is not supported. +>important When RadComboBox is virtualized the filtering is not supported. ## See Also diff --git a/controls/radcontextmenu/events/overview.md b/controls/radcontextmenu/events/overview.md index 5aa750b702..d8c834e384 100644 --- a/controls/radcontextmenu/events/overview.md +++ b/controls/radcontextmenu/events/overview.md @@ -14,7 +14,7 @@ This topic covers the specific events exposed by the __RadContextMenu__ control. The __RadContextMenu__ is an __ItemsControl__. Almost all of the exposed events are inherited from the __ItemsControl__ class. The __RadContextMenu__ adds several additional events for the developer. ->tipTo learn more about the events raised by the __RadMenuItem__, please take a look at the [RadMenu's help]({%slug radmenu-overview%}). +>tip To learn more about the events raised by the __RadMenuItem__, please take a look at the [RadMenu's help]({%slug radmenu-overview%}). The __RadContextMenu__ control raises the following specific event: diff --git a/controls/radcontextmenu/features/opening-on-specific-event.md b/controls/radcontextmenu/features/opening-on-specific-event.md index 27792f0007..c0965a6109 100644 --- a/controls/radcontextmenu/features/opening-on-specific-event.md +++ b/controls/radcontextmenu/features/opening-on-specific-event.md @@ -12,7 +12,7 @@ position: 1 Setting the __EventName__ property will make __RadContextMenu__ to listen for a particular event. When this event occurs, the __RadContextMenu__ will open. For example, you may want to attach a context menu to a __Button__ and the context menu to open whenever the __Button__ gets clicked. This can be done by just setting the __EventName__ property to the name of the event, in this case "__Click__". ->tip__RadContextMenu__ can listen for any of the events of the control to which it is attached. +>tip __RadContextMenu__ can listen for any of the events of the control to which it is attached. diff --git a/controls/radcontextmenu/features/placement.md b/controls/radcontextmenu/features/placement.md index 05dddbb669..5076ca45d5 100644 --- a/controls/radcontextmenu/features/placement.md +++ b/controls/radcontextmenu/features/placement.md @@ -51,7 +51,7 @@ Here is an example: The __PlacementRectangle__ is of type __Rect__ and specifies the position of the __RadContextMenu__. It can be combined with the __Placement__ property. ->tipProperties of type __Rect__ cannot be declared in-line because this is not supported. Set the property as attribute by passing the x, y, width and height parameters. The type converter will handle them from there. +>tip Properties of type __Rect__ cannot be declared in-line because this is not supported. Set the property as attribute by passing the x, y, width and height parameters. The type converter will handle them from there. diff --git a/controls/radcontextmenu/features/working-with-radcontext-menu.md b/controls/radcontextmenu/features/working-with-radcontext-menu.md index 68b9b4c1be..84ff80e79a 100644 --- a/controls/radcontextmenu/features/working-with-radcontext-menu.md +++ b/controls/radcontextmenu/features/working-with-radcontext-menu.md @@ -50,7 +50,7 @@ __Example 1: Attach a RadContextMenu__ >The class that represents the individual menu items is __Telerik.Windows.Controls.RadMenuItem__, located in the __Telerik.Windows.Controls.Navigation__ assembly. ->tipTo learn more about the __RadMenuItem__ control, please take a look at the [RadMenu's documentation]({%slug radmenu-overview%}). +>tip To learn more about the __RadMenuItem__ control, please take a look at the [RadMenu's documentation]({%slug radmenu-overview%}). The __RadContextMenu__ accepts __RadMenuItems__ as child items. Here is a sample declaration of several child menu items. @@ -114,7 +114,7 @@ __Example 3: Get clicked element__ Dim item As RadTreeViewItem = radContextMenu.GetClickedElement(Of RadTreeViewItem)() ``` ->tipA more complex example scenario can be found in the [Use RadContextMenu with a RadGridView]({%slug radcontextmenu-how-to-use-radcontextmenu-with-radgridview%}) topic and in the [Select the Clicked Item of a RadTreeView]({%slug radcontextmenu-how-to-select-the-clicked-item-of-radtreeview%}) topic. +>tip A more complex example scenario can be found in the [Use RadContextMenu with a RadGridView]({%slug radcontextmenu-how-to-use-radcontextmenu-with-radgridview%}) topic and in the [Select the Clicked Item of a RadTreeView]({%slug radcontextmenu-how-to-select-the-clicked-item-of-radtreeview%}) topic. ## See Also diff --git a/controls/radcontextmenu/populating-with-data/binding-to-dynamic-data.md b/controls/radcontextmenu/populating-with-data/binding-to-dynamic-data.md index d3f30d18da..4741a24b45 100644 --- a/controls/radcontextmenu/populating-with-data/binding-to-dynamic-data.md +++ b/controls/radcontextmenu/populating-with-data/binding-to-dynamic-data.md @@ -75,7 +75,7 @@ The __MenuItem__ class holds the information for the menu items. * __IsSeparator__: Indicates whether the item is a separator. ->tipTo learn more about the separator items and the __RadMenuItems__, please take a look at the [RadMenu help content]({%slug radmenu-overview%}). +>tip To learn more about the separator items and the __RadMenuItems__, please take a look at the [RadMenu help content]({%slug radmenu-overview%}). Next, we create a method to create the sample data to populate the RadContextMenu: diff --git a/controls/radcontextmenu/populating-with-data/data-binding-support-overview.md b/controls/radcontextmenu/populating-with-data/data-binding-support-overview.md index babab0291a..e219c05d7a 100644 --- a/controls/radcontextmenu/populating-with-data/data-binding-support-overview.md +++ b/controls/radcontextmenu/populating-with-data/data-binding-support-overview.md @@ -30,7 +30,7 @@ You can bind __RadContextMenu__ to the following types of data sources: To bind the __RadContextMenu__ to a collection of business objects, you should use its __ItemsSource__ property. If you want the changes to the collection to be automatically reflected to the __RadMenuItems__, the collection should implement the __INotifyCollectionChanged__ interface. There is a build-in collection in {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %}, which implements the __INotifyCollectionChanged__ interface and you could use it without making any effort - this is the generic __ObservableCollection__. However, to get a full benefit from the change notification support, your custom business objects should implement the __INotifyPropertyChanged__ interface. ->tipConsider using __ObservableCollection__ or one of the other existing collection classes like __List__, __Collection__, instead of implementing your own collection. If the scenario requires a custom collection to be implemented, use the __IList__ interface, which provides individual access by index to its items and the best performance. +>tip Consider using __ObservableCollection__ or one of the other existing collection classes like __List__, __Collection__, instead of implementing your own collection. If the scenario requires a custom collection to be implemented, use the __IList__ interface, which provides individual access by index to its items and the best performance. ## Data Templates @@ -38,7 +38,7 @@ The __ItemsSource__ property allows the __RadContextMenu__ to be bound to any co Besides the __RadContextMenu's ItemTemplate__ property, you could use the __DisplayMemberPath__ property for controlling the appearance of the created items. ->tipIf neither the __DisplayMemberPath__ nor the __ItemTemplate__ are set, then the content of the item would be set to the value returned by the __ToString()__ method of the business object. +>tip If neither the __DisplayMemberPath__ nor the __ItemTemplate__ are set, then the content of the item would be set to the value returned by the __ToString()__ method of the business object. ## See Also diff --git a/controls/radcontextmenu/populating-with-data/using-static-items.md b/controls/radcontextmenu/populating-with-data/using-static-items.md index 0e8f4a572d..f72f32ff0a 100644 --- a/controls/radcontextmenu/populating-with-data/using-static-items.md +++ b/controls/radcontextmenu/populating-with-data/using-static-items.md @@ -84,7 +84,7 @@ Here is a snapshot of the current result. ![{{ site.framework_name }} RadContextMenu with Static Items](images/RadContextMenu_Populating_with_Data_Static_Items_01.png) ->tipEach of the __RadMenuItems__ can have child items, that are defined in the same way. +>tip Each of the __RadMenuItems__ can have child items, that are defined in the same way. The __RadMenuItem__ exposes an __Icon__ property, which allows you to specify an icon for it. Here is an example. @@ -156,7 +156,7 @@ The __RadMenuItem__ exposes an __Icon__ property, which allows you to specify an ![{{ site.framework_name }} RadContextMenu with Items with Icons](images/RadContextMenu_Populating_with_Data_Static_Items_02.png) ->tipConsider declaring menu items in XAML instead of adding them by code whenever it's possible. This includes situations when you know what items you need at design time. +>tip Consider declaring menu items in XAML instead of adding them by code whenever it's possible. This includes situations when you know what items you need at design time. ## See Also diff --git a/controls/radcontextmenu/styles-and-templates/overview.md b/controls/radcontextmenu/styles-and-templates/overview.md index b5929fd873..c2fade2018 100644 --- a/controls/radcontextmenu/styles-and-templates/overview.md +++ b/controls/radcontextmenu/styles-and-templates/overview.md @@ -12,7 +12,7 @@ position: 0 This section is intended to give you a broad understanding of the possible ways by which you can change the visual appearance of the __RadContextMenu__. There is also comprehensive information about their __ControlTemplates__. You will need this information if you want to customize their appearance. ->tipTo learn about styling and templating the __RadMenuItem__, please take a look at the [Styles and Templates]({%slug radmenu-styling-and-appearance-styling-radmenuitem%}) section of the __RadMenu's__ help. +>tip To learn about styling and templating the __RadMenuItem__, please take a look at the [Styles and Templates]({%slug radmenu-styling-and-appearance-styling-radmenuitem%}) section of the __RadMenu's__ help. You can modify the look of the __RadContextMenu__ either by changing some of the resources exposed by the API, or by modifying their __ControlTemplates__. In the control template you are allowed to reorder the template parts and add your own elements. However, when changing the control template you should be careful to include all required parts. diff --git a/controls/radcontextmenu/styles-and-templates/styling-the-context-menu.md b/controls/radcontextmenu/styles-and-templates/styling-the-context-menu.md index 68023bb722..85f8efd7b8 100644 --- a/controls/radcontextmenu/styles-and-templates/styling-the-context-menu.md +++ b/controls/radcontextmenu/styles-and-templates/styling-the-context-menu.md @@ -10,7 +10,7 @@ position: 2 # Styling the RadContextMenu ->tipTo learn about styling and templating the __RadMenuItem__, please take a look at the [Styles and Templates]({%slug radmenu-styling-and-appearance-styling-radmenuitem%}) section of the __RadMenu's__ help. +>tip To learn about styling and templating the __RadMenuItem__, please take a look at the [Styles and Templates]({%slug radmenu-styling-and-appearance-styling-radmenuitem%}) section of the __RadMenu's__ help. The __RadContextMenu__ can be styled by creating an appropriate __Style__ and setting it to the __Style__ property of the control. @@ -26,11 +26,11 @@ This topic will show you how to perform the second one. To copy the default style, load your project in Expression Blend. As the attached __RadContextMenu__ is not visible in Expression Blend you have to use a dummy. From the 'Assets' pane select the __RadContextMenu__ control and draw one. In the 'Objects and Timeline' pane select it and from the menu choose *Object -> Edit Style -> Edit a Copy*. You will be prompted for the name of the style and where to be placed. ->tipIf you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. +>tip If you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. After clicking 'OK', Expression Blend will generate the default style of the __RadContextMenu__ control in the __Resources__ section of your User Control. The properties available for the style will be loaded in the 'Properties' pane and you will be able to modify their default values. You can also edit the generated XAML in the XAML View or in Visual Studio. ->tipAfter finishing with the style, you can set it to the desired __RadContextMenu__ control. Don't forget to delete the dummy you have drawn in the beginning. +>tip After finishing with the style, you can set it to the desired __RadContextMenu__ control. Don't forget to delete the dummy you have drawn in the beginning. If you go to the 'Resources' pane, you will see an editable list of resources generated together with the style and used by it. In this list you will find the brushes, styles and templates needed to change the visual appearance of the __RadContextMenu__. Their names indicate to which part of the __RadContextMenu__ appearance they are assigned. @@ -44,7 +44,7 @@ If you go to the 'Resources' pane, you will see an editable list of resources ge * __RadContextMenuStyle__ - the default Style generated for the __RadContextMenu__. ->tipChanging the value of the resources can be done by clicking on the color indicator or the icon next to them. +>tip Changing the value of the resources can be done by clicking on the color indicator or the icon next to them. Modify the resource to bring the desired appearance to the __RadContextMenu__. diff --git a/controls/radcontextmenu/styles-and-templates/template-structure.md b/controls/radcontextmenu/styles-and-templates/template-structure.md index 8e957d4386..83d899c1c2 100644 --- a/controls/radcontextmenu/styles-and-templates/template-structure.md +++ b/controls/radcontextmenu/styles-and-templates/template-structure.md @@ -12,7 +12,7 @@ position: 1 Like most WPF controls, the __RadContextMenu__ also allows you to template it in order to change the control from the inside. Except for templating the whole control, you can template parts of it or even independent controls related to it. ->tipFor more information about templating and how to modify the default templates of the controls from the UI for WPF suite read [Editing Control Templates article]({%slug styling-apperance-editing-control-templates%}) on this matter. +>tip For more information about templating and how to modify the default templates of the controls from the UI for WPF suite read [Editing Control Templates article]({%slug styling-apperance-editing-control-templates%}) on this matter. ## RadContextMenu Template Structure diff --git a/controls/raddataform/features/add-edit-delete-buttons.md b/controls/raddataform/features/add-edit-delete-buttons.md index e196a72179..78139ef0fe 100644 --- a/controls/raddataform/features/add-edit-delete-buttons.md +++ b/controls/raddataform/features/add-edit-delete-buttons.md @@ -70,7 +70,7 @@ Please note that when an Edit is started, the Navigation and AddNew commands get **RadDataForm** supports editing of types that do not implement the **IEditableObject** or **INotifyPropertyChanged** interfaces. Still, please note that in this case you cannot take advantage of the cancel edit feature and the **Cancel** button will not be enabled. ->tipYou can find a detailed explanation of how to implement the **IEditableObject** in this [MSDN article](http://msdn.microsoft.com/en-us/library/system.componentmodel.ieditableobject.aspx). +>tip You can find a detailed explanation of how to implement the **IEditableObject** in this [MSDN article](http://msdn.microsoft.com/en-us/library/system.componentmodel.ieditableobject.aspx). ### AutoEdit diff --git a/controls/raddatapager/localization.md b/controls/raddatapager/localization.md index 180cd1171c..08d5a8ed2e 100644 --- a/controls/raddatapager/localization.md +++ b/controls/raddatapager/localization.md @@ -23,7 +23,7 @@ Here is a list of the supported languages: * Dutch * Turkish ->tipTo learn more about the ways to localize the controls from the UI for {{ site.framework_name }} suite, please read the common topic on [Localization]({%slug common-localization%}). +>tip To learn more about the ways to localize the controls from the UI for {{ site.framework_name }} suite, please read the common topic on [Localization]({%slug common-localization%}). Below you may see the resource keys and the strings they are associated with. diff --git a/controls/raddatetimepicker/events.md b/controls/raddatetimepicker/events.md index 6e0fc8c24d..98162c2bd0 100644 --- a/controls/raddatetimepicker/events.md +++ b/controls/raddatetimepicker/events.md @@ -32,7 +32,7 @@ The **ParseDateTimeEventHandler** receives two arguments: ->tipSee an example of implementing custom parsing logic in your __RadDateTimePicker__ control by using the ParseDateTimeValue event [here]({%slug raddatetimepicker-how-to-implement-custom-parsing%}). +>tip See an example of implementing custom parsing logic in your __RadDateTimePicker__ control by using the ParseDateTimeValue event [here]({%slug raddatetimepicker-how-to-implement-custom-parsing%}). ## SelectionChanged diff --git a/controls/raddatetimepicker/features/date-items.md b/controls/raddatetimepicker/features/date-items.md index b885000df2..3bf407576c 100644 --- a/controls/raddatetimepicker/features/date-items.md +++ b/controls/raddatetimepicker/features/date-items.md @@ -32,7 +32,7 @@ Here is the result: The Next Month button is not active because of the __DisplayDateEnd__ property's value set in the example. ->tipYou can further restrict the input by indicating a selectable start and end dates. These dates will allow you to select only within a predefined range, but you would still have the ability to browse within the range of the display start and end dates. [Read more here]({%slug raddatetimepicker-features-selection%}) +>tip You can further restrict the input by indicating a selectable start and end dates. These dates will allow you to select only within a predefined range, but you would still have the ability to browse within the range of the display start and end dates. [Read more here]({%slug raddatetimepicker-features-selection%}) ## Using a default display date @@ -52,7 +52,7 @@ The result of this example will be that when you click on the __RadDateTimePicke ![{{ site.framework_name }} RadDateTimePicker with Custom DisplayDate](images/dateTimePicker_features_date_items_020.png) ->tipIf you set the __DisplayDate__ property to a value which is not in the range of the __DisplayDateStart__ and __DisplayDateEnd__ properties you will end up with a parse error exception. +>tip If you set the __DisplayDate__ property to a value which is not in the range of the __DisplayDateStart__ and __DisplayDateEnd__ properties you will end up with a parse error exception. ## See Also diff --git a/controls/raddatetimepicker/features/militaryparsing.md b/controls/raddatetimepicker/features/militaryparsing.md index 992c8bc342..5e519e27c0 100644 --- a/controls/raddatetimepicker/features/militaryparsing.md +++ b/controls/raddatetimepicker/features/militaryparsing.md @@ -36,7 +36,7 @@ The possible Date formats are: * ddMMMyyyy ->tipWhere MMM is the month with abbreviated name: MAR, JAN, FEB, etc. +>tip Where MMM is the month with abbreviated name: MAR, JAN, FEB, etc. The only possible Time format is: diff --git a/controls/raddatetimepicker/features/preview-tooltip.md b/controls/raddatetimepicker/features/preview-tooltip.md index 6b51be8135..1e8f1054c4 100644 --- a/controls/raddatetimepicker/features/preview-tooltip.md +++ b/controls/raddatetimepicker/features/preview-tooltip.md @@ -15,7 +15,7 @@ The __RadDateTimePicker__ control supports a preview tool tip. This feature help This tooltip acts like the autocomplete functionality. It is a suggestion tooltip, which tries to guess the input as you are typing it. The __RadDateTimePicker__ also shows you a validation __ErrorTooltip__ indicating that the input cannot be parsed as a valid __DateTime__. ->tipBy default, text input is enabled for the __RadDateTimePicker__, because you have the option to enter for instance "3 September" and the tooltip will update its value to suggest 9/3/2010. +>tip By default, text input is enabled for the __RadDateTimePicker__, because you have the option to enter for instance "3 September" and the tooltip will update its value to suggest 9/3/2010. >Additionally, the __ParseDateTimeValue__ event is raised on lost focus because text should be parsed after one has finished entering input and this is the intended default behavior. Read more [here]({%slug raddatetimepicker-events%}). @@ -45,7 +45,7 @@ Here is the result: ![{{ site.framework_name }} RadDateTimePicker Error Tooltip Content and Template](images/dateTimePicker_features_preview_tooltip_010.png) ->importantWhen using the above described approach you should know that setting the x:Name of the RadDateTimePicker to either __"DatePicker"__ or __"DateTimePicker"__ will lead to the ErrorTooltip not showing. The reason is that those specific names are already used in the theme of the control which lead to the binding in the custom TooltipTemplate getting broken. +>important When using the above described approach you should know that setting the x:Name of the RadDateTimePicker to either __"DatePicker"__ or __"DateTimePicker"__ will lead to the ErrorTooltip not showing. The reason is that those specific names are already used in the theme of the control which lead to the binding in the custom TooltipTemplate getting broken. ## See Also diff --git a/controls/raddatetimepicker/features/watermark.md b/controls/raddatetimepicker/features/watermark.md index c312127ed3..08103eca8b 100644 --- a/controls/raddatetimepicker/features/watermark.md +++ b/controls/raddatetimepicker/features/watermark.md @@ -18,7 +18,7 @@ The Watermark is represented by a regular __RadWatermarkTextBox__ control. You c * __DateTimeWatermarkTemplate__ - will set the __WatermarkTemplate__ of the actual __RadWatermarkTextBox__ control. ->tipTo read more about the __RadWatermarkTextBox__ take a look [here]({%slug radwatermarktextbox-overview%}). +>tip To read more about the __RadWatermarkTextBox__ take a look [here]({%slug radwatermarktextbox-overview%}). The __DateTimeWatermarkContent__ is the simplest way to change the watermark's content. For example: diff --git a/controls/raddatetimepicker/how-to/implement-custom-parsing.md b/controls/raddatetimepicker/how-to/implement-custom-parsing.md index 1d53dfbc96..5b72448f5f 100644 --- a/controls/raddatetimepicker/how-to/implement-custom-parsing.md +++ b/controls/raddatetimepicker/how-to/implement-custom-parsing.md @@ -14,7 +14,7 @@ The purpose of this tutorial is to show you how to use the __RadDateTimePicker__ The following example will allow you to enter a month's name into the __RadDateTimePicker's__ input box. As a result the control will assume that the chosen date is the first day of that month and the year will be equal to the current year. Whenever the user enters some text that cannot be parsed it will simply show you an error preview tooltip. ->tipRead more about the __RadDateTimePicker's__ events [here]({%slug raddatetimepicker-events%}). +>tip Read more about the __RadDateTimePicker's__ events [here]({%slug raddatetimepicker-events%}). The final result should look like the snapshots below: @@ -92,7 +92,7 @@ Here is the result: ![{{ site.framework_name }} RadDateTimePicker Custom Parsing](images/dateTimePicker_how_to_implement_custom_parsing_010.png) ->tipIf you want to validate the input date in code behind using __ParseDateTimeValue__ event and set the date back to a previous value if the validation fails, you can still do this. This time you have to set the __ParseDateTimeEventArgs__ parameter's __IsParsingSucceful__ property to __True__ no matter of the errors. However, when validation errors occur you can set the __Result__ property to __ParseDateTimeEventArgs__ parameter's __PreviousValue__ property. In this way if you enter some invalid data, the [Preview Tooltip]({%slug raddatetimepicker-features-preview-tooltip%}) will show you the __PreviousValue__ property's value which will be the last successful input. If you hit enter now, the __RadDateTimePicker__ will select the value indicated by the __Preview Tooltip__. +>tip If you want to validate the input date in code behind using __ParseDateTimeValue__ event and set the date back to a previous value if the validation fails, you can still do this. This time you have to set the __ParseDateTimeEventArgs__ parameter's __IsParsingSucceful__ property to __True__ no matter of the errors. However, when validation errors occur you can set the __Result__ property to __ParseDateTimeEventArgs__ parameter's __PreviousValue__ property. In this way if you enter some invalid data, the [Preview Tooltip]({%slug raddatetimepicker-features-preview-tooltip%}) will show you the __PreviousValue__ property's value which will be the last successful input. If you hit enter now, the __RadDateTimePicker__ will select the value indicated by the __Preview Tooltip__. ## See Also diff --git a/controls/raddatetimepicker/how-to/open-dropdown-get-focus.md b/controls/raddatetimepicker/how-to/open-dropdown-get-focus.md index 9803cba4b8..7a4a7f482d 100644 --- a/controls/raddatetimepicker/how-to/open-dropdown-get-focus.md +++ b/controls/raddatetimepicker/how-to/open-dropdown-get-focus.md @@ -18,7 +18,7 @@ __Example 1: Set the OpenDropDownOnFocus property__ ``` ->tipThe default value of the __RadDateTimePicker__'s __OpenDropDownOnFocus__ property is __False__. +>tip The default value of the __RadDateTimePicker__'s __OpenDropDownOnFocus__ property is __False__. ## See Also diff --git a/controls/raddatetimepicker/how-to/select-only-picker.md b/controls/raddatetimepicker/how-to/select-only-picker.md index 3d636bc48d..18021e00bb 100644 --- a/controls/raddatetimepicker/how-to/select-only-picker.md +++ b/controls/raddatetimepicker/how-to/select-only-picker.md @@ -16,7 +16,7 @@ To do this you will have to slightly modify the template of your __RadDateTimePi * Generate the default __RadDateTimePicker's__ template. ->tipTo see how to do this [read here]({%slug raddatetimepicker-styling-raddatetimepicker%}). +>tip To see how to do this [read here]({%slug raddatetimepicker-styling-raddatetimepicker%}). * Select the __RadWatermarkTextBox__ called __PART_DateTimeInput__ and set its __IsReadOnly__ property to __True__. @@ -24,7 +24,7 @@ This will achieve the desired behavior. However, a specific grey visual element * After generating the __RadWatermarkTextBox's__ style in the __Resources__ pane in Expression Blend you can find the __ControlBackground_ReadOnly__ brush and set it to the __RadDateTimePicker's__ background color. ->tipLearn more about the __RadWatermarkTextBox__ [here]({%slug radwatermarktextbox-overview%}). +>tip Learn more about the __RadWatermarkTextBox__ [here]({%slug radwatermarktextbox-overview%}). ## See Also diff --git a/controls/raddatetimepicker/localization.md b/controls/raddatetimepicker/localization.md index c537a37bab..06cc5f55f9 100644 --- a/controls/raddatetimepicker/localization.md +++ b/controls/raddatetimepicker/localization.md @@ -12,7 +12,7 @@ position: 6 The built-in localization mechanism in Silverlight and WPF allows you to localize any string resource used by the RadDateTimePicker control. Once translated, you might use your resources in both Silverlight and WPF projects without changing anything. ->tipTo learn more about the ways to localize the controls from the UI for {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %} suite please read the common topic about {% if site.site_name == 'Silverlight' %}[Localization](http://www.telerik.com/help/silverlight/common-localization.html){% endif %}{% if site.site_name == 'WPF' %}[Localization](http://www.telerik.com/help/wpf/common-localization.html){% endif %}. +>tip To learn more about the ways to localize the controls from the UI for {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %} suite please read the common topic about {% if site.site_name == 'Silverlight' %}[Localization](http://www.telerik.com/help/silverlight/common-localization.html){% endif %}{% if site.site_name == 'WPF' %}[Localization](http://www.telerik.com/help/wpf/common-localization.html){% endif %}. In __RadDatetimePicker__ you can localize the Enter date message, Close link and Error tooltip: diff --git a/controls/raddatetimepicker/styles-and-templates/styling-clock-view.md b/controls/raddatetimepicker/styles-and-templates/styling-clock-view.md index 64a49e3976..2aa6a65e5a 100644 --- a/controls/raddatetimepicker/styles-and-templates/styling-clock-view.md +++ b/controls/raddatetimepicker/styles-and-templates/styling-clock-view.md @@ -16,7 +16,7 @@ To style the clock in your __RadDateTimePicker__ you can do the following: * Modify the default resources for the __DateTimePickerClock__, that are generated together with the __RadDateTimePicker's Style__. ->tipTo learn how to generate the default __Style__ for the __RadDateTimePicker__ read [here]({%slug raddatetimepicker-styling-raddatetimepicker%}). To learn how to modify the layout of the calendar, look [here]({%slug raddatetimepicker-styling-calendar%}). +>tip To learn how to generate the default __Style__ for the __RadDateTimePicker__ read [here]({%slug raddatetimepicker-styling-raddatetimepicker%}). To learn how to modify the layout of the calendar, look [here]({%slug raddatetimepicker-styling-calendar%}). ## Setting the ClockStyle property diff --git a/controls/raddatetimepicker/styles-and-templates/styling-overview.md b/controls/raddatetimepicker/styles-and-templates/styling-overview.md index 8922ce51f7..02870f44f4 100644 --- a/controls/raddatetimepicker/styles-and-templates/styling-overview.md +++ b/controls/raddatetimepicker/styles-and-templates/styling-overview.md @@ -12,7 +12,7 @@ position: 0 This section is intended to give you a broad understanding of the possible ways to change the visual appearance of the __RadDateTimePicker__ control. There is also comprehensive information about its __ControlTemplates__. You will need this information if you want to customize their appearance. ->tipTo learn how to change the control's theme, please read the common [Implicit Styles]({%slug styling-apperance-implicit-styles-overview%}) topic. +>tip To learn how to change the control's theme, please read the common [Implicit Styles]({%slug styling-apperance-implicit-styles-overview%}) topic. You can modify the look of the __RadDateTimePicker__ control either by changing some of the resources exposed by the API, or by modifying their __ControlTemplates__. In the control template you are allowed to reorder the template parts and add your own elements. However, when changing the __ControlTemplate__ you should be careful to include all required parts. diff --git a/controls/raddatetimepicker/styles-and-templates/styling-raddatetimepicker.md b/controls/raddatetimepicker/styles-and-templates/styling-raddatetimepicker.md index fdd73253e7..968bd7dbb1 100644 --- a/controls/raddatetimepicker/styles-and-templates/styling-raddatetimepicker.md +++ b/controls/raddatetimepicker/styles-and-templates/styling-raddatetimepicker.md @@ -24,7 +24,7 @@ This topic will show you how to perform the second one. To copy the default style, load your project in Expression Blend and open the User Control that holds the __RadDateTimePicker__. In the 'Objects and Timeline' pane select the __RadDateTimePicker__ you want to style. From the menu choose Object -> Edit Style -> Edit a Copy. You will be prompted for the name of the style and where to be placed. ->tipIf you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. +>tip If you choose to define the style in Application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. After clicking 'OK', Expression Blend will generate the default style of the __RadDateTimePicker__ control in the __Resources__ section of your User Control. The properties available for the style will be loaded in the 'Properties' pane and you will be able to modify their default values. You can also edit the generated XAML in the XAML View or in Visual Studio. @@ -62,7 +62,7 @@ Regarding the __DropDownIcon__, you can modify the following resources: * __ButtonIconForeground_Normal__ - is the foreground border brush applied to the CalendarIconBackground path. ->tipIf you want to further modify the drop-down button's default appearance you can modify the default template applied to the __ButtonChrome__. +>tip If you want to further modify the drop-down button's default appearance you can modify the default template applied to the __ButtonChrome__. Here is an example of the above resources modified: diff --git a/controls/raddesktopalert/show-on-current-screen.md b/controls/raddesktopalert/show-on-current-screen.md index b2e02533fd..e43355adef 100644 --- a/controls/raddesktopalert/show-on-current-screen.md +++ b/controls/raddesktopalert/show-on-current-screen.md @@ -48,7 +48,7 @@ __Detach the RadDesktopAlertManager__ manager.Detach(); ``` ->importantDoing so will close all previously opened alerts. +>important Doing so will close all previously opened alerts. >You do not need to call the Detach method if you want to attach the manager to a different element. diff --git a/controls/raddiagram/extensions/settingspane/settingspane_overview.md b/controls/raddiagram/extensions/settingspane/settingspane_overview.md index 8a2fab3285..4503fe00c6 100644 --- a/controls/raddiagram/extensions/settingspane/settingspane_overview.md +++ b/controls/raddiagram/extensions/settingspane/settingspane_overview.md @@ -64,7 +64,7 @@ __RadDiagram__ exposes two events that come in handy while working with the defa * An __AdditionalContentActivatedEventArgs__ object, that gives you access to a __ContextItems__ collection. This collection of __IDiagramItem__ objects represents the items that have activated the additional content. In most cases it contains a single item - the __RadDiagramItem__ that has activated the __SettingsPane__. - >tipPlease note that you can handle this event in order to disable the __SettingsPane__ from displaying on certain __RadDiagramItems__. + >tip Please note that you can handle this event in order to disable the __SettingsPane__ from displaying on certain __RadDiagramItems__. * __AdditionalContentActivated__ - this event is raised by a __RadDiagram__ to inform layouts that the additional content has been activated. The event handler receives two arguments: diff --git a/controls/raddiagram/features/services.md b/controls/raddiagram/features/services.md index 974459290a..3649f571d3 100644 --- a/controls/raddiagram/features/services.md +++ b/controls/raddiagram/features/services.md @@ -126,10 +126,10 @@ This service manages the translation of items on the surface. It exposes the fol _Events_: * __StartDragging__ - occurs when user has done MouseDown on top of an item and has moved the mouse further than the __DiagramConstants.StartDragDelta__ constant. * __Dragging__ - invoked on every MouseMove while the mouse is still pressed and the StartDragging has occured. ->tipIf grid snapping is activated this event will be invoked when a new snapped position is available. +>tip If grid snapping is activated this event will be invoked when a new snapped position is available. * __CompleteDragging__ - occures on mouse up if the __StartDragging__ has been raised. ->importantThe following events are only triggered for items that implement __IDragDropAware__ interface. Currently, only the __RadDiagramContainerShapes__ implement this interface by default. +>important The following events are only triggered for items that implement __IDragDropAware__ interface. Currently, only the __RadDiagramContainerShapes__ implement this interface by default. * __DragEnter__ - occurs when an object is dragged into the drop target's boundary. * __DragLeave__ - occurs when an object is dragged out of the drop target's boundary. diff --git a/controls/raddocking/events/overview.md b/controls/raddocking/events/overview.md index 821db79ce2..331942b9bb 100644 --- a/controls/raddocking/events/overview.md +++ b/controls/raddocking/events/overview.md @@ -75,9 +75,9 @@ This help article covers the specific events exposed by the __RadDocking__ contr * __CustomElementLoading__: Raised when a custom docking element (that derives from __RadPane__, __RadPaneGroup__ or __RadSplitContainer__) is about to be loaded. The passed event argument is of type __LayoutSerializationCustomLoadingEventArgs__. ->tipElements are __cleaned just before loading__ the layout: This operation is performed to prepare the Docking control for the new layout. +>tip Elements are __cleaned just before loading__ the layout: This operation is performed to prepare the Docking control for the new layout. ->tipFor more information about saving and loading __RadDocking__ layout, take a look at the [Save\Load Layout]({%slug raddocking-features-save-load-layout-overview%}) topic. +>tip For more information about saving and loading __RadDocking__ layout, take a look at the [Save\Load Layout]({%slug raddocking-features-save-load-layout-overview%}) topic. ## ElementCreated Events diff --git a/controls/raddocking/features/document-host.md b/controls/raddocking/features/document-host.md index 73e4b95fbd..e0e74b2383 100644 --- a/controls/raddocking/features/document-host.md +++ b/controls/raddocking/features/document-host.md @@ -38,7 +38,7 @@ Here is the XAML declaration of the above structure. ``` ->tipSince the DocumentHost is meant to host the editable documents in your application, it is good idea to use [RadDocumentPanes]({%slug raddocking-panes-raddocumentpane%}) instead of [RadPanes]({%slug raddocking-panes-radpane%}). +>tip Since the DocumentHost is meant to host the editable documents in your application, it is good idea to use [RadDocumentPanes]({%slug raddocking-panes-raddocumentpane%}) instead of [RadPanes]({%slug raddocking-panes-radpane%}). >Placing `RadPaneGroup` directly in the DocumentHost is not a supported scenario in the Docking control. The RadPaneGroup needs to be placed in a `RadSplitContainer`. diff --git a/controls/raddocking/features/drag-and-drop.md b/controls/raddocking/features/drag-and-drop.md index 62e241412b..10cb7b2c78 100644 --- a/controls/raddocking/features/drag-and-drop.md +++ b/controls/raddocking/features/drag-and-drop.md @@ -14,7 +14,7 @@ The __Drag and Drop__ compatibilities of the __RadDocking__ control allow you to Below you can find several step-by-step tutorials for the most common operations that can be accomplished via drag and drop. ->tipFind out how to implement [conditional docking]({%slug raddocking-how-to-implement-conditional-docking%}) using __PreviewShowCompass__ event exposed by __RadDocking__. +>tip Find out how to implement [conditional docking]({%slug raddocking-how-to-implement-conditional-docking%}) using __PreviewShowCompass__ event exposed by __RadDocking__. ## Docking Panes to a Container @@ -58,7 +58,7 @@ As you can see you have dragged your pane over the Compass' right indicator whic ![Adding Panes to Tabbed Documents](images/RadDocking_Features_Drag_and_Drop_030.png) ->tipTo dock a pane to a [Tabbed Document]({%slug raddocking-features-pane-groups%}), drag and drop it over the center indicator of the Compass. +>tip To dock a pane to a [Tabbed Document]({%slug raddocking-features-pane-groups%}), drag and drop it over the center indicator of the Compass. ## Undocking Panes @@ -70,7 +70,7 @@ As you can see you have dragged your pane over the Compass' right indicator whic ![Undocking Panes](images/RadDocking_Features_Drag_and_Drop_040.png) ->tipTo undock a pane and make it floatable, just drag it out of its current place and drop it outside any compass indicator. +>tip To undock a pane and make it floatable, just drag it out of its current place and drop it outside any compass indicator. ## Using Native ToolWindow Drag diff --git a/controls/raddocking/features/nesteddocking.md b/controls/raddocking/features/nesteddocking.md index 119ec195de..d9bed1b7f3 100644 --- a/controls/raddocking/features/nesteddocking.md +++ b/controls/raddocking/features/nesteddocking.md @@ -75,7 +75,7 @@ In this section you can see screenshots of few layouts achieved with nested __Ra The nested __RadDocking__ layouts can be easily saved and loaded using the built-in Save/Load Layout functionality of the control. In order to achieve Save/Load Layout for nested scenarios you will simply need to save each __RadDocking__ separately and load separately each of them afterwards. The direction of the loading operation should be from the inner __RadDockings__ to the outer ones in order to avoid any issues when loading floating __RadPanes/RadPaneGroups__. ->tipFor more details you can check the [Save/Load Layout]({%slug raddocking-features-save-load-layout-overview%}) article. +>tip For more details you can check the [Save/Load Layout]({%slug raddocking-features-save-load-layout-overview%}) article. >tip You can download a runnable sample project demonstrating Save/Load Nested Docking Layouts from [the online SDK repository](https://github.com/telerik/xaml-sdk/tree/master/Docking/NestedDockingSaveLoadLayout). diff --git a/controls/raddocking/features/pane-groups.md b/controls/raddocking/features/pane-groups.md index aad1247912..61cca1292a 100644 --- a/controls/raddocking/features/pane-groups.md +++ b/controls/raddocking/features/pane-groups.md @@ -63,7 +63,7 @@ __Example 2: Adding panes to a RadPaneGroup__ In order to remove panes run-time you should either close the pane or remove the pane from the group via [drag and drop]({%slug raddocking-features-drag-and-drop%}). ->tipIf you want to restrict the user not to close panes, take a look at the [How to Disable the Close ("X") Button]({%slug raddocking-how-to-disable-the-close-button%}) topic. +>tip If you want to restrict the user not to close panes, take a look at the [How to Disable the Close ("X") Button]({%slug raddocking-how-to-disable-the-close-button%}) topic. ## Removing Panes Programmatically @@ -141,7 +141,7 @@ __Example 6: Show all group panes__ >__ShowAllPanes__ method works only when all of the objects are constructed and added to the object tree. Which means that you should invoke it after the __Loaded__ event of the __RadDocking__ control has been fired. ->tipIf you need information about the events fired when showing and hiding panes, take a look at the [Events]({%slug raddocking-events-overview%}) topic. +>tip If you need information about the events fired when showing and hiding panes, take a look at the [Events]({%slug raddocking-events-overview%}) topic. ## Pinning All Panes @@ -183,7 +183,7 @@ __Example 7: Unpin all group panes__ >__UnpinAllPanes__ method works only when all of the objects are constructed and added to the object tree. Which means that you should invoke it after the __Loaded__ event of the __RadDocking__ control has been fired. ->tipIf you need information about the events fired when pinning and unpining panes, take a look at the [Events]({%slug raddocking-events-overview%}) topic. +>tip If you need information about the events fired when pinning and unpining panes, take a look at the [Events]({%slug raddocking-events-overview%}) topic. ## Persist Content with the IsContentPreserved Property diff --git a/controls/raddocking/features/panes/docked-floating-panes.md b/controls/raddocking/features/panes/docked-floating-panes.md index 46ec96716d..8c5fd6d649 100644 --- a/controls/raddocking/features/panes/docked-floating-panes.md +++ b/controls/raddocking/features/panes/docked-floating-panes.md @@ -57,7 +57,7 @@ __Example 2: Remove RadPane from RadPaneGroup__ radPaneGroup.Items.Add(radPane) ``` ->tipIf you need to control the docking run-time (while the user is dragging a pane), you could use the __PreviewShowCompass__ event of the __RadDocking__ control in combination with the __Is<*>IndicatorVisible__ series of properties of the __Compass__ class. Where <*> could be one of the following: Left, Top, Right, Bottom, Center. To learn more take a look at the [How to Implement Conditional Docking]({%slug raddocking-how-to-implement-conditional-docking%}) topic. +>tip If you need to control the docking run-time (while the user is dragging a pane), you could use the __PreviewShowCompass__ event of the __RadDocking__ control in combination with the __Is<*>IndicatorVisible__ series of properties of the __Compass__ class. Where <*> could be one of the following: Left, Top, Right, Bottom, Center. To learn more take a look at the [How to Implement Conditional Docking]({%slug raddocking-how-to-implement-conditional-docking%}) topic. ## Floating Panes @@ -86,7 +86,7 @@ __Example 3: Create Floating Panes__ ``` ->tipIf you want to specify the exact position and size of the floating panes set the attached properties __RadDocking.FloatingLocation__ and __RadDocking.FloatingSize__ inside the declaration of the containing __RadSplitContainer__. +>tip If you want to specify the exact position and size of the floating panes set the attached properties __RadDocking.FloatingLocation__ and __RadDocking.FloatingSize__ inside the declaration of the containing __RadSplitContainer__. __Example 4: Set the FloatingLocation and FloatingSize attached properties__ @@ -119,9 +119,9 @@ __Example 5: Make a RadPane FloatingDockable__ radPane.MakeFloatingDockable() ``` ->tipIf you make your pane floating using the __MakeFloatingOnly()__ you will not be able to dock it back again using [drag and drop]({%slug raddocking-features-drag-and-drop%}). To make it dockable again you have to call the method __MakeDockable()__. +>tip If you make your pane floating using the __MakeFloatingOnly()__ you will not be able to dock it back again using [drag and drop]({%slug raddocking-features-drag-and-drop%}). To make it dockable again you have to call the method __MakeDockable()__. ->tipThe RadPane loses its DataContext when it's made floating since it is hosted in a ToolWindow. In order to preserve any bindings applied to the RadPane properties, you can explicitly set the DataContext on the RadPane itsself. +>tip The RadPane loses its DataContext when it's made floating since it is hosted in a ToolWindow. In order to preserve any bindings applied to the RadPane properties, you can explicitly set the DataContext on the RadPane itsself. ## Disable Floating diff --git a/controls/raddocking/features/panes/panes-menu.md b/controls/raddocking/features/panes/panes-menu.md index bd0a558b5c..6d18a73f36 100644 --- a/controls/raddocking/features/panes/panes-menu.md +++ b/controls/raddocking/features/panes/panes-menu.md @@ -58,7 +58,7 @@ To make the menu items functional you can use the predefined __RadDocking__ comm * __TabbedDocument__ ->tipYou can also create your own custom commands and use them with the RadPane's menu. To learn how read [this topic]({%slug raddocking-how-to-add-menu-items-to-the-radpanes-menu%}). +>tip You can also create your own custom commands and use them with the RadPane's menu. To learn how read [this topic]({%slug raddocking-how-to-add-menu-items-to-the-radpanes-menu%}). Here is the final code: diff --git a/controls/raddocking/features/panes/pinned-unpinned-panes.md b/controls/raddocking/features/panes/pinned-unpinned-panes.md index e387d6bd18..3351c2d199 100644 --- a/controls/raddocking/features/panes/pinned-unpinned-panes.md +++ b/controls/raddocking/features/panes/pinned-unpinned-panes.md @@ -53,7 +53,7 @@ If you hover your mouse over the tab of the "Toolbox" pane, it will slide automa ![{{ site.framework_name }} RadDocking Hovered Pane](images/RadDocking_Features_Panes_Pinn_Unpinn_040.png) ->tipIf you want to control the auto-hide area's width and hight of your unpinned panes use the respective __RadPane__'s properties __AutoHideHeight__ and __AutoHideWidth__. The size of the auto-hide area is also affected by the __FlyoutMinLength__ property of RadDocking. +>tip If you want to control the auto-hide area's width and hight of your unpinned panes use the respective __RadPane__'s properties __AutoHideHeight__ and __AutoHideWidth__. The size of the auto-hide area is also affected by the __FlyoutMinLength__ property of RadDocking. ## Let Auto-Hide Area Content Exceed Screen diff --git a/controls/raddocking/features/panes/raddocumentpane.md b/controls/raddocking/features/panes/raddocumentpane.md index 2971f9879e..44158f446b 100644 --- a/controls/raddocking/features/panes/raddocumentpane.md +++ b/controls/raddocking/features/panes/raddocumentpane.md @@ -14,7 +14,7 @@ Since RadDocumentPane is a direct inheritor of __RadPane__, it shares the same c To learn more about __RadDocumentPane__ take a look at the __RadPane__'s [Overview]({%slug raddocking-panes-radpane%}) topic, since all of the characteristics and functionalities of the __RadPane__ are also valid for the RadDocumentPane. ->tipUse __RadDocumentPane__ to host any kind of documents that are editable by your application, while the utility panels can be hosted in the standard __RadPane__ control. +>tip Use __RadDocumentPane__ to host any kind of documents that are editable by your application, while the utility panels can be hosted in the standard __RadPane__ control. ![{{ site.framework_name }} RadDocking RadDocumentPane](images/RadDocking_Features_Panes_RadDocumentPane_010.png) diff --git a/controls/raddocking/features/retain-pane-size.md b/controls/raddocking/features/retain-pane-size.md index 3bf146fa26..28a22000d2 100644 --- a/controls/raddocking/features/retain-pane-size.md +++ b/controls/raddocking/features/retain-pane-size.md @@ -80,7 +80,7 @@ __Figure 2: __ The Pane is docked: __Figure 3: __ The last floating size is kept when the Pane becomes floating again: ![{{ site.framework_name }} RadDocking The last floating size is kept when the Pane becomes floating again:](images/raddocking-features-retain-pane-size-6.png) ->importantWe recommend setting __FloatingSize__ only to the Pane when initial size needs to be applied. Please, notice that this size will be appplied just once when the Pane is undocked for the first time. +>important We recommend setting __FloatingSize__ only to the Pane when initial size needs to be applied. Please, notice that this size will be appplied just once when the Pane is undocked for the first time. ## DockingAndFloating diff --git a/controls/raddocking/features/save-load-layout/overview.md b/controls/raddocking/features/save-load-layout/overview.md index 0ce03bdcfd..8d88734bb3 100644 --- a/controls/raddocking/features/save-load-layout/overview.md +++ b/controls/raddocking/features/save-load-layout/overview.md @@ -371,7 +371,7 @@ The event argument of the __CustomElementLoading__ event is of type __LayoutSeri * __Cancel__ - determines whether the custom AffectedElement will be loaded. ->tipThe __Telerik.Windows.Controls.LayoutSerializationLoadingEventArgs__ allows you to point out an instance to be used as a newly loaded control. This could be useful if you need to create the instances yourself. +>tip The __Telerik.Windows.Controls.LayoutSerializationLoadingEventArgs__ allows you to point out an instance to be used as a newly loaded control. This could be useful if you need to create the instances yourself. >You have the ability to "say" whether these event to be fired or not, when the __SerializationTag__ is __not specified__. You should use the second overload of the __LoadLayout__ and __SaveLayout__ methods. diff --git a/controls/raddocking/features/save-load-layout/save-load-the-content-of-the-panes.md b/controls/raddocking/features/save-load-layout/save-load-the-content-of-the-panes.md index 7c5a73c58b..3bf78aa4c9 100644 --- a/controls/raddocking/features/save-load-layout/save-load-the-content-of-the-panes.md +++ b/controls/raddocking/features/save-load-layout/save-load-the-content-of-the-panes.md @@ -83,7 +83,7 @@ __Example 4: Get Content of Pane__ End Sub ``` ->importantThe __GetPaneContent()__ method needs to be implemented with the specific user custom logic. +>important The __GetPaneContent()__ method needs to be implemented with the specific user custom logic. ## See Also diff --git a/controls/raddocking/features/split-container.md b/controls/raddocking/features/split-container.md index e35a76ebe0..8b0c990854 100644 --- a/controls/raddocking/features/split-container.md +++ b/controls/raddocking/features/split-container.md @@ -24,7 +24,7 @@ Each split container is painted in a different color. When you want to define the orientation (__Vertical__ or __Horizontal__) in which the panes are ordered inside the container, then you need to set the __Orientation__ property of the __RadSplitContainer__. ->tipSetting the __Orientation__ property of a __RadSplitContainer__ is similar to setting the __Orientation__ property of a __StackPanel__. +>tip Setting the __Orientation__ property of a __RadSplitContainer__ is similar to setting the __Orientation__ property of a __StackPanel__. * Setting the __Orientation__ property to __Vertical__ @@ -96,7 +96,7 @@ __Example 3: Setting Orientation to Vertical in code-behind__ End Sub ``` ->tipThe default __Orientation__ for the __RadSplitContainer__ is __Horizontal__. +>tip The default __Orientation__ for the __RadSplitContainer__ is __Horizontal__. ## Setting the InitialPosition of the RadSplitContainer @@ -254,7 +254,7 @@ __Example 9: Setting InitialPosition in code-behind__ End Sub ``` ->tipPlace each [RadPane]({%slug raddocking-panes-radpane%}) ([RadPaneGroup]({%slug raddocking-features-pane-groups%})) in a separate split container to have the power to initially dock them as desired using the __InitialPosition__ property. +>tip Place each [RadPane]({%slug raddocking-panes-radpane%}) ([RadPaneGroup]({%slug raddocking-features-pane-groups%})) in a separate split container to have the power to initially dock them as desired using the __InitialPosition__ property. ## Setting the InitialSize of the RadSplitContainer @@ -303,7 +303,7 @@ __Example 11: Setting FloatingSize__ >Note that the __InitialPosition__ must be set either to __FloatingOnly__ or __FloatingDockable__. Otherwise setting the __RadDocking.FloatingSize__ attached property will not affect the size of the split container. ->tipIf you want to resize the __RadSplitContainer__ during run-time, then just use the [Resizer]({%slug raddocking-visual-structure%}). +>tip If you want to resize the __RadSplitContainer__ during run-time, then just use the [Resizer]({%slug raddocking-visual-structure%}). ## Setting the Initial FloatingLocation of the RadSplitContainer diff --git a/controls/raddocking/getting-started/getting-started2.md b/controls/raddocking/getting-started/getting-started2.md index db62803bd2..1ff794b134 100644 --- a/controls/raddocking/getting-started/getting-started2.md +++ b/controls/raddocking/getting-started/getting-started2.md @@ -83,7 +83,7 @@ __Example 3: Adding DocumentHost in XAML__ ``` ->tipThe DocumentHost control is not a required element. As an experiment, remove it from the XAML above and run your application to see how the application changes. +>tip The DocumentHost control is not a required element. As an experiment, remove it from the XAML above and run your application to see how the application changes. ### Adding RadSplitContainer diff --git a/controls/raddocking/getting-started/managing-docking-dynamically.md b/controls/raddocking/getting-started/managing-docking-dynamically.md index 22c32583a4..888bf430cb 100644 --- a/controls/raddocking/getting-started/managing-docking-dynamically.md +++ b/controls/raddocking/getting-started/managing-docking-dynamically.md @@ -86,7 +86,7 @@ You can programmatically make a pane floatable by either calling __MakeFloatingD End Sub ``` ->tipNote that if you make your pane floating using the __MakeFloatingOnly()__ you will not be able to dock it back again using [drag and drop]({%slug raddocking-features-drag-and-drop%}), to make it dockable again you have to call the method __MakeDockable()__. +>tip Note that if you make your pane floating using the __MakeFloatingOnly()__ you will not be able to dock it back again using [drag and drop]({%slug raddocking-features-drag-and-drop%}), to make it dockable again you have to call the method __MakeDockable()__. Executing any of the described methods will lead to the following result: @@ -146,7 +146,7 @@ In order to make a pane dockable, you need to invoke the __MakeDockable()__ meth >__MakeDockable__ method works only when all of the objects are constructed and added to the object tree. Which means that you should invoke it after the __Loaded__ event of the __RadDocking__ control has been fired. ->tipMaking a pane dockable __will not dock__ the pane to any of the sides in the docking area. But it will allow the user to dock the pane during run-time via [drag and drop]({%slug raddocking-features-drag-and-drop%}). +>tip Making a pane dockable __will not dock__ the pane to any of the sides in the docking area. But it will allow the user to dock the pane during run-time via [drag and drop]({%slug raddocking-features-drag-and-drop%}). ## Making a Pane Dockable in XAML @@ -164,7 +164,7 @@ In order to make a pane dockable during design-time, you need to set the __Initi ``` ->tipSetting the __InitialPosition__ to __FloatingDockable__ or __FloatingOnly__ will make your pane(s) [floating]({%slug raddocking-features-panes-docked-floating-panes%}). However, using the __FloatingOnly__ value __will not allow__ the user to dock the pane during run-time. +>tip Setting the __InitialPosition__ to __FloatingDockable__ or __FloatingOnly__ will make your pane(s) [floating]({%slug raddocking-features-panes-docked-floating-panes%}). However, using the __FloatingOnly__ value __will not allow__ the user to dock the pane during run-time. ## Docking a Pane in the Code-Behind diff --git a/controls/raddocking/how-to/add-buttons-to-the-pane-headers.md b/controls/raddocking/how-to/add-buttons-to-the-pane-headers.md index 9c86a3f910..4d908b3247 100644 --- a/controls/raddocking/how-to/add-buttons-to-the-pane-headers.md +++ b/controls/raddocking/how-to/add-buttons-to-the-pane-headers.md @@ -12,7 +12,7 @@ position: 1 The purpose of this tutorial is to walk you through the common task of adding buttons to the pane header and attaching some behavior to them. ->tipFor more information about the __RadPane__ and its visual elements, read [here]({%slug raddocking-panes-radpane%}). +>tip For more information about the __RadPane__ and its visual elements, read [here]({%slug raddocking-panes-radpane%}). For the purpose of this tutorial, the following __RadDocking__ declaration will be used: diff --git a/controls/raddocking/how-to/add-menu-items-to-the-radpanes-menu.md b/controls/raddocking/how-to/add-menu-items-to-the-radpanes-menu.md index 82d7817043..6f0e998ca1 100644 --- a/controls/raddocking/how-to/add-menu-items-to-the-radpanes-menu.md +++ b/controls/raddocking/how-to/add-menu-items-to-the-radpanes-menu.md @@ -12,7 +12,7 @@ position: 0 The purpose of this tutorial is to show you how to customize __RadPane's__ menu. ->tipFor more information about the __RadPane__ structure, read [here]({%slug raddocking-panes-radpane%}). If you want to learn more about __RadPane's__ menu, read [this one]({%slug raddocking-features-panes-panes-menu%}). +>tip For more information about the __RadPane__ structure, read [here]({%slug raddocking-panes-radpane%}). If you want to learn more about __RadPane's__ menu, read [this one]({%slug raddocking-features-panes-panes-menu%}). ## Customizing RadPane's Menu diff --git a/controls/raddocking/how-to/implement-conditional-docking.md b/controls/raddocking/how-to/implement-conditional-docking.md index d7e01d1f32..3d3b49a72d 100644 --- a/controls/raddocking/how-to/implement-conditional-docking.md +++ b/controls/raddocking/how-to/implement-conditional-docking.md @@ -169,7 +169,7 @@ Switch to the code-behind. The __PreviewShowCompassEventArgs__ exposes a __Compa In the last case, all compass indicators are disabled. ->tipThere is an alternative approach to disable the docking. You need to set the initial position of the [RadSplitContainer]({%slug raddocking-styling-the-radsplitcontainer%}) to __FloatingOnly__. +>tip There is an alternative approach to disable the docking. You need to set the initial position of the [RadSplitContainer]({%slug raddocking-styling-the-radsplitcontainer%}) to __FloatingOnly__. ## See Also diff --git a/controls/raddocking/localization.md b/controls/raddocking/localization.md index 1586562f7f..9a46b440fc 100644 --- a/controls/raddocking/localization.md +++ b/controls/raddocking/localization.md @@ -12,7 +12,7 @@ position: 5 The built-in localization mechanism in Silverlight and WPF allows you to localize any string resource used by the RadDocking control. Once translated, you might use your resources in both Silverlight and WPF projects without changing anything. ->tipTo learn more about the ways to localize UI for {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %} please read the common topic about {% if site.site_name == 'Silverlight' %}[Localization]({%slug common-localization%}){% endif %}{% if site.site_name == 'WPF' %}[Localization]({%slug common-localization%}){% endif %}. +>tip To learn more about the ways to localize UI for {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %} please read the common topic about {% if site.site_name == 'Silverlight' %}[Localization]({%slug common-localization%}){% endif %}{% if site.site_name == 'WPF' %}[Localization]({%slug common-localization%}){% endif %}. In __RadDocking__ you can localize the context menu: diff --git a/controls/raddocking/styles-and-templates/styling-the-raddocumentpane.md b/controls/raddocking/styles-and-templates/styling-the-raddocumentpane.md index 68333a6152..02b6a20259 100644 --- a/controls/raddocking/styles-and-templates/styling-the-raddocumentpane.md +++ b/controls/raddocking/styles-and-templates/styling-the-raddocumentpane.md @@ -12,7 +12,7 @@ position: 9 For now the __RadDocumentPane__ control is identical to the __RadPane__ control as the __RadDocumentPane__ inherits it. In that way the control properties and templates are the same and you can use the same approach to style it as with the __RadPane__ control. To learn more about styling the __RadPane__ read [here]({%slug raddocking-styling-the-radpane%}). ->tipYou are able to set a style created for the __RadPane__ control directly to the __RadDocumentPane__ control without the need to change its __TargetType__, as the __RadDocumentPane__ derives from the __RadPane__. +>tip You are able to set a style created for the __RadPane__ control directly to the __RadDocumentPane__ control without the need to change its __TargetType__, as the __RadDocumentPane__ derives from the __RadPane__. ## See Also diff --git a/controls/radexpressioneditor/getting-started.md b/controls/radexpressioneditor/getting-started.md index d270a883f3..cb83f74296 100644 --- a/controls/radexpressioneditor/getting-started.md +++ b/controls/radexpressioneditor/getting-started.md @@ -45,7 +45,7 @@ You can find the required assemblies for each control from the suite in the [Con * Create a new project; ->importantIf you are using **{{ site.minimum_net_core_version }}** and later, please note that instead of the **Telerik.Windows.Documents.dll** you need to use the new **Telerik.Windows.Controls.RichTextBox.dll** assembly. +>important If you are using **{{ site.minimum_net_core_version }}** and later, please note that instead of the **Telerik.Windows.Documents.dll** you need to use the new **Telerik.Windows.Controls.RichTextBox.dll** assembly. >In case you use [Implicit Styles]({%slug styling-apperance-implicit-styles-overview%}), please make sure all the needed resource dictionaries are merged: * System.Windows.xaml diff --git a/controls/radexpressioneditor/localization.md b/controls/radexpressioneditor/localization.md index 596834eeda..450eef5ae1 100644 --- a/controls/radexpressioneditor/localization.md +++ b/controls/radexpressioneditor/localization.md @@ -26,7 +26,7 @@ __: Some of RadExpressionEditor`s localized resources:__ ![RadExpressionEditor Localization](images/RadExpressionEditor_Localization.png) ->tipTo learn more about the ways to localize the RadControls please read the common topic on [Localization]({%slug common-localization%}). +>tip To learn more about the ways to localize the RadControls please read the common topic on [Localization]({%slug common-localization%}). >__In order to dynamically localize the RadExpressionEditor at runtime, you should recreate it.__ diff --git a/controls/radganttview/features/columns/cell-template.md b/controls/radganttview/features/columns/cell-template.md index 9920d20ffe..6c40839d96 100644 --- a/controls/radganttview/features/columns/cell-template.md +++ b/controls/radganttview/features/columns/cell-template.md @@ -48,7 +48,7 @@ The next example demonstrates how to customize the CellTemplate of the Title col ``` ->importantWhen creating a custom CellTemplate for a ColumnDefinition which __MemberBinding__ is set to a custom property or a property that is not the Start, End or Title properties of the GanttTask you should set the binding in the DataTemplate to the built-in __FormattedValue__ property as the above code snippet shows. This is an optimized string value that comes from the built-in virtualization of the control in order to achieve maximum performance. +>important When creating a custom CellTemplate for a ColumnDefinition which __MemberBinding__ is set to a custom property or a property that is not the Start, End or Title properties of the GanttTask you should set the binding in the DataTemplate to the built-in __FormattedValue__ property as the above code snippet shows. This is an optimized string value that comes from the built-in virtualization of the control in order to achieve maximum performance. >tip Find a runnable project of the previous example in the [WPF Samples GitHub repository](https://github.com/telerik/xaml-sdk/tree/master/GanttView/CustomCellTemplates). diff --git a/controls/radganttview/features/columns/highlight-template.md b/controls/radganttview/features/columns/highlight-template.md index f81b00a253..786b484176 100644 --- a/controls/radganttview/features/columns/highlight-template.md +++ b/controls/radganttview/features/columns/highlight-template.md @@ -48,7 +48,7 @@ The xaml of the GanttView should look like this: ``` ->importantWhen creating a custom CellHighlightTemplate for a ColumnDefinition which __MemberBinding__ is set to a custom property or a property that is not the Start, End or Title properties of the GanttTask you should set the binding in the DataTemplate to the built-in __FormattedValue__ property as the above code snippet shows. This is an optimized string value that comes from the built-in virtualization of the control in order to achieve maximum performance. +>important When creating a custom CellHighlightTemplate for a ColumnDefinition which __MemberBinding__ is set to a custom property or a property that is not the Start, End or Title properties of the GanttTask you should set the binding in the DataTemplate to the built-in __FormattedValue__ property as the above code snippet shows. This is an optimized string value that comes from the built-in virtualization of the control in order to achieve maximum performance. >tip Find a runnable project of the previous example in the [WPF Samples GitHub repository](https://github.com/telerik/xaml-sdk/tree/master/GanttView/CustomCellTemplates). diff --git a/controls/radganttview/features/columns/selection-template.md b/controls/radganttview/features/columns/selection-template.md index f94be0a017..e520fffbf0 100644 --- a/controls/radganttview/features/columns/selection-template.md +++ b/controls/radganttview/features/columns/selection-template.md @@ -48,7 +48,7 @@ The xaml of the GanttView should look like this: ``` ->importantWhen creating a custom CellSelectionTemplate for a ColumnDefinition which __MemberBinding__ is set to a custom property or a property that is not the Start, End or Title properties of the GanttTask you should set the binding in the DataTemplate to the built-in __FormattedValue__ property as the above code snippet shows. This is an optimized string value that comes from the built-in virtualization of the control in order to achieve maximum performance. +>important When creating a custom CellSelectionTemplate for a ColumnDefinition which __MemberBinding__ is set to a custom property or a property that is not the Start, End or Title properties of the GanttTask you should set the binding in the DataTemplate to the built-in __FormattedValue__ property as the above code snippet shows. This is an optimized string value that comes from the built-in virtualization of the control in order to achieve maximum performance. >tip Find a runnable project of the previous example in the [WPF Samples GitHub repository](https://github.com/telerik/xaml-sdk/tree/master/GanttView/CustomCellTemplates). diff --git a/controls/radganttview/styles-and-templates/setting-theme.md b/controls/radganttview/styles-and-templates/setting-theme.md index e505091a63..8ba5aba45f 100644 --- a/controls/radganttview/styles-and-templates/setting-theme.md +++ b/controls/radganttview/styles-and-templates/setting-theme.md @@ -12,7 +12,7 @@ position: 0 The purpose of this article is to show you how to set a built-in theme to __RadGanttView__ for {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %}. ->tipDetailed information about the use of implicit styles can be found {% if site.site_name == 'Silverlight' %}[here](http://www.telerik.com/help/silverlight/styling-apperance-implicit-styles-overview.html){% endif %}{% if site.site_name == 'WPF' %}[here](http://www.telerik.com/help/wpf/styling-apperance-implicit-styles-overview.html){% endif %}. +>tip Detailed information about the use of implicit styles can be found {% if site.site_name == 'Silverlight' %}[here](http://www.telerik.com/help/silverlight/styling-apperance-implicit-styles-overview.html){% endif %}{% if site.site_name == 'WPF' %}[here](http://www.telerik.com/help/wpf/styling-apperance-implicit-styles-overview.html){% endif %}. So, in order to set a theme to the GanttView, you should merge the following xaml files in App.xaml file: diff --git a/controls/radgauge/features/indicators/bar-indicators-basics.md b/controls/radgauge/features/indicators/bar-indicators-basics.md index 44d7e30972..60831a1efc 100644 --- a/controls/radgauge/features/indicators/bar-indicators-basics.md +++ b/controls/radgauge/features/indicators/bar-indicators-basics.md @@ -12,7 +12,7 @@ position: 3 The __Linear__ and the __Radial__ __Bars__ derive from the __BarIndicator__ class. Because of that they provide some common functionality. This topic will focus on the common features between these indicators. ->tipThe __BarIndicator__ class inherits the __IndicatorBase__ class, which is a base class for all indicators, except the __NumericIndicator__. To learn more about the base features of the indicators read [this topic]({%slug radgauge-features-indicators-basics%}). +>tip The __BarIndicator__ class inherits the __IndicatorBase__ class, which is a base class for all indicators, except the __NumericIndicator__. To learn more about the base features of the indicators read [this topic]({%slug radgauge-features-indicators-basics%}). For the examples in this article a __LinearBar__ indicator will be used, but the examples can be applied to the __RadialBar__ one as well. diff --git a/controls/radgauge/features/indicators/marker.md b/controls/radgauge/features/indicators/marker.md index bd81c9db6e..924450a7e7 100644 --- a/controls/radgauge/features/indicators/marker.md +++ b/controls/radgauge/features/indicators/marker.md @@ -12,7 +12,7 @@ position: 1 The __Marker__ is one of the indicator types that the __RadGauge__ control introduces. It directly inherits the __InteractiveIndicator__ class and doesn't introduce any specific features. ->tipTo learn more about the base features of the indicators read [this topic]({%slug radgauge-features-indicators-basics%}). +>tip To learn more about the base features of the indicators read [this topic]({%slug radgauge-features-indicators-basics%}). The __Marker__ control is represented by a triangle shape. The appearance and the shape can be easily modified. diff --git a/controls/radgridview/columns/celltemplate-and-celledittemplate.md b/controls/radgridview/columns/celltemplate-and-celledittemplate.md index fcecace1e0..72f0159cca 100644 --- a/controls/radgridview/columns/celltemplate-and-celledittemplate.md +++ b/controls/radgridview/columns/celltemplate-and-celledittemplate.md @@ -40,7 +40,7 @@ Sometimes you need to extend the functionality of a column and define a custom e * __CellEditTemplate__: Gets or sets the data template for the cell in edit mode. ->tipYou can also conditionally apply different data templates to RadGridView cells by using the [CellTemplateSelector and CellEditTemplateSelector]({%slug gridview-cell-template-selector%}) properties. +>tip You can also conditionally apply different data templates to RadGridView cells by using the [CellTemplateSelector and CellEditTemplateSelector]({%slug gridview-cell-template-selector%}) properties. **Example 1** demonstrates how to use both properties to customize your columns. We set the __RadDateTimePicker__ as a __CellEditTemplate__ for the __DateTime__ column type and the __RadNumericUpDown__ as a __CellTemplate__ for the **Salary** column. diff --git a/controls/radgridview/columns/column-headers.md b/controls/radgridview/columns/column-headers.md index e4be78ee60..96b66c2c7b 100644 --- a/controls/radgridview/columns/column-headers.md +++ b/controls/radgridview/columns/column-headers.md @@ -89,7 +89,7 @@ The header of the column plays the main role when we want to sort it. It also ho ![Telerik {{ site.framework_name }} DataGrid Column Headers 4](images/RadGridView_ColumnHeaders_4.png) ->tipAs of Q2 2013, the user can benefit from __Column Sort Sequence Indicator__. In order to have this feature enabled you need to set ShowColumnSortIndexes property of RadGridView to True. +>tip As of Q2 2013, the user can benefit from __Column Sort Sequence Indicator__. In order to have this feature enabled you need to set ShowColumnSortIndexes property of RadGridView to True. To learn more about the sorting functionality take a look at the [Basic Sorting]({%slug gridview-sorting-basics%}) topic in the Sorting chapter. diff --git a/controls/radgridview/columns/columntypes/checkbox-column.md b/controls/radgridview/columns/columntypes/checkbox-column.md index c5ff44323b..1035dd324c 100644 --- a/controls/radgridview/columns/columntypes/checkbox-column.md +++ b/controls/radgridview/columns/columntypes/checkbox-column.md @@ -27,7 +27,7 @@ __Example 1: Declare a column of type GridViewCheckBoxColumn__ #### __Figure 1: Declared CheckBox Column.__ ![Rad Grid View Columns Check Box Column 01](images/RadGridView_Columns_CheckBoxColumn_01.png) ->tipUse this column for __better performance__ when you know that the underlying data is of __boolean type__. +>tip Use this column for __better performance__ when you know that the underlying data is of __boolean type__. __GridViewCheckBoxColumn__ provides a property that is not present in any other column: __AutoSelectOnEdit__. When set to __True__ the __CheckBox__ is automatically toggled on editing the cell thus decreasing the number of clicks you need to take to change the boolean value of the bound property. diff --git a/controls/radgridview/columns/columntypes/column-types-basic-column.md b/controls/radgridview/columns/columntypes/column-types-basic-column.md index 63a1c0ec8f..2c8d9241ed 100644 --- a/controls/radgridview/columns/columntypes/column-types-basic-column.md +++ b/controls/radgridview/columns/columntypes/column-types-basic-column.md @@ -17,7 +17,7 @@ __GridViewColumn__ is the base column type on top of which the other columns are You can add aggregate functions to display their result in the column footers, manage the headers and cells, apply different styling for the its header and cells, reorder it, etc. The most common usage of this type of column is when you want to define a column that doesn't bind to any data. ->tipSuch a column is frequently referred as “[unbound]({%slug gridview-columns-bound-unbound-columns%})” column. +>tip Such a column is frequently referred as “[unbound]({%slug gridview-columns-bound-unbound-columns%})” column. A typical usage of such column involves setting the __CellStyle__/__CellTemplate__ properties in order to place custom content within the cells such as buttons, checkboxes or even composite user controls rather than displaying data from the items source. You can check the [Setting CellTemplate and CellEditTemplate]({%slug radgridview-columns-celltemplate-and-celledittemplate%}) article for more information on how to define your own CellTemplate or CellEditTemplate. diff --git a/controls/radgridview/columns/columntypes/image-column.md b/controls/radgridview/columns/columntypes/image-column.md index 81af4825ed..0ee6ce11d5 100644 --- a/controls/radgridview/columns/columntypes/image-column.md +++ b/controls/radgridview/columns/columntypes/image-column.md @@ -20,7 +20,7 @@ Here is a list of the most important properties. * __ImageWidth__ - width of the images displayed in the column. ->tipYou can bind GridViewImageColumn to a __string or a byte[] data__ via DataMemberBinding property. +>tip You can bind GridViewImageColumn to a __string or a byte[] data__ via DataMemberBinding property. __Example 1: Define GridViewImageColumn in XAML.__ diff --git a/controls/radgridview/columns/how-to/create-custom-column-editor.md b/controls/radgridview/columns/how-to/create-custom-column-editor.md index a953020b07..cbc799b24c 100644 --- a/controls/radgridview/columns/how-to/create-custom-column-editor.md +++ b/controls/radgridview/columns/how-to/create-custom-column-editor.md @@ -477,7 +477,7 @@ __Example 7: The MyConverter class__ ![Creating Custom Column Editor in RadGridView - Telerik's {{ site.framework_name }} DataGrid](images/gridview-howto-create-custom-column-editor.png) ->tipYou can download a runnable project of the previous example from the online SDK repository [CustomColumnEditor](https://github.com/telerik/xaml-sdk/tree/master/GridView/CustomColumnEditor). +>tip You can download a runnable project of the previous example from the online SDK repository [CustomColumnEditor](https://github.com/telerik/xaml-sdk/tree/master/GridView/CustomColumnEditor). >You can also check the [SDK Samples Browser]({%slug sdk-samples-browser%}) that provides a more convenient approach to exploring and executing the examples in the Telerik XAML SDK repository. diff --git a/controls/radgridview/columns/how-to/read-only-rows-cells.md b/controls/radgridview/columns/how-to/read-only-rows-cells.md index c93f6b8412..8b5ebc9900 100644 --- a/controls/radgridview/columns/how-to/read-only-rows-cells.md +++ b/controls/radgridview/columns/how-to/read-only-rows-cells.md @@ -44,7 +44,7 @@ __Example 2: Binding IsReadOnlyBinding at column level.__ In both cases the property to which IsReadOnlyBinding is bound is exposed by the business object. In the example above "IsActive" as well as "Age" are properties of one and the same data item. ->tipYou can download a __runnable project__ illustrating the different setups from our online SDK repository [here](https://github.com/telerik/xaml-sdk/tree/master/GridView/ReadOnlyBinding). +>tip You can download a __runnable project__ illustrating the different setups from our online SDK repository [here](https://github.com/telerik/xaml-sdk/tree/master/GridView/ReadOnlyBinding). >You can also check the [SDK Samples Browser]({%slug sdk-samples-browser%}) that provides a more convenient approach in exploring and executing the examples in the Telerik XAML SDK repository. diff --git a/controls/radgridview/columns/how-to/set-sortingstate-on-column.md b/controls/radgridview/columns/how-to/set-sortingstate-on-column.md index 8080f16251..4d38824cfa 100644 --- a/controls/radgridview/columns/how-to/set-sortingstate-on-column.md +++ b/controls/radgridview/columns/how-to/set-sortingstate-on-column.md @@ -26,7 +26,7 @@ __Example 1: Setting SortingState for a column.__ Once you define all the necessary properties, the corresponding column will be set in an Ascending sorting order. Furthermore, you will be able to handle the Sorting event of the RadGridView and perform any additional logic that you need. ->tipFor further information on implementing custom sorting you may run through the [Custom Sorting]({%slug gridview-sorting-custom%}) article. +>tip For further information on implementing custom sorting you may run through the [Custom Sorting]({%slug gridview-sorting-custom%}) article. # See also diff --git a/controls/radgridview/columns/how-to/wrap-text-column-header.md b/controls/radgridview/columns/how-to/wrap-text-column-header.md index 0a6fb5d20f..979dd5454e 100644 --- a/controls/radgridview/columns/how-to/wrap-text-column-header.md +++ b/controls/radgridview/columns/how-to/wrap-text-column-header.md @@ -46,7 +46,7 @@ We will take advantage of the fact that the __Header__ property of the GridView ``` ->importantPlease note that this approach can cause issues if you're binding the header to another control's content, for example, the Content of the CheckBoxes from the example in the [Control Panel]({%slug gridview-overview-controlpanel%}) article. In this case, you need to make sure that you're creating a copy of the TextBlock or use a converter to only access its Text property. +>important Please note that this approach can cause issues if you're binding the header to another control's content, for example, the Content of the CheckBoxes from the example in the [Control Panel]({%slug gridview-overview-controlpanel%}) article. In this case, you need to make sure that you're creating a copy of the TextBlock or use a converter to only access its Text property. ## See also * [Column Headers]({%slug gridview-columns-column-headers%}) diff --git a/controls/radgridview/commands/keyboardcommandprovider.md b/controls/radgridview/commands/keyboardcommandprovider.md index 3a4352c1f5..482e94852b 100644 --- a/controls/radgridview/commands/keyboardcommandprovider.md +++ b/controls/radgridview/commands/keyboardcommandprovider.md @@ -92,8 +92,8 @@ The last thing to be done is to set __KeyboardCommandProvider__ Property of the ``` ->tipYou can download a runnable project of the previous example from our online SDK repository [here](https://github.com/telerik/xaml-sdk/tree/master/GridView/CustomKeyboardCommandProvider). +>tip You can download a runnable project of the previous example from our online SDK repository [here](https://github.com/telerik/xaml-sdk/tree/master/GridView/CustomKeyboardCommandProvider). >You can also check the [SDK Samples Browser]({%slug sdk-samples-browser%}) that provides a more convenient approach in exploring and executing the examples in the Telerik XAML SDK repository. ->tipFor some additional details you can also check [this blog post](http://blogs.telerik.com/xamlteam/posts/10-06-30/how---to-change-the-default-keyboard-behavior-in-radgridview-for-silverlight-wpf.aspx) +>tip For some additional details you can also check [this blog post](http://blogs.telerik.com/xamlteam/posts/10-06-30/how---to-change-the-default-keyboard-behavior-in-radgridview-for-silverlight-wpf.aspx) diff --git a/controls/radgridview/events/edit.md b/controls/radgridview/events/edit.md index 1100aa2ce7..b3896cbeaf 100644 --- a/controls/radgridview/events/edit.md +++ b/controls/radgridview/events/edit.md @@ -268,7 +268,7 @@ The __RowEditEnded__ event occurs when row validation passed successfully and ne * __EditOperationType__ - Gets the edit operation type. ->tipThe __EditOperationType__ property is a __EditOperationType__ enumeration, which exposes the following values: +>tip The __EditOperationType__ property is a __EditOperationType__ enumeration, which exposes the following values: * __Insert__ @@ -314,7 +314,7 @@ The example below uses the __RowEditEnded__ to display the new data of the edite End Sub ``` ->tipThe __CellEditEnded__ event is always fired before __RowEditEnded__ event. +>tip The __CellEditEnded__ event is always fired before __RowEditEnded__ event. ## See Also diff --git a/controls/radgridview/events/export-events.md b/controls/radgridview/events/export-events.md index 8a1e597501..03d306970a 100644 --- a/controls/radgridview/events/export-events.md +++ b/controls/radgridview/events/export-events.md @@ -153,7 +153,7 @@ The event handler expects a __GridViewElementExportedToDocumentEventArgs__ argum ## InitializingExcelMLStyles (ExcelML only) ->tipThis event will be only raised when exporting with __ExportFormat.ExcelML__. +>tip This event will be only raised when exporting with __ExportFormat.ExcelML__. You can define a style when the __InitializingExcelMLStyles__ event is raised, as shown in __Example 4__. diff --git a/controls/radgridview/export/events/elementexporting-elementexported-todocument.md b/controls/radgridview/export/events/elementexporting-elementexported-todocument.md index b987ca645b..189bf48be3 100644 --- a/controls/radgridview/export/events/elementexporting-elementexported-todocument.md +++ b/controls/radgridview/export/events/elementexporting-elementexported-todocument.md @@ -60,7 +60,7 @@ The event handler expects __GridViewElementExportedToDocumentEventArgs__ argumen ## InitializingExcelMLStyles (ExcelML only) ->tipThis event will be only raised when exporting with __ExportFormat.ExcelML__ +>tip This event will be only raised when exporting with __ExportFormat.ExcelML__ You can define a Style when __InitializingExcelMLStyles__ event is raised. For example: diff --git a/controls/radgridview/export/events/elementexporting-elementexported.md b/controls/radgridview/export/events/elementexporting-elementexported.md index 2e29520e56..bdd9b575c9 100644 --- a/controls/radgridview/export/events/elementexporting-elementexported.md +++ b/controls/radgridview/export/events/elementexporting-elementexported.md @@ -134,7 +134,7 @@ You can use these contexts to conditionally style and format the exported elemen ## InitializingExcelMLStyles (ExcelML only) ->tipThis event will be only raised when exporting with __ExportFormat.ExcelML__ +>tip This event will be only raised when exporting with __ExportFormat.ExcelML__ You can define a Style when __InitializingExcelMLStyles__ event is raised. For example: diff --git a/controls/radgridview/export/events/initializing-excelml-styles.md b/controls/radgridview/export/events/initializing-excelml-styles.md index eecad023d5..75e2bbd690 100644 --- a/controls/radgridview/export/events/initializing-excelml-styles.md +++ b/controls/radgridview/export/events/initializing-excelml-styles.md @@ -10,7 +10,7 @@ position: 4 # InitializingExcelMLStyles ->tipThis event will be only raised when exporting with __ExportFormat.ExcelML__ +>tip This event will be only raised when exporting with __ExportFormat.ExcelML__ You can define a Style when __InitializingExcelMLStyles__ event is raised. For example: diff --git a/controls/radgridview/export/excel/export-xlsx.md b/controls/radgridview/export/excel/export-xlsx.md index e8e9ce7d56..eca67bc687 100644 --- a/controls/radgridview/export/excel/export-xlsx.md +++ b/controls/radgridview/export/excel/export-xlsx.md @@ -73,7 +73,7 @@ __Example 1: Use of ExportToXlsx Method__ >To export the Default Styles of RadGridView in grouped state, at least one row must be expanded, so that the exporting engine can get the styles. ->importantExporting the Default Styles will take into account the styling applied to the __first element__ of each type(cell, column header, etc.). This is due to performance optimizations. Exporting a separate style for the needed element is discussed in details here:[Style Exported XLSX & PDF Documents]({%slug gridview-export-style-exported-xlsx-pdf-documents%}). +>important Exporting the Default Styles will take into account the styling applied to the __first element__ of each type(cell, column header, etc.). This is due to performance optimizations. Exporting a separate style for the needed element is discussed in details here:[Style Exported XLSX & PDF Documents]({%slug gridview-export-style-exported-xlsx-pdf-documents%}). RadGridView can be exported with its default styles by setting the __ExportDefaultStyles__ property to __True__ diff --git a/controls/radgridview/export/how-to/export-string.md b/controls/radgridview/export/how-to/export-string.md index 6fe64599f7..8eb8c18df5 100644 --- a/controls/radgridview/export/how-to/export-string.md +++ b/controls/radgridview/export/how-to/export-string.md @@ -15,7 +15,7 @@ __PROBLEM__ When exporting a RadGridView to Excel using __ExportFormat.HTML__, the string values that can be converted to numbers, are opened in Excel as numbers. ->tipThis behavior does not occur when exporting using __ExportFormat.ExcelML__. +>tip This behavior does not occur when exporting using __ExportFormat.ExcelML__. __CAUSE__ diff --git a/controls/radgridview/export/pdf/export-pdf.md b/controls/radgridview/export/pdf/export-pdf.md index 81f1a6718b..d80579f639 100644 --- a/controls/radgridview/export/pdf/export-pdf.md +++ b/controls/radgridview/export/pdf/export-pdf.md @@ -73,7 +73,7 @@ __Example 1: Usage of Method ExportToPdf__ >To export the default styles of RadGridView in grouped state, at least one row must be expanded, so that the exporting engine can get the styles. ->importantExporting the Default Styles will take into account the styling applied to the __first element__ of each type(cell, column header, etc.). This is due to performance optimizations. Exporting a separate style for the needed element is discussed in details here:[Style Exported XLSX & PDF Documents]({%slug gridview-export-style-exported-xlsx-pdf-documents%}). +>important Exporting the Default Styles will take into account the styling applied to the __first element__ of each type(cell, column header, etc.). This is due to performance optimizations. Exporting a separate style for the needed element is discussed in details here:[Style Exported XLSX & PDF Documents]({%slug gridview-export-style-exported-xlsx-pdf-documents%}). RadGridView can be exported with its default styles by setting the ExportDefaultStyles property to “true” diff --git a/controls/radgridview/features/merged-cells.md b/controls/radgridview/features/merged-cells.md index e82ed59b6f..95e2e41519 100644 --- a/controls/radgridview/features/merged-cells.md +++ b/controls/radgridview/features/merged-cells.md @@ -30,7 +30,7 @@ When the RadGridView is setup, you can configure it to display the merged cells * __Horizontal__ ->importantMerged Cells are only supported with __GroupRenderMode=”Flat”__. You can check the [Rendering Modes]({%slug gridview-grouping-groupingmodes%}) article for further details on it. +>important Merged Cells are only supported with __GroupRenderMode=”Flat”__. You can check the [Rendering Modes]({%slug gridview-grouping-groupingmodes%}) article for further details on it. >Currently, frozen columns are not supported while having merged cells enabled. An exception will be thrown: "Cell merging is not supported when frozen columns are enabled.”. diff --git a/controls/radgridview/features/overview-filtering.md b/controls/radgridview/features/overview-filtering.md index b6a9fc9627..3c73cedee8 100644 --- a/controls/radgridview/features/overview-filtering.md +++ b/controls/radgridview/features/overview-filtering.md @@ -86,7 +86,7 @@ You could localize those strings. For the complete list of the localization stri >The list of filter operations depends on the __DataType__ property of the column. For example, the filter operations "__StartsWith__", "__EndsWith__, "__IsEmpty__, "__IsNotEmpty__... " will not be available for columns of __Integer__ or __DateTime__ types. ->tipConsider using the code-behind approach only when changing the filtering criteria __run-time__. +>tip Consider using the code-behind approach only when changing the filtering criteria __run-time__. Check out the chapters entirely dedicated to the filtering functionality of __RadGridView__ and find the answers to many questions like: diff --git a/controls/radgridview/features/overview-grouping.md b/controls/radgridview/features/overview-grouping.md index 53db840881..42034c823e 100644 --- a/controls/radgridview/features/overview-grouping.md +++ b/controls/radgridview/features/overview-grouping.md @@ -55,7 +55,7 @@ __Example 1: Grouping applied programmatically__ >Тhe __GroupDescriptors__ property of RadGridView is a __collection__ so you can add more than one __GroupDescriptor__ to a certain __RadGridView__. ->tipConsider using the code-behind approach only when changing the grouping criteria __run-time__. +>tip Consider using the code-behind approach only when changing the grouping criteria __run-time__. Check out the chapters entirely dedicated to the grouping functionality of __RadGridView__ and find the answers to the following questions: diff --git a/controls/radgridview/features/overview-keyboard-support.md b/controls/radgridview/features/overview-keyboard-support.md index e7eccb1761..ff0c394529 100644 --- a/controls/radgridview/features/overview-keyboard-support.md +++ b/controls/radgridview/features/overview-keyboard-support.md @@ -87,7 +87,7 @@ __Subscribe to KeyDown and KeyUp events__ ``` ->tipIt is always a good practice to attach your event handlers in the XAML, whenever your application logic allows this. +>tip It is always a good practice to attach your event handlers in the XAML, whenever your application logic allows this. The implementation of both event handlers is located in the code-behind file (C# or VB.NET) and looks like this: diff --git a/controls/radgridview/features/overview-lightweight-template.md b/controls/radgridview/features/overview-lightweight-template.md index 724783e4de..bfa4f5edb2 100644 --- a/controls/radgridview/features/overview-lightweight-template.md +++ b/controls/radgridview/features/overview-lightweight-template.md @@ -20,7 +20,7 @@ With __2013 Q2 SP__ we have introduced lightweight templates for __RadGridView a They are represented by several additional __simplified styles, which you can merge in your project__. The main idea of simplifying templates of different parts of RadGridView is to limit the number of visual elements within the templates in order to __speed up the performance__ of __RadGridView/RadTreeListView__. ->importantThe Lightweight Templates can only be applied with NoXaml binaries and Implicit Themes. You can find more information on them [here]({%slug styling-apperance-implicit-styles-overview%}). +>important The Lightweight Templates can only be applied with NoXaml binaries and Implicit Themes. You can find more information on them [here]({%slug styling-apperance-implicit-styles-overview%}). {% if site.site_name == 'WPF' %} >tip The performance on loading the visual elements will be increased __up to 50%__ when the lightweight templates are applied.{% endif %} @@ -87,7 +87,7 @@ __Example 2: Applying Lightweight Templates with Validation__ >__GridViewRowCoreValidationStyle__ contains a row indicator, which you can use to perform validation. ->tipFor __RadGridView__ you need to merge only the CoreStyles for __GridViewCell and GridViewRow__. For __RadTreeListView__ you need to merge the styles for __GridViewCell and TreeListViewRow__. +>tip For __RadGridView__ you need to merge only the CoreStyles for __GridViewCell and GridViewRow__. For __RadTreeListView__ you need to merge the styles for __GridViewCell and TreeListViewRow__. ## Remove the Border of the Current Cell diff --git a/controls/radgridview/features/overview-sorting.md b/controls/radgridview/features/overview-sorting.md index 5e3529fbaf..721a7439dc 100644 --- a/controls/radgridview/features/overview-sorting.md +++ b/controls/radgridview/features/overview-sorting.md @@ -50,9 +50,9 @@ You can achieve the same result if you define your sorting criteria in the code- >Note that since __SortDescriptors__ property is a __collection__, you can add more than one __SortDescriptor__ to a __RadGridView__. ->tipConsider using the code-behind approach only when changing the sorting criteria __run-time__. +>tip Consider using the code-behind approach only when changing the sorting criteria __run-time__. ->importantIf the RadGridView is bound to a collection that inherits __ICollectionView__ that has a __CanSort__ property set to __true__, the RadGridView`s sorting is disabled and the sorting mechanism of the collection is used instead. +>important If the RadGridView is bound to a collection that inherits __ICollectionView__ that has a __CanSort__ property set to __true__, the RadGridView`s sorting is disabled and the sorting mechanism of the collection is used instead. Check out the chapters entirely dedicated to the sorting functionality of __RadGridView__ and find the answers to the following questions: diff --git a/controls/radgridview/features/pinned-rows.md b/controls/radgridview/features/pinned-rows.md index 35f20a38e4..4a95390d20 100644 --- a/controls/radgridview/features/pinned-rows.md +++ b/controls/radgridview/features/pinned-rows.md @@ -12,7 +12,7 @@ position: 17 Since **R2 2016**, RadGridView supports **Pinned Rows**. By using Pinned Rows, you can pin particular rows to the top or bottom of your **RadGridView** so that they do not participate in the vertical scrolling. ->importantCurrently, [RowDetails]({%slug radgridview-row-details-overview%}), [Merged Cells]({%slug gridview-merged-cells%}) and [Extended selection]({%slug gridview-multiple-selection%}) are not supported when pinning rows. +>important Currently, [RowDetails]({%slug radgridview-row-details-overview%}), [Merged Cells]({%slug gridview-merged-cells%}) and [Extended selection]({%slug gridview-multiple-selection%}) are not supported when pinning rows. In this article, we will discuss the following topics: diff --git a/controls/radgridview/features/search-as-you-type.md b/controls/radgridview/features/search-as-you-type.md index e6d0aff6c3..e24d3592cf 100644 --- a/controls/radgridview/features/search-as-you-type.md +++ b/controls/radgridview/features/search-as-you-type.md @@ -153,7 +153,7 @@ __Stop the searching based on a condition__ The `Searched` event will be raised when the grid data has been searched. It's arguments are of type `GridViewSearchedEventArgs` and contain the value of the text which was entered in the search panel `TextBox` - `SearchText`. ->tipFor more information, refer to the [Overview]({%slug gridview-events-overview%}) article. +>tip For more information, refer to the [Overview]({%slug gridview-events-overview%}) article. ## Modify the Searching Criteria diff --git a/controls/radgridview/filtering/basic.md b/controls/radgridview/filtering/basic.md index 79daa665d3..d07059295a 100644 --- a/controls/radgridview/filtering/basic.md +++ b/controls/radgridview/filtering/basic.md @@ -48,7 +48,7 @@ The filtering control that the user is presented with has two parts. The upper p The string representations that are displayed to the user are produced by taking the raw distinct value from the source collection and then applying the column’s `DataMemberBinding` `IValueConverter` or `DataFormatString` if any are defined. For example, if you have specified a *currency* DataFormatString for your column, the user will see a nicely formatted *$2.22* in the distinct values list. However, underneath this nicely formatted string the original *Float* value will be preserved and will be used for performing the actual filtering inside the data engine. ->importantUsing an IValueConverter or DataFormatstring will not affect the data operations in any way. They are used for UI purposes only and do not play any role in the data engine. Filtering is always performed with the raw data values. +>important Using an IValueConverter or DataFormatstring will not affect the data operations in any way. They are used for UI purposes only and do not play any role in the data engine. Filtering is always performed with the raw data values. By default, only the first 1000 distinct values will be shown. The amount of distinct values displayed can easily be configured as described in [this article]({%slug gridview-filtering-howto-display-all-distinct-values%}). diff --git a/controls/radgridview/filtering/faq/dataformatstring-and-filtering.md b/controls/radgridview/filtering/faq/dataformatstring-and-filtering.md index e1a46b7f62..7de5c03b72 100644 --- a/controls/radgridview/filtering/faq/dataformatstring-and-filtering.md +++ b/controls/radgridview/filtering/faq/dataformatstring-and-filtering.md @@ -20,7 +20,7 @@ The __DataFormatString is only used for presentation purposes__. It plays absolu Each GridViewColumn has a property called __FilterMemberPath__. You can use this property to tell the column to __filter on a property different from the one it displays__ in its cells. ->tipFor example: FilterMemberPath="PropertyToFilterOn". You can also check the [FilterMemberPath documentation]({%slug gridview-filtering-basic%}). +>tip For example: FilterMemberPath="PropertyToFilterOn". You can also check the [FilterMemberPath documentation]({%slug gridview-filtering-basic%}). ## See Also diff --git a/controls/radgridview/filtering/faq/datetime-filtering.md b/controls/radgridview/filtering/faq/datetime-filtering.md index d38ae59c66..38cad153bd 100644 --- a/controls/radgridview/filtering/faq/datetime-filtering.md +++ b/controls/radgridview/filtering/faq/datetime-filtering.md @@ -28,14 +28,14 @@ The user can be instructed to enter both the date and time parts of the date whe Bind the column __directly to the Date (or Year)__ property of the __DateTime__ object. ->tipFor example: DataMemberBinding="{Binding BirthDate.Date}" +>tip For example: DataMemberBinding="{Binding BirthDate.Date}" >Columns bound to the __Date__ part of a __Nullable DateTime__ does not support filtering, as a __Nullable DateTime__ does not expose a __Date__ property. As alternative solution, you can benefit from a property called __FilterMemberPath__. You can use it to tell the column to __filter on a property different from the one it displays__ in its cells. ->tipFor example: **FilterMemberPath="BirthDate.Date"**. You can also check the [FilterMemberPath documentation]({%slug gridview-filtering-basic%}). +>tip For example: **FilterMemberPath="BirthDate.Date"**. You can also check the [FilterMemberPath documentation]({%slug gridview-filtering-basic%}). ## See Also diff --git a/controls/radgridview/filtering/how-to/disable-filtering-for-a-specific-column.md b/controls/radgridview/filtering/how-to/disable-filtering-for-a-specific-column.md index b1259d13b1..24b0ecd947 100644 --- a/controls/radgridview/filtering/how-to/disable-filtering-for-a-specific-column.md +++ b/controls/radgridview/filtering/how-to/disable-filtering-for-a-specific-column.md @@ -41,7 +41,7 @@ __Example 2: Disable the filtering of the Name column when generating it__ ![The Name column with disabled filtering](images/disable-filter.png) ->importantIf the data displayed in the column is not filterable in the first place, setting the IsFilterable property will not have any effect. To learn what your objects need to implement for the column to become filterable, please have a look at the [Filter a Custom Type]({%slug gridview-filtering-howto-filter-a-custom-type%}) article. +>important If the data displayed in the column is not filterable in the first place, setting the IsFilterable property will not have any effect. To learn what your objects need to implement for the column to become filterable, please have a look at the [Filter a Custom Type]({%slug gridview-filtering-howto-filter-a-custom-type%}) article. ## See Also diff --git a/controls/radgridview/filtering/programmatic.md b/controls/radgridview/filtering/programmatic.md index 6ad07fe1c2..dfe1c96908 100644 --- a/controls/radgridview/filtering/programmatic.md +++ b/controls/radgridview/filtering/programmatic.md @@ -213,7 +213,7 @@ When choosing the **Operator**, you have to make sure that the respective **Memb | IsLessThan, IsLessThanOrEqualTo, IsGreaterThan, IsGreaterThanOrEqualTo | Numeric types, DateTime, TimeSpan, all types that overload these operators | | IsNull, IsNotNull | All filterable null-able types | ->tipYou could localize those strings. For the complete list of the localization strings please check this [how to topic]({%slug gridview-filtering-howto-localize-the-filtering-ui%}). +>tip You could localize those strings. For the complete list of the localization strings please check this [how to topic]({%slug gridview-filtering-howto-localize-the-filtering-ui%}). To help you understand how this FilterDescriptor is used by the data engine, let’s give a practical example with the one we have created above. The data engine will build a LINQ expression based on the information it reads from the FilterDescriptor instance. It will then execute this query against the query provider of RadGridView’s source collection. Here is what the expression would be for this FilterDescriptor in pseudo-code: @@ -318,7 +318,7 @@ As you might have already guessed, the IColumnFilterDescriptor that is used for Notice how this hierarchy is the same as the Popup filtering control layout. Working through the IColumnFilterDescriptor interface makes sure that you cannot randomly add criteria which cannot be correctly displayed by the Popup filtering control. ->tipYou can check some sample code on the {% if site.site_name == 'Silverlight' %}[Programmatic Filtering Demo](https://demos.telerik.com/silverlight/#GridView/ProgrammaticFiltering){% endif %}{% if site.site_name == 'WPF' %}[Programmatic Filtering Demo](https://demos.telerik.com/wpf){% endif %}. +>tip You can check some sample code on the {% if site.site_name == 'Silverlight' %}[Programmatic Filtering Demo](https://demos.telerik.com/silverlight/#GridView/ProgrammaticFiltering){% endif %}{% if site.site_name == 'WPF' %}[Programmatic Filtering Demo](https://demos.telerik.com/wpf){% endif %}. ## See Also diff --git a/controls/radgridview/grouping/aggregates.md b/controls/radgridview/grouping/aggregates.md index 72796b0a87..0f20b91a00 100644 --- a/controls/radgridview/grouping/aggregates.md +++ b/controls/radgridview/grouping/aggregates.md @@ -32,7 +32,7 @@ There are two main types of aggregate functions available which in turn serve as * __SumFunction__: Returns the **sum** of all cell values in the column. ->tipYou can also create your own custom functions similar to these by inheriting __Telerik.Windows.Data.EnumerableAggregateFunction__ or **EnumerableSelectorAggregateFunction** class. An example can be found {% if site.site_name == 'Silverlight' %} [here](https://demos.telerik.com/silverlight/#GridView/CustomAggregates){% else %}in the __Custom Aggregate Function__ RadGridView example from our [demos](https://demos.telerik.com/wpf/){% endif %}. +>tip You can also create your own custom functions similar to these by inheriting __Telerik.Windows.Data.EnumerableAggregateFunction__ or **EnumerableSelectorAggregateFunction** class. An example can be found {% if site.site_name == 'Silverlight' %} [here](https://demos.telerik.com/silverlight/#GridView/CustomAggregates){% else %}in the __Custom Aggregate Function__ RadGridView example from our [demos](https://demos.telerik.com/wpf/){% endif %}. Each aggregate function has a caption and a result, which are displayed next to the group title. diff --git a/controls/radgridview/grouping/groupingmodes.md b/controls/radgridview/grouping/groupingmodes.md index 1d53db11b9..2296bd6222 100644 --- a/controls/radgridview/grouping/groupingmodes.md +++ b/controls/radgridview/grouping/groupingmodes.md @@ -16,7 +16,7 @@ __Nested__: This is the default value and it will nest __GridViewGroupRows__ int __Flat__: This mode represents our new virtualization mechanism with a completely new item container generator. It simply renders rows one below the other and all rows are on the same level. The visual element representing the grouped row is __GroupHeaderRow__. ->importantFor compatibility reasons, the Nested render mode is also preserved, but it is highly recommended to use the new Flat mode as it leads to better performance and most of the latest features and bug fixes only target this mode. +>important For compatibility reasons, the Nested render mode is also preserved, but it is highly recommended to use the new Flat mode as it leads to better performance and most of the latest features and bug fixes only target this mode. >Please note that when you use the __Flat mode__, you should work with __GroupHeaderRow__, not __GridViewGroupRow__. diff --git a/controls/radgridview/grouping/modify-grouptemplates.md b/controls/radgridview/grouping/modify-grouptemplates.md index 1f481b792d..2cd4a2a11a 100644 --- a/controls/radgridview/grouping/modify-grouptemplates.md +++ b/controls/radgridview/grouping/modify-grouptemplates.md @@ -12,7 +12,7 @@ position: 8 This article explains how you can modify the default header and footer templates of the group row. You can do that by predefining the `GroupHeaderTemplate` and `GroupFooterTemplate` properties. ->tipLearn more about the GridView visual structure in [this article]({%slug gridview-visual-structure%}). +>tip Learn more about the GridView visual structure in [this article]({%slug gridview-visual-structure%}). >Please note that the DataContext of the group row is {% if site.site_name == 'WPF' %}[GroupViewModel](https://docs.telerik.com/devtools/wpf/api/telerik.windows.controls.gridview.groupviewmodel){% endif %}{% if site.site_name == 'Silverlight' %}[GroupViewModel](https://docs.telerik.com/devtools/silverlight/api/telerik.windows.controls.gridview.groupviewmodel){% endif %}. As you can check in the API reference, this class contains properties like Group, Column, AggregateResults, etc. Having this in mind you can bind the TextBlock-s in the GroupHeaderTemplate to the values of the properties in the GroupViewModel. diff --git a/controls/radgridview/grouping/modifying-group-panel.md b/controls/radgridview/grouping/modifying-group-panel.md index 2d7c188015..8062ecba8c 100644 --- a/controls/radgridview/grouping/modifying-group-panel.md +++ b/controls/radgridview/grouping/modifying-group-panel.md @@ -12,7 +12,7 @@ position: 6 __RadGridView__ exposes two properties - __GroupPanelBackground__ and __GroupPanelForeground__ which allow you to make basic modifications of the __Group Panel__ (area). ->tipThe __GridView__ also exposes two style properties - __GroupPanelStyle__ and __GroupPanelItemStyle__. To learn how to use them in order to style the __Group Panel__ read [here]({%slug radgridview-styles-and-templates-styling-the-group-panel%}). +>tip The __GridView__ also exposes two style properties - __GroupPanelStyle__ and __GroupPanelItemStyle__. To learn how to use them in order to style the __Group Panel__ read [here]({%slug radgridview-styles-and-templates-styling-the-group-panel%}). >[Here]({%slug gridview-visual-structure%}) you can read more information about the visual structure of the __RadGridView__. diff --git a/controls/radgridview/hierarchical-gridview/basic-hierarchies.md b/controls/radgridview/hierarchical-gridview/basic-hierarchies.md index 9559fec6cb..2ae3473d3d 100644 --- a/controls/radgridview/hierarchical-gridview/basic-hierarchies.md +++ b/controls/radgridview/hierarchical-gridview/basic-hierarchies.md @@ -66,7 +66,7 @@ __Example 4: Adding the GridViewTableDefinition to the ChildTableDefinitions pro Me.radGridView.ChildTableDefinitions.Add(d) ``` ->tipThe __GridViewTableDefinition__ object also exposes a __ChildTableDefinitions__ property, which means that you can nest grids on more than one level. +>tip The __GridViewTableDefinition__ object also exposes a __ChildTableDefinitions__ property, which means that you can nest grids on more than one level. ## Check If a Hierarchy Item Is Expanded diff --git a/controls/radgridview/how-to/access-filtered-and-sorted-items.md b/controls/radgridview/how-to/access-filtered-and-sorted-items.md index 94b57d38b4..c590b8732d 100644 --- a/controls/radgridview/how-to/access-filtered-and-sorted-items.md +++ b/controls/radgridview/how-to/access-filtered-and-sorted-items.md @@ -26,7 +26,7 @@ Eventually, we would like to filter and sort the RadGridView: You can access the items that remain after the data operations are applied through the __Items__ property, as the __ItemsSource__ will remain unchanged. ->tipThe __Items__ collection will be sorted according to the applied changes. Grouping the __RadGridView__ might also result in reordering the collection. +>tip The __Items__ collection will be sorted according to the applied changes. Grouping the __RadGridView__ might also result in reordering the collection. ## See Also diff --git a/controls/radgridview/how-to/create-tooltip.md b/controls/radgridview/how-to/create-tooltip.md index 9c871e340e..f953111e46 100644 --- a/controls/radgridview/how-to/create-tooltip.md +++ b/controls/radgridview/how-to/create-tooltip.md @@ -78,7 +78,7 @@ __Example 4: Setting custom style to the HeaderCellStyle property__ ``` ->tipYou can define the DataTemplate as a StaticResource and then directly assign the HeaderCellStyle property of the GridViewColumn. +>tip You can define the DataTemplate as a StaticResource and then directly assign the HeaderCellStyle property of the GridViewColumn. * Predefine the Header for the column. diff --git a/controls/radgridview/how-to/customize-ui-programmatically.md b/controls/radgridview/how-to/customize-ui-programmatically.md index 3e4ed982c1..487758a7e8 100644 --- a/controls/radgridview/how-to/customize-ui-programmatically.md +++ b/controls/radgridview/how-to/customize-ui-programmatically.md @@ -15,7 +15,7 @@ You can manipulate the controls easily with two powerful extension methods: * __ParentOfType<>__ * __ChildrenOfType<>__. ->tipYou can access all items currently available in RadGridView through __RadGridView.Items__ collection. +>tip You can access all items currently available in RadGridView through __RadGridView.Items__ collection. >Generally we do not recommend working with the visual elements as RadGridView is a virtualized control and its elements are reused as they go in and out the visual area. You can check the topic on [UI virtualization]({%slug radgridview-features-ui-virtualization%}) for further information. diff --git a/controls/radgridview/how-to/show-hide-columns-outside-of-the-radgridview.md b/controls/radgridview/how-to/show-hide-columns-outside-of-the-radgridview.md index 18bec8a8e6..86a47bcc84 100644 --- a/controls/radgridview/how-to/show-hide-columns-outside-of-the-radgridview.md +++ b/controls/radgridview/how-to/show-hide-columns-outside-of-the-radgridview.md @@ -81,5 +81,5 @@ After that define __DataTemplate__ for __ItemTemplate__ property of the ListBox. Provide RadGridView with an appropriate data source and run your application. The result should be similar to this snapshot: ![Telerik {{ site.framework_name }} DataGrid Telerik {{ site.framework_name }} DataGrid how to column chooser 2](images/RadGridView_radgridview_how_to_column_chooser_2.png) ->tipYou can download a runnable project of the previous example from our online SDK repository: [ColumnChooser](https://github.com/telerik/xaml-sdk/tree/master/GridView/ColumnChooser). +>tip You can download a runnable project of the previous example from our online SDK repository: [ColumnChooser](https://github.com/telerik/xaml-sdk/tree/master/GridView/ColumnChooser). diff --git a/controls/radgridview/localization/localization2.md b/controls/radgridview/localization/localization2.md index a3c9bc8d7e..3cba636bf6 100644 --- a/controls/radgridview/localization/localization2.md +++ b/controls/radgridview/localization/localization2.md @@ -25,7 +25,7 @@ Here is a list of the supported languages: ![Telerik {{ site.framework_name }} DataGrid Localization 4](images/RadGridView_Localization_4.png) ->tipTo learn more about the ways to localize the RadControls please read the common topic on [Localization]({%slug common-localization%}). +>tip To learn more about the ways to localize the RadControls please read the common topic on [Localization]({%slug common-localization%}). >__In order to dynamically localize the GridView at runtime, you should recreate it.__ diff --git a/controls/radgridview/overview2.md b/controls/radgridview/overview2.md index d6f9d2be72..bb21d3458f 100644 --- a/controls/radgridview/overview2.md +++ b/controls/radgridview/overview2.md @@ -69,7 +69,7 @@ Check out the online demo [here.](https://demos.telerik.com/silverlight/#GridVie Check out the WPF demos [here.](https://demos.telerik.com/wpf/){% endif %} ->tipYou can find more examples of how to implement various scenarios available for download from our online SDK repository [here. ](https://github.com/telerik/xaml-sdk/)Look for examples listed under __GridView__. For a better and easier reviewing of our examples you can download the [SDK Samples Browser.](https://demos.telerik.com/xaml-sdkbrowser//) +>tip You can find more examples of how to implement various scenarios available for download from our online SDK repository [here. ](https://github.com/telerik/xaml-sdk/)Look for examples listed under __GridView__. For a better and easier reviewing of our examples you can download the [SDK Samples Browser.](https://demos.telerik.com/xaml-sdkbrowser//) {% if site.site_name == 'WPF' %} ## Telerik UI for WPF Support and Learning Resources diff --git a/controls/radgridview/populating-with-data/binding-to-dataset.md b/controls/radgridview/populating-with-data/binding-to-dataset.md index 76ba013a37..3440fa6088 100644 --- a/controls/radgridview/populating-with-data/binding-to-dataset.md +++ b/controls/radgridview/populating-with-data/binding-to-dataset.md @@ -154,7 +154,7 @@ __Example 1: Setting up the ViewModel__ End Class ``` ->importantPlease note that the **DataRelation** is required for RadGridView to generate the hierarchy automatically. +>important Please note that the **DataRelation** is required for RadGridView to generate the hierarchy automatically. __Example 2__ demonstrates how the RadGridView is set up in XAML. diff --git a/controls/radgridview/populating-with-data/in-memory-date.md b/controls/radgridview/populating-with-data/in-memory-date.md index dc0b073339..5c7240a772 100644 --- a/controls/radgridview/populating-with-data/in-memory-date.md +++ b/controls/radgridview/populating-with-data/in-memory-date.md @@ -144,7 +144,7 @@ Run your demo, the result can be seen on the next picture: ![Telerik {{ site.framework_name }} DataGrid PopulatingWithDataLoadFromInMemoryData 010](images/RadGridView_PopulatingWithDataLoadFromInMemoryData_010.PNG) ->tipIf you need to define the columns manually read the topic [Defining Columns]({%slug gridview-columns-defining-columns%}). +>tip If you need to define the columns manually read the topic [Defining Columns]({%slug gridview-columns-defining-columns%}). ## See Also diff --git a/controls/radgridview/populating-with-data/loading-data-from-adonet-services.md b/controls/radgridview/populating-with-data/loading-data-from-adonet-services.md index a401a23515..f5746f07c2 100644 --- a/controls/radgridview/populating-with-data/loading-data-from-adonet-services.md +++ b/controls/radgridview/populating-with-data/loading-data-from-adonet-services.md @@ -44,7 +44,7 @@ Before proceeding further with this tutorial you need to create a new applicatio Private dbContext2 As New NorthwindEntities(New Uri("Enter your service address here")) ``` ->tipFor more information about how to add a reference to an ADO.NET Data Service and how to create a new instance of the exposed entity, take a look at the [Consuming ADO.NET Data Service](http://www.telerik.com/help/wpf/consuming-data-ado-net-data-service.html) topic.The gridview control will be populated with all __Customers__ from the __Northwind__ database. Add the following code which will make the initial load of the objects. +>tip For more information about how to add a reference to an ADO.NET Data Service and how to create a new instance of the exposed entity, take a look at the [Consuming ADO.NET Data Service](http://www.telerik.com/help/wpf/consuming-data-ado-net-data-service.html) topic.The gridview control will be populated with all __Customers__ from the __Northwind__ database. Add the following code which will make the initial load of the objects. ```C# private void BeginRequest() diff --git a/controls/radgridview/populating-with-data/loading-data-from-wcf-services.md b/controls/radgridview/populating-with-data/loading-data-from-wcf-services.md index e6caf6d5ac..efd0863cd9 100644 --- a/controls/radgridview/populating-with-data/loading-data-from-wcf-services.md +++ b/controls/radgridview/populating-with-data/loading-data-from-wcf-services.md @@ -33,7 +33,7 @@ Before proceeding further with this tutorial you need to create a new applicatio Private serviceClient As New WcfServiceClient() ``` ->tipFor more information about how to add a reference to a WCF Service and how to create a new instance of a WCF Service client, take a look at the {% if site.site_name == 'Silverlight' %}[Consuming WCF Service](http://www.telerik.com/help/silverlight/consuming-data-wcf-service.html){% endif %}{% if site.site_name == 'WPF' %}[Consuming WCF Service](http://www.telerik.com/help/wpf/consuming-data-wcf-service.html){% endif %} topic. +>tip For more information about how to add a reference to a WCF Service and how to create a new instance of a WCF Service client, take a look at the {% if site.site_name == 'Silverlight' %}[Consuming WCF Service](http://www.telerik.com/help/silverlight/consuming-data-wcf-service.html){% endif %}{% if site.site_name == 'WPF' %}[Consuming WCF Service](http://www.telerik.com/help/wpf/consuming-data-wcf-service.html){% endif %} topic. * The gridview control will be populated with all __Customers__ from the __Northwind__ database. Add the following code which will make the initial load of the objects. @@ -126,7 +126,7 @@ This section will show you how to populate your __RadGridView__ control in a MVV End Class ``` ->tipFor more information about how to add a reference to a WCF Service and how to create a new instance of a WCF Service client, take a look at the [Consuming WCF Service](http://www.telerik.com/help/wpf/consuming-data-wcf-service.html) topic. +>tip For more information about how to add a reference to a WCF Service and how to create a new instance of a WCF Service client, take a look at the [Consuming WCF Service](http://www.telerik.com/help/wpf/consuming-data-wcf-service.html) topic. * Add the following code in the constructor of the __NorthwindDataSource__. It will make the initial load of all __Customers__ from the database: @@ -193,7 +193,7 @@ Run your demo, the result can be seen on the next picture: ![Telerik {{ site.framework_name }} DataGrid PopulatingWithDataLoadFromWcf 010](images/RadGridView_PopulatingWithDataLoadFromWcf_010.PNG) ->tipIf you need to define the columns manually take a look at the [Defining Columns]({%slug gridview-columns-defining-columns%}) topic. +>tip If you need to define the columns manually take a look at the [Defining Columns]({%slug gridview-columns-defining-columns%}) topic. ## See Also diff --git a/controls/radgridview/populating-with-data/loading-data-from-xml.md b/controls/radgridview/populating-with-data/loading-data-from-xml.md index d6f737ea91..89a29efc56 100644 --- a/controls/radgridview/populating-with-data/loading-data-from-xml.md +++ b/controls/radgridview/populating-with-data/loading-data-from-xml.md @@ -205,7 +205,7 @@ Run your demo, the result can be seen on the next picture: ![Telerik {{ site.framework_name }} DataGrid PopulatingWithDataLoadFromXml 020](images/RadGridView_PopulatingWithDataLoadFromXml_020.PNG) ->tipIf you need to define the columns manually read the topic [Defining Columns]({%slug gridview-columns-defining-columns%}). +>tip If you need to define the columns manually read the topic [Defining Columns]({%slug gridview-columns-defining-columns%}). ## See Also diff --git a/controls/radgridview/row-details/external-row-details.md b/controls/radgridview/row-details/external-row-details.md index d6b9d0898f..a873d6683e 100644 --- a/controls/radgridview/row-details/external-row-details.md +++ b/controls/radgridview/row-details/external-row-details.md @@ -14,7 +14,7 @@ position: 5 In order to display Row Details outside of the __RadGridView__, place a __DetailsPresenter__ control somewhere around your __RadGridView__. The only thing that you need to do in order to synchronize the __DetailsPresenter__ with the __RadGridView__ is to connect its __DetailsProvider__ property to the __RowDetailsProvider__ property of the __RadGridView__. ->tipThe __DetailsPresenter__ control used for displaying external details is exactly the same control internally used by the __RadGridView__ rows. +>tip The __DetailsPresenter__ control used for displaying external details is exactly the same control internally used by the __RadGridView__ rows. The __RowDetailsProvider__ takes care to passing the needed data (the data template, the row details style and etc) to the presenter. It doesn't matter if it is internal or external. Each time a different row is selected or the template is changed, the grid will communicate this change via its __RowDetailsProvider__ property and update the connected __DetailsPresenter__ automatically. diff --git a/controls/radgridview/row-details/overview.md b/controls/radgridview/row-details/overview.md index 0b030fd359..071d7f341a 100644 --- a/controls/radgridview/row-details/overview.md +++ b/controls/radgridview/row-details/overview.md @@ -16,11 +16,11 @@ One of the advantages of using a __Row Details__ template is that it can be disp ![Telerik {{ site.framework_name }} DataGrid RowDetails 1](images/RadGridView_RowDetails_1.png) ->tipTo easily expand / collapse the __Row Details__ you can use the [Toggle RowDetails Column]({%slug radgridview-columns-column-types-toggle-rowdetails-column%}). +>tip To easily expand / collapse the __Row Details__ you can use the [Toggle RowDetails Column]({%slug radgridview-columns-column-types-toggle-rowdetails-column%}). ->tipThe row and the row details share the same data context, so you are free to bind the elements in your template to any of the properties of the data item. To learn more about the __Row Details template__ read [here]({%slug radgridview-row-details-template%}). +>tip The row and the row details share the same data context, so you are free to bind the elements in your template to any of the properties of the data item. To learn more about the __Row Details template__ read [here]({%slug radgridview-row-details-template%}). ->tipIn order to not scroll the RowDetails when horizontally scrolling the parent RadGridView, you should set __AreRowDetailsFrozen="True"__ for it. +>tip In order to not scroll the RowDetails when horizontally scrolling the parent RadGridView, you should set __AreRowDetailsFrozen="True"__ for it. This chapter will make you familiar with the specifics around the __Row Details__. The following things will get explained: diff --git a/controls/radgridview/row-details/programming.md b/controls/radgridview/row-details/programming.md index e211bd2a11..1e5658a88e 100644 --- a/controls/radgridview/row-details/programming.md +++ b/controls/radgridview/row-details/programming.md @@ -15,7 +15,7 @@ position: 4 __RadGridView__ control exposes several events regarding the __RowDetails__: ->tipMore about the events that the __RadGridView__ exposes, can be found [here]({%slug gridview-events-overview%}). +>tip More about the events that the __RadGridView__ exposes, can be found [here]({%slug gridview-events-overview%}). * __LoadingRowDetails__: The event is raised immediately after the __FrameworkElement__ has been loaded from the __Row Details DataTemplate__. It is raised the __very first time__ the row details are about to be shown. Once this event has been fired, it will never fire again for that row. However, if the row is recycled and then realized, it starts its "life" again, this event will be fired again the first time the details are about to be shown. @@ -96,7 +96,7 @@ __Example 3: Accessing the expanded item__ * __RowDetailsVisiblityChanged__: This event is fired each time the row details are shown or hidden, i.e. by selecting or deselecting the row. Via the __GridViewRowDetailsEventArgs__ you could access the just loaded __DetailsElement__, the respective __GridViewRow__ (Row) as well as the __Visibility__ of the row details. ->tipTo manually change the visibility of a row - set its __DetailsVisibility__ property to either Visibility.Collapsed or Visibility.Visible +>tip To manually change the visibility of a row - set its __DetailsVisibility__ property to either Visibility.Collapsed or Visibility.Visible ## See Also diff --git a/controls/radgridview/row-details/templateselector.md b/controls/radgridview/row-details/templateselector.md index 2be9998eab..1b64be2b03 100644 --- a/controls/radgridview/row-details/templateselector.md +++ b/controls/radgridview/row-details/templateselector.md @@ -168,7 +168,7 @@ __Example 3: Definition of RowDetailsTemplateSelector property of RadGridView__ ``` ->tipYou can download a runnable project of the demonstrated example in [the online SDK repository](https://github.com/telerik/xaml-sdk/tree/master/GridView/RowDetailsTemplateSelector). In addition to make finding and browsing the examples easier, you can take advantage of our [SDK Samples Browser]({%slug sdk-samples-browser%}). +>tip You can download a runnable project of the demonstrated example in [the online SDK repository](https://github.com/telerik/xaml-sdk/tree/master/GridView/RowDetailsTemplateSelector). In addition to make finding and browsing the examples easier, you can take advantage of our [SDK Samples Browser]({%slug sdk-samples-browser%}). ## See Also diff --git a/controls/radgridview/selection/how-to/via-checkbox.md b/controls/radgridview/selection/how-to/via-checkbox.md index 2066c90b65..398e13e5e8 100644 --- a/controls/radgridview/selection/how-to/via-checkbox.md +++ b/controls/radgridview/selection/how-to/via-checkbox.md @@ -70,6 +70,6 @@ Here is the final result. When you select the CheckBox Header, then all rows wil ![Telerik {{ site.framework_name }} DataGrid HowTo SelectionViaCheckbox 020](images/RadGridView_HowTo_SelectionViaCheckbox_020.png) ->tipWhen you want to use selection via checkbox, then:1. Set the __SelectionMode__ property to __Extended__ or __Multiple__. Leaving it to __Single__ you won't be able to select all of the entries in the __RadGridView__.2. Add a __GridViewSelectColumn__. +>tip When you want to use selection via checkbox, then:1. Set the __SelectionMode__ property to __Extended__ or __Multiple__. Leaving it to __Single__ you won't be able to select all of the entries in the __RadGridView__.2. Add a __GridViewSelectColumn__. ->tipIf you need further information for the __GridViewSelectColumn__ and all other provided columns take a look at the [this topic]({%slug radgridview-columns-column-types-select-column%}). +>tip If you need further information for the __GridViewSelectColumn__ and all other provided columns take a look at the [this topic]({%slug radgridview-columns-column-types-select-column%}). diff --git a/controls/radgridview/selection/multiple-selection.md b/controls/radgridview/selection/multiple-selection.md index 51f51c87c3..5a5c294d01 100644 --- a/controls/radgridview/selection/multiple-selection.md +++ b/controls/radgridview/selection/multiple-selection.md @@ -34,7 +34,7 @@ The __Multiple__ value of the __SelectionMode__ enumeration allows the user to a The __Extended__ selection on the other hand, allows users to select multiple records using the common key modifiers - __Shift__ and __Ctrl__. Holding __Shift__ while selecting a row will select the range of rows between the newly-selected row and the previously-selected one. By holding __Ctrl__ upon selection, the selected row will be added to the current selection or removed from it if it has already been selected. The same rules apply to the cells if the [SelectionUnit]({%slug gridview-selection-basics%}) property is set to __Cell__. If no modifiers are pressed when selecting a unit only that unit will be selected. ->tipPressing __Ctrl+A__ will select all items. +>tip Pressing __Ctrl+A__ will select all items. ![Telerik {{ site.framework_name }} DataGrid cell selection](images/RadGridView_MultipleSelection_1.png)![{{ site.framework_name }} RadGridView Multiple Selection](images/gridview_cell_selection.png) diff --git a/controls/radgridview/selection/programmatic-selection.md b/controls/radgridview/selection/programmatic-selection.md index 48c57423cf..d014710a2e 100644 --- a/controls/radgridview/selection/programmatic-selection.md +++ b/controls/radgridview/selection/programmatic-selection.md @@ -38,7 +38,7 @@ __Example 2: Setting the SelectedItem to an item of the ItemsSource__ When choosing this approach, you need to make sure that the data is already loaded. (e.g. you can use the above code in the __DataLoaded__ event of the RadGridView) ->tipYou can also make another control like __ListBox__ or __ComboBox__ to pass the __SelectedItem__ to the __RadGridView__. +>tip You can also make another control like __ListBox__ or __ComboBox__ to pass the __SelectedItem__ to the __RadGridView__. ## CurrentItem @@ -55,7 +55,7 @@ __Example 3: Setting the CurrentItem__ Me.radGridView.CurrentItem = CType(Me.radGridView.ItemsSource, ObservableCollection(Of Employee)).First() ``` ->tipYou can also make another control like __ListBox__ or __ComboBox__ to pass the __CurrentItem__ to the __RadGridView__. +>tip You can also make another control like __ListBox__ or __ComboBox__ to pass the __CurrentItem__ to the __RadGridView__. >Prior to R2 2010 version, the current item was synchronized with the selected item. As a result, the __first row__ of the GridView was __selected initially__. To prevent this, you would simply need to set the __IsSynchronizedWithCurrentItem__ property of RadGridView to __False__. In __R2 2010__ version, the __IsSynchronizedWithCurrentItem__ is null by default - SelectedItem is synchronized with the CurrentItem only if CollectionView is used as ItemsSource diff --git a/controls/radgridview/style-selectors/group-footer-row-styleselector.md b/controls/radgridview/style-selectors/group-footer-row-styleselector.md index d1a6c1166c..11c699352e 100644 --- a/controls/radgridview/style-selectors/group-footer-row-styleselector.md +++ b/controls/radgridview/style-selectors/group-footer-row-styleselector.md @@ -12,7 +12,7 @@ position: 5 The **GroupFooterRowStyleSelector** property of RadGridView can be used to style group footer rows differently based on a specific condition. ->importantBear in mind that the **GroupFooterRowStyle** takes precedence over the **GroupFooterRowStyleSelector** and will overwrite it if both are defined simultaneously. +>important Bear in mind that the **GroupFooterRowStyle** takes precedence over the **GroupFooterRowStyleSelector** and will overwrite it if both are defined simultaneously. To do so, first create a new class that inherits the **StyleSelector** class and override its **SelectStyle** method: diff --git a/controls/radgridview/style-selectors/group-row-style-selector.md b/controls/radgridview/style-selectors/group-row-style-selector.md index 2dc0fd54cc..baf9a7ff00 100644 --- a/controls/radgridview/style-selectors/group-row-style-selector.md +++ b/controls/radgridview/style-selectors/group-row-style-selector.md @@ -12,7 +12,7 @@ position: 3 You can use RadGridView's **GroupRowStyleSelector** property if you need to style group rows differently based on a specific condition. ->importantBear in mind that the [GroupRowStyle]({%slug gridview-styling-group-row%}) takes precedence over the **GroupRowStyleSelector** and will overwrite it if both are defined simultaneously. +>important Bear in mind that the [GroupRowStyle]({%slug gridview-styling-group-row%}) takes precedence over the **GroupRowStyleSelector** and will overwrite it if both are defined simultaneously. To achieve this, first create a new class that inherits from the **StyleSelector** class and override its **SelectStyle** method: diff --git a/controls/radgridview/style-selectors/groupfootercell-styleselector.md b/controls/radgridview/style-selectors/groupfootercell-styleselector.md index 2fea98e702..21f75e2f1d 100644 --- a/controls/radgridview/style-selectors/groupfootercell-styleselector.md +++ b/controls/radgridview/style-selectors/groupfootercell-styleselector.md @@ -12,7 +12,7 @@ position: 6 The **GroupFooterCellStyleSelector** property of RadGridView can be used to style group footer rows differently based on a specific condition. ->importantBear in mind that the **GroupFooterCellStyle** takes precedence over the **GroupFooterCellStyleSelector** and will overwrite it if both are defined simultaneously. +>important Bear in mind that the **GroupFooterCellStyle** takes precedence over the **GroupFooterCellStyleSelector** and will overwrite it if both are defined simultaneously. To do so, first create a new class that inherits the **StyleSelector** class and override its **SelectStyle** method: diff --git a/controls/radgridview/style-selectors/merged-cells-style-selector.md b/controls/radgridview/style-selectors/merged-cells-style-selector.md index 3a176765cb..26db1687f6 100644 --- a/controls/radgridview/style-selectors/merged-cells-style-selector.md +++ b/controls/radgridview/style-selectors/merged-cells-style-selector.md @@ -12,7 +12,7 @@ position: 4 __RadGridView__'s **MergedCellsStyleSelector** can be used to style merged cells differently based on a specific condition. ->importantBear in mind that the **MergedCellsStyle** takes precedence over the **MergedCellsStyleSelector** and will overwrite it if both are defined simultaneously. +>important Bear in mind that the **MergedCellsStyle** takes precedence over the **MergedCellsStyleSelector** and will overwrite it if both are defined simultaneously. To do so, first create a new class that inherits the **StyleSelector** class and override its **SelectStyle** method: diff --git a/controls/radgridview/style-selectors/rowdetails-styleselector.md b/controls/radgridview/style-selectors/rowdetails-styleselector.md index c9074c80e9..7e905b0bb3 100644 --- a/controls/radgridview/style-selectors/rowdetails-styleselector.md +++ b/controls/radgridview/style-selectors/rowdetails-styleselector.md @@ -128,7 +128,7 @@ And here is the final result: ![Telerik {{ site.framework_name }} DataGrid-rowdetails-styleselector](images/gridview-rowdetails-styleselector.png) ->tipAnother approach for achieving the same result is demonstrated in the {% if site.site_name == 'Silverlight' %}[Silverlight Controls Samples](https://demos.telerik.com/silverlight/#GridView/Selectors/StyleSelectors/RowDetailsStyleSelector){% endif %}{% if site.site_name == 'WPF' %}[WPF Controls Samples](https://demos.telerik.com/wpf/) under **StyleSelectors -> Row Details**{% endif %}. +>tip Another approach for achieving the same result is demonstrated in the {% if site.site_name == 'Silverlight' %}[Silverlight Controls Samples](https://demos.telerik.com/silverlight/#GridView/Selectors/StyleSelectors/RowDetailsStyleSelector){% endif %}{% if site.site_name == 'WPF' %}[WPF Controls Samples](https://demos.telerik.com/wpf/) under **StyleSelectors -> Row Details**{% endif %}. ## See Also diff --git a/controls/radgridview/style-selectors/rowstyleselector.md b/controls/radgridview/style-selectors/rowstyleselector.md index 99d4d0e874..e485b1d6d6 100644 --- a/controls/radgridview/style-selectors/rowstyleselector.md +++ b/controls/radgridview/style-selectors/rowstyleselector.md @@ -137,7 +137,7 @@ __Example 4: Set RadGridView's RowStyleSelector__ >Since the virtualization of the control is turned on by default, it is not recommended to work with the visual elements (i.e. GridViewRow) and their properties. You should not set properties of GridViewRow inside SelectStyle method. [Read mode on UI Virtualization]({%slug radgridview-features-ui-virtualization%}). ->tipYou can download a runnable project of the previous example from our online SDK repository [here](https://github.com/telerik/xaml-sdk/), the example is listed as __GridView/RowStyleSelector__. +>tip You can download a runnable project of the previous example from our online SDK repository [here](https://github.com/telerik/xaml-sdk/), the example is listed as __GridView/RowStyleSelector__. ## AlternateRowStyleSelector diff --git a/controls/radgridview/styles-and-templates/modifying-default-styles.md b/controls/radgridview/styles-and-templates/modifying-default-styles.md index eef2957860..d9c16540be 100644 --- a/controls/radgridview/styles-and-templates/modifying-default-styles.md +++ b/controls/radgridview/styles-and-templates/modifying-default-styles.md @@ -56,7 +56,7 @@ The **Create Style Resource** dialog will prompt you for the name of the style a For this example, we will choose to apply this style to all FilteringDropDown controls and place it in our **App.xaml** file. ->tipIf you choose to define the style in the resources of the application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. +>tip If you choose to define the style in the resources of the application, it would be available for the entire application. This allows you to define a style only once and then reuse it where needed. #### __Figure 4: The "Create Style Resource" window__ @@ -68,9 +68,9 @@ After clicking **OK**, the default style of the control will be created in the s ![Telerik {{ site.framework_name }} DataGrid Styles and Templates Styling FilteringControl 4](images/RadGridView_Styles_and_Templates_Styling_FilteringControl_4.png) ->tipPlease bear in mind that the control template may be different in the different themes. This example modifies the **OfficeBlack** theme. +>tip Please bear in mind that the control template may be different in the different themes. This example modifies the **OfficeBlack** theme. ->importantNote that when changing a __Control Template__ you should include all required parts. Even if your code compiles, some of the functionality may be impacted due to the omission of the required parts. The required parts are usually marked with the prefix "__PART___". +>important Note that when changing a __Control Template__ you should include all required parts. Even if your code compiles, some of the functionality may be impacted due to the omission of the required parts. The required parts are usually marked with the prefix "__PART___". ### Modifying the Control Template @@ -100,7 +100,7 @@ If you prefer, you can manually extract the needed style from the respective XAM The process is similar to [manually extracting the Control Template]({%slug styling-apperance-editing-control-templates%}#extracting-control-templates-manually-from-the-theme-xaml-file) of a given control. ->importantNote that when changing a __Control Template__ you should include all required parts. Even if your code compiles, some of the functionality may be impacted due to the omission of the required parts. The required parts are usually marked with the prefix "__PART___". +>important Note that when changing a __Control Template__ you should include all required parts. Even if your code compiles, some of the functionality may be impacted due to the omission of the required parts. The required parts are usually marked with the prefix "__PART___". ## See Also diff --git a/controls/radgridview/styles-and-templates/stylines-and-templates-overview.md b/controls/radgridview/styles-and-templates/stylines-and-templates-overview.md index a5f7828aae..b754768e56 100644 --- a/controls/radgridview/styles-and-templates/stylines-and-templates-overview.md +++ b/controls/radgridview/styles-and-templates/stylines-and-templates-overview.md @@ -12,14 +12,14 @@ position: 0 This section is intended to give you a broad understanding of the possible ways by which you can change the visual appearance of __RadGridView__ and its elements. There is also comprehensive information about their __ControlTemplates__. You will need this information if you want to customize their appearance. ->tipTo learn how to style Telerik UI for {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %} read the common topics about [Setting a Theme (Using Implicit Styles)]({%slug styling-apperance-implicit-styles-overview%}). You can also check the [Editing Control Templates]({%slug styling-apperance-editing-control-templates%}) topic. +>tip To learn how to style Telerik UI for {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %} read the common topics about [Setting a Theme (Using Implicit Styles)]({%slug styling-apperance-implicit-styles-overview%}). You can also check the [Editing Control Templates]({%slug styling-apperance-editing-control-templates%}) topic. You can modify the look of the __RadGridView__ and its elements either by changing some of the resources exposed by the API, or by modifying their __ControlTemplates__. In the control template you are allowed to reorder the template parts and add your own elements. However, when changing the control template you should be careful to include all required parts. Using [Implicit Styles]({%slug styling-apperance-implicit-styles-overview%}) gives you the ability to easily extract and edit the default ControlTemplates of the controls. You can follow [this article]({%slug styling-apperance-editing-control-templates%}) for two different approaches on how to extract the ControlTemplates. ->tipNote that when changing the __ControlTemplate__ you should include all required parts. Even if your code compiles, some of the functionality may be impacted due to the omission of the required parts. The required parts are usually marked with the prefix "__PART___". +>tip Note that when changing the __ControlTemplate__ you should include all required parts. Even if your code compiles, some of the functionality may be impacted due to the omission of the required parts. The required parts are usually marked with the prefix "__PART___". To learn more about styling the __RadGridView__ specific elements, read the following topics. diff --git a/controls/radgridview/styles-and-templates/styling-filterrow.md b/controls/radgridview/styles-and-templates/styling-filterrow.md index a8ccb876f0..a9d43a400c 100644 --- a/controls/radgridview/styles-and-templates/styling-filterrow.md +++ b/controls/radgridview/styles-and-templates/styling-filterrow.md @@ -25,7 +25,7 @@ Here are the four different scenarios that you can get: * Boolean: Nothing * Other: __TextBox__ ->tipWhen the DataType of the column is of __Boolean__ type, you will have **IsTrue** and **IsFalse** filter operators in the drop-down. For that reason, you do not need an editor. +>tip When the DataType of the column is of __Boolean__ type, you will have **IsTrue** and **IsFalse** filter operators in the drop-down. For that reason, you do not need an editor. ## Modifying the StringFilterEditor's Style diff --git a/controls/radgridview/styles-and-templates/styling-group-row.md b/controls/radgridview/styles-and-templates/styling-group-row.md index 7a9f89802e..215123538b 100644 --- a/controls/radgridview/styles-and-templates/styling-group-row.md +++ b/controls/radgridview/styles-and-templates/styling-group-row.md @@ -10,7 +10,7 @@ position: 12 # Styling Group Row ->importantWith R3 2012, Telerik introduced __GroupRenderMode="Flat"__ which uses the **GroupHeaderRow** element as opposed to the **Nested** group render mode that uses the **GridViewGroupRow**. You should target the correct element in order for your styles to be applied. Please look at this [help article]({%slug gridview-grouping-groupingmodes%}) for details. +>important With R3 2012, Telerik introduced __GroupRenderMode="Flat"__ which uses the **GroupHeaderRow** element as opposed to the **Nested** group render mode that uses the **GridViewGroupRow**. You should target the correct element in order for your styles to be applied. Please look at this [help article]({%slug gridview-grouping-groupingmodes%}) for details. ## Targeting the GridViewGroupRow Element diff --git a/controls/radgridview/styles-and-templates/styling-merged-column-headers.md b/controls/radgridview/styles-and-templates/styling-merged-column-headers.md index cc9a11f9ed..bf07a0b7e8 100644 --- a/controls/radgridview/styles-and-templates/styling-merged-column-headers.md +++ b/controls/radgridview/styles-and-templates/styling-merged-column-headers.md @@ -36,7 +36,7 @@ This will result in a red background for the merged header cells. ![Telerik {{ site.framework_name }} DataGrid-styling-column-groups](images/gridview-styling-column-groups.png) ->importantAs of version Q2 2015, the __GridViewColumnGroupRow__ visual element was introduced. You need to also merge its XAML if using a Custom Theme. +>important As of version Q2 2015, the __GridViewColumnGroupRow__ visual element was introduced. You need to also merge its XAML if using a Custom Theme. >If you want to have your [**Row Indicator** visible]({%slug gridview-customizing-rows%}#hiding-the-row-indicator), you will also need to modify the **CommonHeaderIndent** element of the **GridViewHeaderRow**. You can look at the [Styling Header Row article]({%slug gridview-styling-header-row%}) for more information on how to achieve that. diff --git a/controls/radgridview/styles-and-templates/styling-mergedcell.md b/controls/radgridview/styles-and-templates/styling-mergedcell.md index 0bc9f3ebc2..4f43edaa34 100644 --- a/controls/radgridview/styles-and-templates/styling-mergedcell.md +++ b/controls/radgridview/styles-and-templates/styling-mergedcell.md @@ -11,7 +11,7 @@ site_name: WPF # Styling Merged Cells ->tipMerged cells have a template structure similar to [RadGridView cells]({%slug gridview-styling-cell%}). +>tip Merged cells have a template structure similar to [RadGridView cells]({%slug gridview-styling-cell%}). In this article we will discuss the following topics: @@ -73,7 +73,7 @@ __Example 2: Styling merged cells of a specific RadGridView__ ``` ->tipIf you are using [Implicit Themes]({%slug styling-apperance-implicit-styles-overview%}), you should base the style on the one defined for the corresponding theme. +>tip If you are using [Implicit Themes]({%slug styling-apperance-implicit-styles-overview%}), you should base the style on the one defined for the corresponding theme. ## Setting MergedCellsStyleSelector diff --git a/controls/radgridview/template-selectors/cell-template-selector.md b/controls/radgridview/template-selectors/cell-template-selector.md index 07c7972068..9cb2930ae3 100644 --- a/controls/radgridview/template-selectors/cell-template-selector.md +++ b/controls/radgridview/template-selectors/cell-template-selector.md @@ -12,7 +12,7 @@ position: 1 This article will show you how to conditionally apply a different data template to RadGridView cells using the __CellTemplateSelector__ and **CellEditTemplateSelector** properties. ->tipTo learn the basics about __TemplateSelectors__ please check [this article]({%slug gridview-template-selectors-overview%}). +>tip To learn the basics about __TemplateSelectors__ please check [this article]({%slug gridview-template-selectors-overview%}). Assume we have a GridView bound to a collection of clubs. Each club has a property StadiumCapacity. What we want to achieve is to apply one data template if the capacity is greater than 50 000 and another otherwise: diff --git a/controls/radgridview/template-selectors/overview.md b/controls/radgridview/template-selectors/overview.md index b9df3ef6d4..619d0a6dfc 100644 --- a/controls/radgridview/template-selectors/overview.md +++ b/controls/radgridview/template-selectors/overview.md @@ -16,7 +16,7 @@ The __DataTemplateSelector__ provides a way to apply data templates based on cus Typically, you use a template selector when you have more than one data template defined for the same type of objects. For example, use it if your binding source is a list of student objects and you want to apply a particular template to the part-time students. You can do this by creating a class that inherits from __DataTemplateSelector__ and by overriding the __SelectTemplate()__ method. Once your class is defined you can assign an instance of the class to the template selector property of your element. ->tipFor more information, you can check the [DataTemplateSelector Class msdn article](http://msdn.microsoft.com/en-us/library/system.windows.controls.datatemplateselector(v=vs.110).aspx). +>tip For more information, you can check the [DataTemplateSelector Class msdn article](http://msdn.microsoft.com/en-us/library/system.windows.controls.datatemplateselector(v=vs.110).aspx). ## See Also diff --git a/controls/radgridview/troubleshooting/cannot-insert-new-row.md b/controls/radgridview/troubleshooting/cannot-insert-new-row.md index 6572e8dacd..7d4b8b8ec0 100644 --- a/controls/radgridview/troubleshooting/cannot-insert-new-row.md +++ b/controls/radgridview/troubleshooting/cannot-insert-new-row.md @@ -22,7 +22,7 @@ Generally the reason why you cannot add any new item, is because RadGridView doe Another possible reason can be the type of the bound data source collection. If the collection itself does not support inserting and removing items then you will not be able to add any new item. ->tipYou can find more information on different types of collections and the functionality they provide in [this help article](http://msdn.microsoft.com/en-us/library/system.collections(v=vs.110).aspx). +>tip You can find more information on different types of collections and the functionality they provide in [this help article](http://msdn.microsoft.com/en-us/library/system.collections(v=vs.110).aspx). __SOLUTION__ diff --git a/controls/radgridview/troubleshooting/first-row-always-selected.md b/controls/radgridview/troubleshooting/first-row-always-selected.md index 28c27f9066..11d0793d9d 100644 --- a/controls/radgridview/troubleshooting/first-row-always-selected.md +++ b/controls/radgridview/troubleshooting/first-row-always-selected.md @@ -14,7 +14,7 @@ __PROBLEM__ By default, the first row of the RadGridView is selected. This is also causing the [SelectionChanged]({%slug gridview-selection-events%}) event to fire when the control is loaded. ->tipThis behavior does not occur in versions after __Q2 2010__. +>tip This behavior does not occur in versions after __Q2 2010__. __CAUSE__ diff --git a/controls/radgridview/troubleshooting/reevaluation-dataoperations.md b/controls/radgridview/troubleshooting/reevaluation-dataoperations.md index 1a19e194e9..a9a467bd40 100644 --- a/controls/radgridview/troubleshooting/reevaluation-dataoperations.md +++ b/controls/radgridview/troubleshooting/reevaluation-dataoperations.md @@ -32,7 +32,7 @@ There are four possible solutions: >When a __nested property__ is modified and a notification is raised for it as suggested in point 1., then RadGridView will not receive it and the data displayed will not be re-evaluated. In that case the suggested solutuons listed as 2. or 3. should be applied. ->tipYou can also find the blog post on [Fast real-time update](http://blogs.telerik.com/vladimirenchev/posts/10-10-04/fast-real-time-data-update-for-your-silverlight-and-wpf-applications.aspx). +>tip You can also find the blog post on [Fast real-time update](http://blogs.telerik.com/vladimirenchev/posts/10-10-04/fast-real-time-data-update-for-your-silverlight-and-wpf-applications.aspx). ## See Also * [Basic Filtering]({%slug gridview-filtering-basic%}) diff --git a/controls/radimageeditor/how-to/howto-custom-tool.md b/controls/radimageeditor/how-to/howto-custom-tool.md index 56369256bb..7a4b1dbf5c 100644 --- a/controls/radimageeditor/how-to/howto-custom-tool.md +++ b/controls/radimageeditor/how-to/howto-custom-tool.md @@ -72,7 +72,7 @@ This allows you to implement virtually any behavior you want within your tool an - >tipDo not forget to initialize the command in the constructor of the tool. + >tip Do not forget to initialize the command in the constructor of the tool. 1. __Create command context.__
Create context for your custom command. In this case we will take into account the Opacity, Rotation, Scale and Image properties. @@ -101,7 +101,7 @@ This allows you to implement virtually any behavior you want within your tool an 1. __Create UI settings for the tool.__ - >tip__ToolSettingsHeader__ is a content control located in the Telerik.Windows.Controls.ImageEditor assembly. + >tip __ToolSettingsHeader__ is a content control located in the Telerik.Windows.Controls.ImageEditor assembly. __Example 4: Create Custom Tool Settings__ @@ -193,7 +193,7 @@ This allows you to implement virtually any behavior you want within your tool an >The __IsDirty__ property is used in the commiting logic of tools. Make sure to set it to true when a change in the settings has occured and to false when the settings are reset. - >tipThe complete code is available in the XAML SDK repository: [Custom Watermark Tool](https://github.com/telerik/xaml-sdk/tree/master/ImageEditor/CustomWatermarkTool). + >tip The complete code is available in the XAML SDK repository: [Custom Watermark Tool](https://github.com/telerik/xaml-sdk/tree/master/ImageEditor/CustomWatermarkTool). ## See Also diff --git a/controls/radimageeditor/tools/howto-use-crop.md b/controls/radimageeditor/tools/howto-use-crop.md index 8aa5583dab..cddac24e51 100644 --- a/controls/radimageeditor/tools/howto-use-crop.md +++ b/controls/radimageeditor/tools/howto-use-crop.md @@ -129,7 +129,7 @@ __Example 8: Set fixed aspect ratio in code-behind__ Me.ImageEditorUI.ImageEditor.ExecuteTool(cropTool) ``` ->tipYou can crop an image with fixed ratio between the width and height without setting the FixedRatio property. Just press and hold the __Shift__ key while dragging the crop adorner. +>tip You can crop an image with fixed ratio between the width and height without setting the FixedRatio property. Just press and hold the __Shift__ key while dragging the crop adorner. ## See Also diff --git a/controls/radlistbox/features/autocomplete.md b/controls/radlistbox/features/autocomplete.md index 9547ac57ca..4dc795b634 100644 --- a/controls/radlistbox/features/autocomplete.md +++ b/controls/radlistbox/features/autocomplete.md @@ -55,9 +55,9 @@ Typing, for example "L" will select the corresponding item: >Note that if you have set __DisplayMemberPath__ to a certain property and you want to use the same property for __Autocomplete__, you don't need to set __TextPath__/__TextBinding__. ->tipAutocomplete always starts from the beginning, regardless of the selection. +>tip Autocomplete always starts from the beginning, regardless of the selection. ->tipPressing __Esc__ clears the current text for autocomplete. +>tip Pressing __Esc__ clears the current text for autocomplete. ## Disable Autocomplete diff --git a/controls/radlistbox/populating-with-data/binding-support-overview.md b/controls/radlistbox/populating-with-data/binding-support-overview.md index 85e9a9373a..bc266f10fa 100644 --- a/controls/radlistbox/populating-with-data/binding-support-overview.md +++ b/controls/radlistbox/populating-with-data/binding-support-overview.md @@ -20,7 +20,7 @@ Binding to __RadListBox__ involves the following property: To bind the __RadListBox__ to a collection of business objects, you should use its __ItemsSource__ property. If you want the changes to the collection to be automatically reflected to the __RadListBoxItems__, the collection should implement the __INotifyCollectionChanged__ interface. There is a build-in collection in {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %}, which implements the __INotifyCollectionChanged__ interface and you could use it without making any effort - this is the generic __ObservableCollection__. However, to get a full benefit from the change notification support, your custom business objects should implement the __INotifyPropertyChanged__ interface. ->tipConsider using __ObservableCollection__ or one of the other existing collection classes like __List__, __Collection__, instead of implementing your own collection. If the scenario requires a custom collection to be implemented, use the __IList__ interface, which provides individual access by index to its items and the best performance. +>tip Consider using __ObservableCollection__ or one of the other existing collection classes like __List__, __Collection__, instead of implementing your own collection. If the scenario requires a custom collection to be implemented, use the __IList__ interface, which provides individual access by index to its items and the best performance. __Exmaple 1: Create an objects class__ @@ -119,4 +119,4 @@ __Example 5: Set DisplayMemberPath to 'Name' to show the names of the countries #### __Figure 1: Result of Examples 4 and 5__ ![Rad List Box ItemsSource DisplayMemberPath 01](images/RadListBox_PopulatingWithData_DataBindingSupportOverview_01.png) ->tipIf neither the __DisplayMemberPath__ nor the __ItemTemplate__ are set, the content of the item would be set to the value returned by the __ToString()__ method of the business object. \ No newline at end of file +>tip If neither the __DisplayMemberPath__ nor the __ItemTemplate__ are set, the content of the item would be set to the value returned by the __ToString()__ method of the business object. \ No newline at end of file diff --git a/controls/radlistbox/populating-with-data/binding-to-object.md b/controls/radlistbox/populating-with-data/binding-to-object.md index 23a0dd2c67..edbf5d253f 100644 --- a/controls/radlistbox/populating-with-data/binding-to-object.md +++ b/controls/radlistbox/populating-with-data/binding-to-object.md @@ -18,7 +18,7 @@ The following tutorial will guide you how to bind a __RadListBox__ to a collecti * [Using DisplayMemberPath property](#using-displaymemberpath) ->tipBefore reading this tutorial you should get familiar with the [Data Binding]({%slug radlistbox-populating-with-data-binding-support-overview%}) support of the RadListBox control. +>tip Before reading this tutorial you should get familiar with the [Data Binding]({%slug radlistbox-populating-with-data-binding-support-overview%}) support of the RadListBox control. In order to bind a __RadListBox__ to a collection of business objects, you should perform the following instructions: diff --git a/controls/radmap/features/providers/uriimageprovider.md b/controls/radmap/features/providers/uriimageprovider.md index d711fefe2c..b27775581a 100644 --- a/controls/radmap/features/providers/uriimageprovider.md +++ b/controls/radmap/features/providers/uriimageprovider.md @@ -53,4 +53,4 @@ the value of the __BaseAddress__ property. * __ZoomNumericFormat__: Gets or sets numeric format string will be used to replace {zoom} placeholder. For example "D2" will replace {zoom} placeholder with 2 digits integer (01, 02, ..., 19). The default value is null and it produces simple integer without paddings (1, 2, ... 9, 10, ... 19). ->tipNote that the __UriImageProvider__ cannot be used as a master provider in a multi-provider scenario and always should be restricted within geographic region (i.e. you need to set the UriImageProvider.GeoBounds property). +>tip Note that the __UriImageProvider__ cannot be used as a master provider in a multi-provider scenario and always should be restricted within geographic region (i.e. you need to set the UriImageProvider.GeoBounds property). diff --git a/controls/radmap/features/visualization-layer/heatures-clustering.md b/controls/radmap/features/visualization-layer/heatures-clustering.md index f56de4536c..39438086fa 100644 --- a/controls/radmap/features/visualization-layer/heatures-clustering.md +++ b/controls/radmap/features/visualization-layer/heatures-clustering.md @@ -22,7 +22,7 @@ The __VisualizationLayer__ exposes the following properties which are related to * __ClusteringEnabledThreshold__: A property of type __int__ that gets or sets clustering enabled threshold. This value sets the max zoom level for clustering. If current zoom level of the control is greater than this value then clustering will be disabled. ->tipYou should set the __AutoCalculateClusteringThreshold__ to __False__ to allow the RadMap to respect the __ClusteringEnabledThreshold__. The default value of this property is __True__. This means that you need to explicitly set it to false in all cases when you need to predefine the clustering threshold. +>tip You should set the __AutoCalculateClusteringThreshold__ to __False__ to allow the RadMap to respect the __ClusteringEnabledThreshold__. The default value of this property is __True__. This means that you need to explicitly set it to false in all cases when you need to predefine the clustering threshold. * __ClusteringEnabledThresholdMinItems__: A property of type __int__ that gets or sets the minimum number of items in the cluster for auto calculated clustering threshold. The clustering threshold will be set if number of the items in every cluster is less than this value. diff --git a/controls/radmenu/features/checkable-items.md b/controls/radmenu/features/checkable-items.md index f34ef65fe7..8ce7fcebb4 100644 --- a/controls/radmenu/features/checkable-items.md +++ b/controls/radmenu/features/checkable-items.md @@ -12,9 +12,9 @@ position: 8 In order to enhance the functionality of the __RadMenu__ control, the __RadMenuItem__ can behave like a checkable item. This means that it can be checked and unchecked like a simple __CheckBox__. In order to toggle this behavior you have to set the __IsCheckable__ property of the __RadMenuItem__ to either __True__ or __False__. The default value is __False__. ->tipTo learn how to group the checkable items into radio groups read [here]({%slug radmenu-how-to-group-checkable-menu-items-into-radio-group%}). +>tip To learn how to group the checkable items into radio groups read [here]({%slug radmenu-how-to-group-checkable-menu-items-into-radio-group%}). ->tipUpon checking and unchecking the respective events are raised - __Checked__ and __Unchecked__. You can subscribe to them in order to implement your custom logic against the respective action. To learn more about them read here. +>tip Upon checking and unchecking the respective events are raised - __Checked__ and __Unchecked__. You can subscribe to them in order to implement your custom logic against the respective action. To learn more about them read here. Here is an example of a definition of a checkable __RadMenuItem__: @@ -26,7 +26,7 @@ __Example 1: Define a checkable menu item__ Upon clicking on the item it will get checked and the tick will appear as an icon for the item. ->tipNote that after clicking on the item the menu will collapse. In order to keep the menu open you can set the __StaysOpenOnClick__ property of the __RadMenuItem__ to __True__. This will keep the menu open when this item is clicked. +>tip Note that after clicking on the item the menu will collapse. In order to keep the menu open you can set the __StaysOpenOnClick__ property of the __RadMenuItem__ to __True__. This will keep the menu open when this item is clicked. ![Checkable Menu Item](images/RadMenu_Features_Checkable_Items_01.png) diff --git a/controls/radmenu/features/click-modes.md b/controls/radmenu/features/click-modes.md index 9c3293d8bb..91c1bf5061 100644 --- a/controls/radmenu/features/click-modes.md +++ b/controls/radmenu/features/click-modes.md @@ -23,7 +23,7 @@ If you set this property to __True__, the menu won't get closed upon a click on ![{{ site.framework_name }} RadMenu Stays Open On Click](images/RadMenu_Click_Modes_01.png) ->tipYou might find this functionality very useful, when having checkable menu items in your __RadMenu__. It allows you to keep the menu open, when a menu item gets checked. To learn more about this type of items read [here]({%slug radmenu-features-checkable-items%}). +>tip You might find this functionality very useful, when having checkable menu items in your __RadMenu__. It allows you to keep the menu open, when a menu item gets checked. To learn more about this type of items read [here]({%slug radmenu-features-checkable-items%}). ## See Also diff --git a/controls/radmenu/features/commands.md b/controls/radmenu/features/commands.md index e82fb825e0..2ec46d9211 100644 --- a/controls/radmenu/features/commands.md +++ b/controls/radmenu/features/commands.md @@ -18,7 +18,7 @@ The __RadMenuItem__ control provides you with a standard __ICommandSource__ impl * __CommandTarget__ - the object that the command is being executed on. ->tipAs the __RadMenuItem__ implements the __ICommandSource__, you can use it with any command that implements the __ICommand__ interface, for example the __DelegateCommands__ in Prism. +>tip As the __RadMenuItem__ implements the __ICommandSource__, you can use it with any command that implements the __ICommand__ interface, for example the __DelegateCommands__ in Prism. > By default the command of a RadMenuItem will not be executed for RadMenuItems which have child RadMenuItems. If you wish to change this behavior, you can set the __NotifyOnHeaderClick__ property of the __RadMenu__ to __True__. This way, even if a RadMenuItem has child items, its corresponding command will be invoked on click. diff --git a/controls/radmenu/features/icons.md b/controls/radmenu/features/icons.md index 88ceb17ce4..09345960d9 100644 --- a/controls/radmenu/features/icons.md +++ b/controls/radmenu/features/icons.md @@ -14,7 +14,7 @@ The `RadMenu` allows you to display an icon for each of the menu items. This can ## Setting the Icon of a Static Item ->tipTo learn more about this way of populating the RadMenu with static data take a look at the [Using Static Items]({%slug radmenu-populating-with-data-using-static-items%}) topic. +>tip To learn more about this way of populating the RadMenu with static data take a look at the [Using Static Items]({%slug radmenu-populating-with-data-using-static-items%}) topic. When using static items you can directly access the Icon property of each item. Respectively you can set it directly: @@ -34,7 +34,7 @@ __RadMenuItems with their Icon property set__ ## Setting the Icon of a Dynamic Item ->tipTo learn more about this way of populating the RadMenu with dynamic data take a look at the [Binding to Dynamic Data]({%slug radmenu-populating-with-data-binding-to-dynamic-data%}) topic. +>tip To learn more about this way of populating the RadMenu with dynamic data take a look at the [Binding to Dynamic Data]({%slug radmenu-populating-with-data-binding-to-dynamic-data%}) topic. When using dynamic items, you have to bind the Icon property to a property of the data item. The specific here is that your data item needs to either expose a property of type Image, so the Icon property can be bound properly or you need to define the IconTemplate property of the menu items if you wish to bind it to a `string` or `Uri`, for example. diff --git a/controls/radmenu/how-to/group-checkable-menu-items-into-radio-group.md b/controls/radmenu/how-to/group-checkable-menu-items-into-radio-group.md index 28091ecb94..cd86bd1f6f 100644 --- a/controls/radmenu/how-to/group-checkable-menu-items-into-radio-group.md +++ b/controls/radmenu/how-to/group-checkable-menu-items-into-radio-group.md @@ -186,9 +186,9 @@ Now as the sibling items from the same group are available, the only things that ## Using this Logic with Dynamic Data ->tipBefore you continue, please, Take a look at the topic about [Binding to Dynamic Data]({%slug radmenu-populating-with-data-binding-to-dynamic-data%}). +>tip Before you continue, please, Take a look at the topic about [Binding to Dynamic Data]({%slug radmenu-populating-with-data-binding-to-dynamic-data%}). ->tipAn entirely business object oriented approach about handling radio groups within dynamic data can be found in the [online demo](https://demos.telerik.com/silverlight/#Menu/CheckableMenuItems). +>tip An entirely business object oriented approach about handling radio groups within dynamic data can be found in the [online demo](https://demos.telerik.com/silverlight/#Menu/CheckableMenuItems). When having __RadMenu__ with dynamic data in it, the logic remains the same, but you have to modify the data items a bit, so they can provide the needed information. You need your business object to expose several properties. diff --git a/controls/radmenu/populating-with-data/data-binding-support-overview.md b/controls/radmenu/populating-with-data/data-binding-support-overview.md index e547331242..ec3d47e833 100644 --- a/controls/radmenu/populating-with-data/data-binding-support-overview.md +++ b/controls/radmenu/populating-with-data/data-binding-support-overview.md @@ -30,7 +30,7 @@ You can bind __RadMenu__ to the following types of data sources: To bind the __RadMenu__ to a collection of business objects, you should use its __ItemsSource__ property. If you want the changes to the collection to be automatically reflected to the __RadMenuItems__, the collection should implement the __INotifyCollectionChanged__ interface. There is a build-in collection in {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %}, which implements the __INotifyCollectionChanged__ interface and you could use it without making any effort - this is the generic __ObservableCollection__. However, to get a full benefit from the change notification support, your custom business objects should implement the __INotifyPropertyChanged__ interface. ->tipConsider using __ObservableCollection\__ or one of the other existing collection classes like __List__, __Collection__, instead of implementing your own collection. If the scenario requires a custom collection to be implemented, use the __IList__ interface, which provides individual access by index to its items and the best performance. +>tip Consider using __ObservableCollection\__ or one of the other existing collection classes like __List__, __Collection__, instead of implementing your own collection. If the scenario requires a custom collection to be implemented, use the __IList__ interface, which provides individual access by index to its items and the best performance. ## Data Templates @@ -38,7 +38,7 @@ The __ItemsSource__ property allows the __RadMenu__ to be bound to any collectio Besides the __RadMenu's ItemTemplate__ property, you could use the __DisplayMemberPath__ property for controlling the appearance of the created items. ->tipIf neither the __DisplayMemberPath__ nor the __ItemTemplate__ are set, the content of the item would be set to the value returned by the __ToString()__ method of the business object. +>tip If neither the __DisplayMemberPath__ nor the __ItemTemplate__ are set, the content of the item would be set to the value returned by the __ToString()__ method of the business object. ## See Also diff --git a/controls/radmenu/populating-with-data/template-and-style-selectors.md b/controls/radmenu/populating-with-data/template-and-style-selectors.md index d8df3ddda7..f64efd9155 100644 --- a/controls/radmenu/populating-with-data/template-and-style-selectors.md +++ b/controls/radmenu/populating-with-data/template-and-style-selectors.md @@ -26,7 +26,7 @@ And a list of the selectors provided by the __RadMenuItem__ control: * __ItemTemplateSelector__ - used to select the __DataTemplate__ that is set to the __HeaderTemplate__ property of the child __RadMenuItems__. ->tipThese properties of the __RadMenuItem__ should be set through the __ItemContainerStyle__ of the parent item. If you set the __ItemContainerStyle__ property of the __RadMenu__ only, it will get inherited in the hierarchy, unless it is not explicitly set somewhere. +>tip These properties of the __RadMenuItem__ should be set through the __ItemContainerStyle__ of the parent item. If you set the __ItemContainerStyle__ property of the __RadMenu__ only, it will get inherited in the hierarchy, unless it is not explicitly set somewhere. The __HierarchicalDataTemplate__ used with the __RadMenu__ also exposes __ItemContainerStyleSelector__ and __ItemTemplateSelector__ properties. diff --git a/controls/radmenu/styles-and-templates/visual-states.md b/controls/radmenu/styles-and-templates/visual-states.md index bcf9754a1a..b260b8a195 100644 --- a/controls/radmenu/styles-and-templates/visual-states.md +++ b/controls/radmenu/styles-and-templates/visual-states.md @@ -54,7 +54,7 @@ The __RadMenuItem__ exposes several states, grouped as follows: * __Unfocused__ - the state of the control, when it isn't focused. ->tipOnly one state of a group can be active. For example, if the control goes into the Checked state, it cannot be in the HideIcon state too. By default the Checked state should display a mark before the item, so it should hide the icon no matter if it is null or not. If the item is not checked and the icon is not defined, the HideIcon state will get activated and the empty icon will get hidden. +>tip Only one state of a group can be active. For example, if the control goes into the Checked state, it cannot be in the HideIcon state too. By default the Checked state should display a mark before the item, so it should hide the icon no matter if it is null or not. If the item is not checked and the icon is not defined, the HideIcon state will get activated and the empty icon will get hidden. The several templates of the __RadMenuItem__ don't handle all of the states, but only those, which they need. When generated through Expression Blend, the logic placed in these templates also gets generated. In the following table you can see which states the specific template makes use of. diff --git a/controls/radnumericupdown/getting-started.md b/controls/radnumericupdown/getting-started.md index 64b0db72a7..aab89348a8 100644 --- a/controls/radnumericupdown/getting-started.md +++ b/controls/radnumericupdown/getting-started.md @@ -57,7 +57,7 @@ If you run the application you will see and empty RadNumericUpDown as demonstrat ![Empty RadNumericUpDown](images/numericupdown-empty.jpg) ->importantThe default **Value** of the __RadNumericUpDown__ control is equal to __null__. +>important The default **Value** of the __RadNumericUpDown__ control is equal to __null__. ## Binding Value diff --git a/controls/radoutlookbar/localization.md b/controls/radoutlookbar/localization.md index e9583d8e22..ba2da57a45 100644 --- a/controls/radoutlookbar/localization.md +++ b/controls/radoutlookbar/localization.md @@ -10,7 +10,7 @@ position: 3 # Localization ->tipTo learn more about the ways to localize the controls from the suite please read the common topic on [Localization]({%slug common-localization%}). +>tip To learn more about the ways to localize the controls from the suite please read the common topic on [Localization]({%slug common-localization%}). __RadOutlookBar__ provides strings for localizing various of its elements. In order to be able to distinguish these resources, an unique identifier, called resource key, is assigned to each string that can be localized. diff --git a/controls/radpdfviewer/getting-started.md b/controls/radpdfviewer/getting-started.md index c8dcd1b845..b049e02ad5 100644 --- a/controls/radpdfviewer/getting-started.md +++ b/controls/radpdfviewer/getting-started.md @@ -90,7 +90,7 @@ __Example 3: Add a RadToolBar to RadPdfViewer__ ``` ->tipYou can download a complete runnable example that shows the default RadPdfViewer with RadToolBar configuration from the [Telerik® SDK repository](https://github.com/telerik/xaml-sdk/tree/master/PdfViewer/FirstLook). +>tip You can download a complete runnable example that shows the default RadPdfViewer with RadToolBar configuration from the [Telerik® SDK repository](https://github.com/telerik/xaml-sdk/tree/master/PdfViewer/FirstLook). You can then add buttons, combo boxes, etc., bound to the respective command descriptors of the viewer, as __Example 4__ shows. @@ -106,7 +106,7 @@ __Example 4: Wire a CommandDescriptor to a RadButton__ ``` ->tipFor the whole configuration of a RadToolBar with all commands of the viewer, you can refer to the [Wiring UI]({%slug radpdfviewer-wiring-ui%}) article. More information about the command descriptors is available [here]({%slug radpdfviewer-command-descriptors%}). +>tip For the whole configuration of a RadToolBar with all commands of the viewer, you can refer to the [Wiring UI]({%slug radpdfviewer-wiring-ui%}) article. More information about the command descriptors is available [here]({%slug radpdfviewer-command-descriptors%}). ## diff --git a/controls/radpdfviewer/localization.md b/controls/radpdfviewer/localization.md index b34d5c14c7..54d4f64e1d 100644 --- a/controls/radpdfviewer/localization.md +++ b/controls/radpdfviewer/localization.md @@ -50,7 +50,7 @@ RadPdfViewer has several localization strings so in order to be able to distingu The three files should keep the same resource keys, whereas the values must be the translated ones. ->tipIt is easiest to copy the default __RadPdfViewerResources.resx__ file and rename it. Afterwards, go through all string and change only the Values for the strings that will be used in your application. +>tip It is easiest to copy the default __RadPdfViewerResources.resx__ file and rename it. Afterwards, go through all string and change only the Values for the strings that will be used in your application. The last step is to instantiate the __LocalizationManager__ class and set its __ResourceManager__ to the resources that have been just created. diff --git a/controls/radpdfviewer/ui/document-presenters.md b/controls/radpdfviewer/ui/document-presenters.md index 2e313b105e..a2a8807746 100644 --- a/controls/radpdfviewer/ui/document-presenters.md +++ b/controls/radpdfviewer/ui/document-presenters.md @@ -39,7 +39,7 @@ Both of those presenters inherit the abstract __Telerik.Windows.Documents.UI.Fix >You can access the document presenter in __RadPdfViewer__ by accessing the __FixedDocumentPresenter__ property. ->tipFixedDocumentPresenterBase exposes the **VisiblePagesCacheOffset property**, which you can use to control the amount of pages that are cached before and after the visible ones. The default value of VisiblePagesCacheOffset is 1. +>tip FixedDocumentPresenterBase exposes the **VisiblePagesCacheOffset property**, which you can use to control the amount of pages that are cached before and after the visible ones. The default value of VisiblePagesCacheOffset is 1. ## Using FixedDocumentPagesPresenter diff --git a/controls/radpdfviewer/ui/find-dialog.md b/controls/radpdfviewer/ui/find-dialog.md index 2b515c5bc7..3972b8e9a6 100644 --- a/controls/radpdfviewer/ui/find-dialog.md +++ b/controls/radpdfviewer/ui/find-dialog.md @@ -14,7 +14,7 @@ position: 4 __RadPdfViewer__ allows flexible searching in a loaded PDF document. The following article describes the available search options, as well as how to use and customize the find dialog. ->importantOther than the default needed [assemblies]({%slug radpdfviewer-getting-started%}), in order to take advantage of the Find dialog functionality in __RadPdfViewer__ you need to add to your project a reference to __Telerik.Windows.Controls.Navigation.dll__. +>important Other than the default needed [assemblies]({%slug radpdfviewer-getting-started%}), in order to take advantage of the Find dialog functionality in __RadPdfViewer__ you need to add to your project a reference to __Telerik.Windows.Controls.Navigation.dll__. >note Find Programmatically is described in detail in the [Find]({%slug radpdfviewer-find%}) article. diff --git a/controls/radpdfviewer/ui/switching-icons-at-runtime.md b/controls/radpdfviewer/ui/switching-icons-at-runtime.md index dd3bae4782..5abdd61f76 100644 --- a/controls/radpdfviewer/ui/switching-icons-at-runtime.md +++ b/controls/radpdfviewer/ui/switching-icons-at-runtime.md @@ -28,7 +28,7 @@ __Example 1: Creating IconSources__ ``` ->tipTo browse all icons you can download the source code of the controls from your Telerik account. The images are located at {%if site.site_name == 'WPF' %}\Telerik\_UI\_for\_WPF\_Source\_[Version]\Controls\PdfViewer\FixedDocumentViewers\Images{%endif%}{%if site.site_name == 'Silverlight' %}\Telerik\_UI\_for\_Silverlight\_Source\_[Version]Controls\PdfViewer\FixedDocumentViewers\Images{%endif%}. +>tip To browse all icons you can download the source code of the controls from your Telerik account. The images are located at {%if site.site_name == 'WPF' %}\Telerik\_UI\_for\_WPF\_Source\_[Version]\Controls\PdfViewer\FixedDocumentViewers\Images{%endif%}{%if site.site_name == 'Silverlight' %}\Telerik\_UI\_for\_Silverlight\_Source\_[Version]Controls\PdfViewer\FixedDocumentViewers\Images{%endif%}. ## See Also diff --git a/controls/radpivotgrid/events/overview.md b/controls/radpivotgrid/events/overview.md index ed37eb5a8b..9e534ad12e 100644 --- a/controls/radpivotgrid/events/overview.md +++ b/controls/radpivotgrid/events/overview.md @@ -50,7 +50,7 @@ For example you can use the event in order to replace a __DoubleGroupDescription * __StatusChanged__ - raised whenever the status of the DataProvider is changed. It can be used in order to execute custom logic whenever the DataProvider is updated. ->importantThe __StatusChanged__ event is raised on multiple threads, so it is required to use Dispatcher when executing a custom logic inside of the event handler. +>important The __StatusChanged__ event is raised on multiple threads, so it is required to use Dispatcher when executing a custom logic inside of the event handler. You can find an example below that demonstrates how to get the current status of the DataProvider: @@ -157,7 +157,7 @@ Figure 1: Custom folders in the FieldTree. The event can be used in order to add and/or remove nodes from the tree. ->tipFor more details on how to add/remove nodes from the FieldTree you can check the CustomizeFieldTree example from our [online SDK repository](https://github.com/telerik/xaml-sdk/tree/master/PivotGrid/CustomizeFieldTree). +>tip For more details on how to add/remove nodes from the FieldTree you can check the CustomizeFieldTree example from our [online SDK repository](https://github.com/telerik/xaml-sdk/tree/master/PivotGrid/CustomizeFieldTree). ## See Also diff --git a/controls/radpivotgrid/features/export.md b/controls/radpivotgrid/features/export.md index fe557b3787..c381a216a0 100644 --- a/controls/radpivotgrid/features/export.md +++ b/controls/radpivotgrid/features/export.md @@ -368,7 +368,7 @@ __Example 1: Generating the exported workbook__ No matter which of these three formats you have chosen, you will have to create a new __RadDocument__, which will hold the content, that will be exported. After that, you have to set this __RadDocument__ instance to the Document property of __RadRichTextBox__. This __RadRichTextBox__ must be visualized in order to be able to export its data. To generate __RadDocument__ you can use the code below: ->tipYou can put __RadRichTextBox__ as a content of a __RadWindow__ and use the window as PrintPreview dialog. You can check a full implementation of this solution in our {% if site.site_name == 'Silverlight' %}[Export](https://demos.telerik.com/silverlight/#PivotGrid/Export){% endif %}{% if site.site_name == 'WPF' %}[Export](https://demos.telerik.com/wpf/){% endif %} demo. If you do not want to show PrintPreview dialog, you can set the visibility of the window to collapsed. +>tip You can put __RadRichTextBox__ as a content of a __RadWindow__ and use the window as PrintPreview dialog. You can check a full implementation of this solution in our {% if site.site_name == 'Silverlight' %}[Export](https://demos.telerik.com/silverlight/#PivotGrid/Export){% endif %}{% if site.site_name == 'WPF' %}[Export](https://demos.telerik.com/wpf/){% endif %} demo. If you do not want to show PrintPreview dialog, you can set the visibility of the window to collapsed. __Example 2: Generating the exported document__ diff --git a/controls/radpivotgrid/features/localdatasourceprovider/data-annotations.md b/controls/radpivotgrid/features/localdatasourceprovider/data-annotations.md index c2937fb4f1..0b07277057 100644 --- a/controls/radpivotgrid/features/localdatasourceprovider/data-annotations.md +++ b/controls/radpivotgrid/features/localdatasourceprovider/data-annotations.md @@ -52,7 +52,7 @@ But what if you want to hide the "Advertisement" property or show different name ## Data Annotations with RadPivotGrid ->importantIf you want to use Data Annotations in your application, you have to add a reference to System.ComponentModel.DataAnnotations assembly. +>important If you want to use Data Annotations in your application, you have to add a reference to System.ComponentModel.DataAnnotations assembly. With Data Annotations you can apply attributes to the members of the class that specify how the data is displayed. __RadPivotGrid__ supports {% if site.site_name == 'Silverlight' %}two{% endif %}{% if site.site_name == 'WPF' %}three{% endif %} different Data Annotations: diff --git a/controls/radpivotgrid/features/localdatasourceprovider/filtering.md b/controls/radpivotgrid/features/localdatasourceprovider/filtering.md index 66e900009d..de4b282a40 100644 --- a/controls/radpivotgrid/features/localdatasourceprovider/filtering.md +++ b/controls/radpivotgrid/features/localdatasourceprovider/filtering.md @@ -55,7 +55,7 @@ The __LabelFilter__ is used for filtering the data based on the Headers (row or * __is not between__ - showing only groups which header is NOT between the two parameters we pass. ->importantAll conditions are case sensitive and are using string comparison between the headers of the groups and the passed parameters. +>important All conditions are case sensitive and are using string comparison between the headers of the groups and the passed parameters. So if we apply a __LabelFilter__ of __RadPivotGrid__ from GettingStarted article with condition *begins with* and parameter *"P"* we will receive the following result: @@ -209,7 +209,7 @@ __Value Filter__ is applied on __RowGroupDescriptions__/__ColumnGroupDescription * __is not between__ - showing only groups which header is NOT between the two parameters we pass. ->important__Value Filter__ is filtering the groups by number comparison between the *GrandTotals* of the groups and the parameters we pass, while __Label Filter__ is a string filter. +>important __Value Filter__ is filtering the groups by number comparison between the *GrandTotals* of the groups and the parameters we pass, while __Label Filter__ is a string filter. So if we apply a __Value Filter__ on the *Name* RowGroupDescription from the __GettingStarted__ article, set condition *"is greater than"* and pass as parameter value 10 we will notice that one of the items is missing because its *GrandTotal* is less than 10. diff --git a/controls/radpivotgrid/features/localdatasourceprovider/local-calc-fields.md b/controls/radpivotgrid/features/localdatasourceprovider/local-calc-fields.md index 1abcfd5521..079abcb0a9 100644 --- a/controls/radpivotgrid/features/localdatasourceprovider/local-calc-fields.md +++ b/controls/radpivotgrid/features/localdatasourceprovider/local-calc-fields.md @@ -112,7 +112,7 @@ Now it is time to add a new instance of this class to the CalculatedFields colle dataProvider.CalculatedFields.Add(calculatedField) ``` ->importantIf you add caculated fields in code behind, you have to set the ItemsSource of LocalDataSourceProvider after you have added all calculated fields or to wrap the code between *BeginInit() - EndInit()* methods (or inside *using DeferRefresh() { ... } section* ). +>important If you add caculated fields in code behind, you have to set the ItemsSource of LocalDataSourceProvider after you have added all calculated fields or to wrap the code between *BeginInit() - EndInit()* methods (or inside *using DeferRefresh() { ... } section* ). This way the Commission field will be visible in a special folder inside __RadPivotFieldList__ called Calculated Fields. diff --git a/controls/radpivotgrid/features/localdatasourceprovider/sorting.md b/controls/radpivotgrid/features/localdatasourceprovider/sorting.md index f1e04dd9e4..e092dde16b 100644 --- a/controls/radpivotgrid/features/localdatasourceprovider/sorting.md +++ b/controls/radpivotgrid/features/localdatasourceprovider/sorting.md @@ -30,7 +30,7 @@ The columns are reordered based on their names (check the green rectangle on the ![Rad Pivot Grid Features Sorting 03](images/RadPivotGrid_Features_Sorting_03.png) ->importantThe sorting is set on the __ColumnGroupDescriptions__ or __RowGroupDescriptions__. You cannot set sorting on the __AggregateDescriptions__, but you can sort the columns or rows based on the aggregated values. +>important The sorting is set on the __ColumnGroupDescriptions__ or __RowGroupDescriptions__. You cannot set sorting on the __AggregateDescriptions__, but you can sort the columns or rows based on the aggregated values. ## Sort the data diff --git a/controls/radpivotgrid/features/olap-providers/filtering-olap.md b/controls/radpivotgrid/features/olap-providers/filtering-olap.md index d232764a37..4e6d9562ab 100644 --- a/controls/radpivotgrid/features/olap-providers/filtering-olap.md +++ b/controls/radpivotgrid/features/olap-providers/filtering-olap.md @@ -298,7 +298,7 @@ If you use __AdomdDataProvider:__ groupDescription.Levels.Add(levelGroupDescription2) ``` ->tipThe value of "Than" property is the unique name of the member (defined in OLAP Cube). As you are unable to use & in XAML, you have to use & which will be parsed to &. You have to define *sys* namespace: __xmlns:sys="clr-namespace:System;assembly=mscorlib"__. +>tip The value of "Than" property is the unique name of the member (defined in OLAP Cube). As you are unable to use & in XAML, you have to use & which will be parsed to &. You have to define *sys* namespace: __xmlns:sys="clr-namespace:System;assembly=mscorlib"__. ## Value Filter @@ -320,7 +320,7 @@ __Value Filter__ is applied on __RowGroupDescriptions__/__ColumnGroupDescription * __is not between__ - show only members for which the selected measure is NOT between the two passed parameters. ->important__Value Filter__ is filtering the groups by number comparison between the *GrandTotals* of the groups and the parameters we pass, while __Label Filter__ is a string filter. +>important __Value Filter__ is filtering the groups by number comparison between the *GrandTotals* of the groups and the parameters we pass, while __Label Filter__ is a string filter. So if we apply a __Value Filter__ on the *Category* ColumnGroupDescription, set condition *"is greater than"* for the AggregateDescription Reseller Order Quantity and pass as parameter value 50000 we will notice that two of the groups are missing because their *GrandTotal* is less than 50 000. diff --git a/controls/radpivotgrid/features/olap-providers/sorting-olap.md b/controls/radpivotgrid/features/olap-providers/sorting-olap.md index bf591a7f0f..603017a9d8 100644 --- a/controls/radpivotgrid/features/olap-providers/sorting-olap.md +++ b/controls/radpivotgrid/features/olap-providers/sorting-olap.md @@ -30,7 +30,7 @@ The columns are reordered based on their names (check the green rectangle on the ![Rad Pivot Grid Features Sorting OLAP 03](images/RadPivotGrid_Features_Sorting_OLAP_03.png) ->importantThe sorting is set on the __ColumnGroupDescriptions__ or __RowGroupDescriptions__. You cannot set sorting on the __AggregateDescriptions__, but you can sort the columns or rows based on the aggregated values. +>important The sorting is set on the __ColumnGroupDescriptions__ or __RowGroupDescriptions__. You cannot set sorting on the __AggregateDescriptions__, but you can sort the columns or rows based on the aggregated values. ## Sort the data diff --git a/controls/radpivotgrid/features/queryabledataprovider/queryable-calc-fields.md b/controls/radpivotgrid/features/queryabledataprovider/queryable-calc-fields.md index 9ab805845b..cb7e2883f0 100644 --- a/controls/radpivotgrid/features/queryabledataprovider/queryable-calc-fields.md +++ b/controls/radpivotgrid/features/queryabledataprovider/queryable-calc-fields.md @@ -111,7 +111,7 @@ Now it is time to add a new instance of this class to the CalculatedFields colle dataProvider.CalculatedFields.Add(queryableCalculatedField) ``` ->importantIf you add caculated fields in code behind, you have to set the ItemsSource of QueryableDataProvider after you have added all calculated fields or to wrap the code between *BeginInit() - EndInit()* methods (or inside *using DeferRefresh() { ... } section* ). +>important If you add caculated fields in code behind, you have to set the ItemsSource of QueryableDataProvider after you have added all calculated fields or to wrap the code between *BeginInit() - EndInit()* methods (or inside *using DeferRefresh() { ... } section* ). This way the Commission field will be visible in a special folder inside __RadPivotFieldList__ called Calculated Fields. diff --git a/controls/radpivotgrid/features/queryabledataprovider/queryable-group-filtering.md b/controls/radpivotgrid/features/queryabledataprovider/queryable-group-filtering.md index e589787c65..e9e1e2a3a2 100644 --- a/controls/radpivotgrid/features/queryabledataprovider/queryable-group-filtering.md +++ b/controls/radpivotgrid/features/queryabledataprovider/queryable-group-filtering.md @@ -58,7 +58,7 @@ The __LabelFilter__ is used for filtering the data based on the Headers (row or * __is not between__ - showing only groups which header is NOT between the two parameters we pass. ->importantAll conditions are using string comparison between the headers of the groups and the passed parameters. The case-sensitivity depends on the field in the table (if data is in database). +>important All conditions are using string comparison between the headers of the groups and the passed parameters. The case-sensitivity depends on the field in the table (if data is in database). ### Defining Label Filter @@ -209,7 +209,7 @@ __Value Filter__ is applied on __RowGroupDescriptions__/__ColumnGroupDescription * __is not between__ - showing only groups which header is NOT between the two parameters we pass. ->important__Value Filter__ is filtering the groups by number comparison between the *GrandTotals* of the groups and the parameters we pass, while __Label Filter__ is a string filter. +>important __Value Filter__ is filtering the groups by number comparison between the *GrandTotals* of the groups and the parameters we pass, while __Label Filter__ is a string filter. __RadPivotGrid__ without __Value Filter__: diff --git a/controls/radpivotgrid/features/queryabledataprovider/queryable-sorting.md b/controls/radpivotgrid/features/queryabledataprovider/queryable-sorting.md index 4806551a13..ab507d1439 100644 --- a/controls/radpivotgrid/features/queryabledataprovider/queryable-sorting.md +++ b/controls/radpivotgrid/features/queryabledataprovider/queryable-sorting.md @@ -31,7 +31,7 @@ The columns are reordered based on their names (check the green rectangle on the ![Rad Pivot Grid Features Queryable Sorting 03](images/RadPivotGrid_Features_Queryable_Sorting_03.png) ->importantThe sorting is set on the __ColumnGroupDescriptions__ or __RowGroupDescriptions__. You cannot set sorting on the __AggregateDescriptions__, but you can sort the columns or rows based on the aggregated values. +>important The sorting is set on the __ColumnGroupDescriptions__ or __RowGroupDescriptions__. You cannot set sorting on the __AggregateDescriptions__, but you can sort the columns or rows based on the aggregated values. ## Sort the data diff --git a/controls/radpivotgrid/features/radchartview-integration.md b/controls/radpivotgrid/features/radchartview-integration.md index 5ec5458700..d2277d7a9e 100644 --- a/controls/radpivotgrid/features/radchartview-integration.md +++ b/controls/radpivotgrid/features/radchartview-integration.md @@ -32,7 +32,7 @@ In order to create __RadChartView__ you need data source. In our case we need th * __SelectedAxis__ - Gets or sets the PivotAxis which will be used as the Y axis (the value axis) when generating the __SeriesSource__. Default value is *Columns*. ->cautionIf you want to modify __RadChartView__ via __RadPivotFieldList__ or to see the same data in __RadPivotGrid__ and in __RadChartView__ you have to use the same DataProvider in __RadPivotGrid__, __RadPivotFieldList__ and __PivotChartViewModel__. DataProvider is the connection between these elements. +>caution If you want to modify __RadChartView__ via __RadPivotFieldList__ or to see the same data in __RadPivotGrid__ and in __RadChartView__ you have to use the same DataProvider in __RadPivotGrid__, __RadPivotFieldList__ and __PivotChartViewModel__. DataProvider is the connection between these elements. >If you use both __RadPivotGrid__ and __PivotChartViewModel__, changing the GrandTotals/SubTotals position in one of them, will not affect the other one as they are not connected. diff --git a/controls/radpivotgrid/getting-started/getting-started.md b/controls/radpivotgrid/getting-started/getting-started.md index 66ae1da310..d1d7644051 100644 --- a/controls/radpivotgrid/getting-started/getting-started.md +++ b/controls/radpivotgrid/getting-started/getting-started.md @@ -49,7 +49,7 @@ There are two ways to add __RadPivotGrid__ to your application: ``` ->importantYou will have to define the pivot namespace in your __XAML__: __xmlns:pivot="http://schemas.telerik.com/2008/xaml/presentation/pivot"__ +>important You will have to define the pivot namespace in your __XAML__: __xmlns:pivot="http://schemas.telerik.com/2008/xaml/presentation/pivot"__ ## Create Data to Show in RadPivotGrid diff --git a/controls/radpivotgrid/getting-started/started-understanding-pivot.md b/controls/radpivotgrid/getting-started/started-understanding-pivot.md index d84b43b265..f6c724ab7d 100644 --- a/controls/radpivotgrid/getting-started/started-understanding-pivot.md +++ b/controls/radpivotgrid/getting-started/started-understanding-pivot.md @@ -113,7 +113,7 @@ __RadPivotGrid or RadGridView__ In some cases you may get confused which control to use - __RadPivotGrid__ or __RadGridView__. The main difference between the two of them is the view of the data - if you want to show all of your items - you need __RadGridView__. If you want to show only grouped data and different aggregates you need __RadPivotGrid__. ->importantIf you want to show your data items then use __RadGridView__. __RadPivotGrid__ shows only groups and aggregates (without data items behind these groups). +>important If you want to show your data items then use __RadGridView__. __RadPivotGrid__ shows only groups and aggregates (without data items behind these groups). Here is __RadPivotGrid__ with two groupings and two aggregate descriptions applied: diff --git a/controls/radpivotgrid/how-to/howto-set-http-access-to-sqlserver.md b/controls/radpivotgrid/how-to/howto-set-http-access-to-sqlserver.md index 8c360de662..da3da77301 100644 --- a/controls/radpivotgrid/how-to/howto-set-http-access-to-sqlserver.md +++ b/controls/radpivotgrid/how-to/howto-set-http-access-to-sqlserver.md @@ -96,7 +96,7 @@ It is time to configure our Internet Information Service (IIS). To do it start I ![Rad Pivot Grid How To Set Http Access To Cube 13](images/RadPivotGrid_HowTo_SetHttpAccessToCube_13.png) - >importantIn the General Tab above you can set database permissions for this role. Your users will need at least Read permissions. + >important In the General Tab above you can set database permissions for this role. Your users will need at least Read permissions. After applying this you should be able to use XmlaDataProvider in your __RadPivotGrid__ to access the data from your Cube. diff --git a/controls/radpivotgrid/populating-with-data/data-adomd.md b/controls/radpivotgrid/populating-with-data/data-adomd.md index de8ae7d47b..38e79f9e6f 100644 --- a/controls/radpivotgrid/populating-with-data/data-adomd.md +++ b/controls/radpivotgrid/populating-with-data/data-adomd.md @@ -60,7 +60,7 @@ AdomdDataProvider uses four different collections to design the view of RadPivot You can define your AdomdDataProvider as a *StaticResource* in the XAML and then use it in both RadPivotGrid and RadPivotFieldList controls. ->importantThe __pivot__ namespace is URI namespace: __xmlns:pivot="http://schemas.telerik.com/2008/xaml/presentation/pivot"__. It is mandatory to define it if you are using the AdomdDataProvider in your XAML. +>important The __pivot__ namespace is URI namespace: __xmlns:pivot="http://schemas.telerik.com/2008/xaml/presentation/pivot"__. It is mandatory to define it if you are using the AdomdDataProvider in your XAML. ```XAML diff --git a/controls/radpivotgrid/populating-with-data/data-queryable.md b/controls/radpivotgrid/populating-with-data/data-queryable.md index 5c59185b73..8a9413a382 100644 --- a/controls/radpivotgrid/populating-with-data/data-queryable.md +++ b/controls/radpivotgrid/populating-with-data/data-queryable.md @@ -20,7 +20,7 @@ __QueryableDataProvider__ is one of the data source providers that can be used w You can define the __QueryableDataProvider__ as a *StaticResource* in your XAML if it will be used in more than one controls (for example if you have __RadPivotGrid__ and __RadPivotFieldList__ controls in your application) or define it directly for any of the controls you are planning to use: ->importantThe __pivot__ namespace is URI namespace: __xmlns:pivot="http://schemas.telerik.com/2008/xaml/presentation/pivot"__. It is mandatory to define it if you are using the __QueryableDataProvider__ in your XAML. +>important The __pivot__ namespace is URI namespace: __xmlns:pivot="http://schemas.telerik.com/2008/xaml/presentation/pivot"__. It is mandatory to define it if you are using the __QueryableDataProvider__ in your XAML. * Defined as a *StaticResource* and used in __RadPivotGrid__ and __RadPivotFieldList__: @@ -42,7 +42,7 @@ You can define the __QueryableDataProvider__ as a *StaticResource* in your XAML ``` ->cautionIf you set different DataProviders for __RadPivotGrid__ and __RadPivotFieldList__ you will not be able to see any changes in __RadPivotGrid__ even when you change something in __RadPivotFieldList__. +>caution If you set different DataProviders for __RadPivotGrid__ and __RadPivotFieldList__ you will not be able to see any changes in __RadPivotGrid__ even when you change something in __RadPivotFieldList__. You can also create an object of type __QueryableDataProvider__ in the background and after that to use it for your controls: diff --git a/controls/radpivotgrid/populating-with-data/data-xmla.md b/controls/radpivotgrid/populating-with-data/data-xmla.md index 595141edfb..34bae01ba8 100644 --- a/controls/radpivotgrid/populating-with-data/data-xmla.md +++ b/controls/radpivotgrid/populating-with-data/data-xmla.md @@ -22,7 +22,7 @@ Extensible Markup Language for Analysis (XMLA) is a standard that allows client __RadPivotGrid__ provides XMLA access to OLAP data sources. You can use the __XmlaDataProvider__ in your application to connect to your OLAP data source. ->cautionYou have to add reference to the following __Telerik__ assembly to be able to use __XmlaDataProvider__ in your application: Telerik.Pivot.DataProviders.Xmla +>caution You have to add reference to the following __Telerik__ assembly to be able to use __XmlaDataProvider__ in your application: Telerik.Pivot.DataProviders.Xmla __XmlaDataProvider__ has several important properties that have to be defined: @@ -85,7 +85,7 @@ __XmlaDataProvider__ uses four different collections to design the view of __Rad __XmlaDataProvider__ can be defined in the __XAML__ as a *StaticResource* and used by both __RadPivotGrid__ and __RadPivotFieldList__. ->importantThe __pivot__ namespace is URI namespace: __xmlns:pivot="http://schemas.telerik.com/2008/xaml/presentation/pivot"__. It is mandatory to define it if you are using the __XmlaDataProvider__ in your XAML. +>important The __pivot__ namespace is URI namespace: __xmlns:pivot="http://schemas.telerik.com/2008/xaml/presentation/pivot"__. It is mandatory to define it if you are using the __XmlaDataProvider__ in your XAML. diff --git a/controls/radpivotgrid/styles-and-templates/quickstyles.md b/controls/radpivotgrid/styles-and-templates/quickstyles.md index c8cf2701a2..8ce8bd6747 100644 --- a/controls/radpivotgrid/styles-and-templates/quickstyles.md +++ b/controls/radpivotgrid/styles-and-templates/quickstyles.md @@ -125,11 +125,11 @@ __RadPivotGrid__ relays on the __QuickStyle__ in order to get visualized correct ``` ->importantWhen applying a custom __QuickStyle__ all of the properties of the default style should be included in order to have a correct appearance. If there are missing properties, the corresponding elements will appear without any styling. +>important When applying a custom __QuickStyle__ all of the properties of the default style should be included in order to have a correct appearance. If there are missing properties, the corresponding elements will appear without any styling. ->importantIf the __QuickStyle__ property is set to *null* __RadPivotGrid__ will loose all of its styling. +>important If the __QuickStyle__ property is set to *null* __RadPivotGrid__ will loose all of its styling. Afterwards the custom __QuickStyle__ should be applied the following way: diff --git a/controls/radpropertygrid/features/collectioneditor.md b/controls/radpropertygrid/features/collectioneditor.md index ef474bfb9e..eb1fb13991 100644 --- a/controls/radpropertygrid/features/collectioneditor.md +++ b/controls/radpropertygrid/features/collectioneditor.md @@ -25,7 +25,7 @@ __Example 1: Defining CollectionEditor__ ![Rad Property Grid Collection Editor Picker](images/RadPropertyGrid_CollectionEditorPicker.png) ->importantIf you want CollectionEditor to work with a __custom collection__, then the edited collection type should implement __ICollectionView__ and __IEditableCollectionView__ interfaces. +>important If you want CollectionEditor to work with a __custom collection__, then the edited collection type should implement __ICollectionView__ and __IEditableCollectionView__ interfaces. ## Dependencies diff --git a/controls/radpropertygrid/features/data-annotations.md b/controls/radpropertygrid/features/data-annotations.md index 426da805bf..c994e332c9 100644 --- a/controls/radpropertygrid/features/data-annotations.md +++ b/controls/radpropertygrid/features/data-annotations.md @@ -89,7 +89,7 @@ After you run the application you should see the following: ![RadPropertyGrid bound to an Employee instance](images/RadPropertyGrid_Data_Annotations_1.PNG) ->importantIf you want to use Data Annotations in your application, you have to add a reference to the **System.ComponentModel.DataAnnotations** assembly. +>important If you want to use Data Annotations in your application, you have to add a reference to the **System.ComponentModel.DataAnnotations** assembly. ## Display diff --git a/controls/radpropertygrid/features/edit-modes.md b/controls/radpropertygrid/features/edit-modes.md index cfc39ae89e..7c20a70b16 100644 --- a/controls/radpropertygrid/features/edit-modes.md +++ b/controls/radpropertygrid/features/edit-modes.md @@ -42,7 +42,7 @@ Single EditMode introduces the concept of __editing properties one at a time__. It relies on PropertyDefinition’s Binding property. Setting this mode is not supported with dynamic data or when [Property-Sets are defined]({%slug radpropertygrid-defining-propertysets%}). ->important__Single EditMode__ is supported only when __RenderMode is set to Flat__. For more information on the different rendering modes, please check the [Layout Rendering Modes]({%slug radpropertygrid-features-layout-rendering-modes%}) article. +>important __Single EditMode__ is supported only when __RenderMode is set to Flat__. For more information on the different rendering modes, please check the [Layout Rendering Modes]({%slug radpropertygrid-features-layout-rendering-modes%}) article. __Example 2: RadPropertyGrid with EditMode set to Single__ diff --git a/controls/radpropertygrid/features/grouping.md b/controls/radpropertygrid/features/grouping.md index 41c615e82f..c4cd7b9a94 100644 --- a/controls/radpropertygrid/features/grouping.md +++ b/controls/radpropertygrid/features/grouping.md @@ -112,7 +112,7 @@ __Example 6: Collapsing all RadPropertyGrid Groups__ Me.PropertyGrid1.CollapseAllGroups() ``` ->importantYou need to set __RenderMode="Flat"__ in order to be able to execute the methods above. For more information check [Layout Rendering Modes]({%slug radpropertygrid-features-layout-rendering-modes%}). +>important You need to set __RenderMode="Flat"__ in order to be able to execute the methods above. For more information check [Layout Rendering Modes]({%slug radpropertygrid-features-layout-rendering-modes%}). ## GroupDefinitions @@ -137,7 +137,7 @@ __Example 7: Suspending and Resuming notifications__ Me.PropertyGrid1.GroupDefinitions.ResumeNotifications() ``` ->importantYou need to set __RenderMode="Flat"__ in order to be able to work with the GroupDefinitions collection. For more information check [Layout Rendering Modes]({%slug radpropertygrid-features-layout-rendering-modes%}). +>important You need to set __RenderMode="Flat"__ in order to be able to work with the GroupDefinitions collection. For more information check [Layout Rendering Modes]({%slug radpropertygrid-features-layout-rendering-modes%}). ## AutoExpandGroups diff --git a/controls/radpropertygrid/features/layout-rendering-modes.md b/controls/radpropertygrid/features/layout-rendering-modes.md index 7b46df42e2..24acda2b73 100644 --- a/controls/radpropertygrid/features/layout-rendering-modes.md +++ b/controls/radpropertygrid/features/layout-rendering-modes.md @@ -22,7 +22,7 @@ As of __Q2 2013__ RadPropertyGrid exposes new property - __RenderMode__. It repr ->tipFor compatibility reasons, Hierarchical mode is also preserved, but it is recommended to use Flat mode. +>tip For compatibility reasons, Hierarchical mode is also preserved, but it is recommended to use Flat mode. There are a number of benefits of using the __Flat__ render mode. Some are listed below: diff --git a/controls/radpropertygrid/features/readonlyeditorstate.md b/controls/radpropertygrid/features/readonlyeditorstate.md index c197d9bad5..e7ad8db5c5 100644 --- a/controls/radpropertygrid/features/readonlyeditorstate.md +++ b/controls/radpropertygrid/features/readonlyeditorstate.md @@ -20,7 +20,7 @@ The property supports three options: * __ReadOnly__: When this is the selected option, the __IsReadOnly__ property will be set. If the corresponding control does __not have IsReadOnly__ property, then the __IsEnabled__ property will be set as a fallback. This option provides limited interaction with the property values. ->importantThis behavior can be used only when IsReadOnly = “True”. +>important This behavior can be used only when IsReadOnly = “True”. The following examples show how RadPropertyGrid will look like when the ReadOnlyEditorState property is used: diff --git a/controls/radpropertygrid/features/scrolling.md b/controls/radpropertygrid/features/scrolling.md index f9d35ede1f..f9c0f51037 100644 --- a/controls/radpropertygrid/features/scrolling.md +++ b/controls/radpropertygrid/features/scrolling.md @@ -16,9 +16,9 @@ Since __RadPropertyGrid__ utilizes UI virtualization, it only initializes those __ScrollIntoViewAsync(PropertyDefinition propertyDefinition, Action finishedCallback)__ handles the mentioned scenario. Invoking it for a certain __PropertyDefinition__ forces RadPropertyGrid to calculate the needed scroll offset to display its PropertyGridField and then scrolls to it. ->tipAfter the scrolling operation is accomplished, the __finishedCallback__ is executed, passing the __newly realized PropertyGridField as a parameter__. +>tip After the scrolling operation is accomplished, the __finishedCallback__ is executed, passing the __newly realized PropertyGridField as a parameter__. ->importantScrollIntoViewAsync is supported only when __RenderMode is set to Flat__. For more information on the different rendering modes, please check the [Layout Rendering Modes]({%slug radpropertygrid-features-layout-rendering-modes%}) article. +>important ScrollIntoViewAsync is supported only when __RenderMode is set to Flat__. For more information on the different rendering modes, please check the [Layout Rendering Modes]({%slug radpropertygrid-features-layout-rendering-modes%}) article. You can define RadPropertyGrid similar to: @@ -88,7 +88,7 @@ __Figure 2__: RadPropertyGrid after scrolling to a particular PropertyDefinition __ScrollIntoViewAsync__ can also be used in __grouped scenarios__, to bring given PropertyDefinition’s PropertyGridField in the view port. ->tipInvoking it will scroll to the group, expanding it if needed. +>tip Invoking it will scroll to the group, expanding it if needed. However, this functionality is supported only for groups that have valid Key (PropertyDefinition.GroupName). You can find more information on how to define groups in the article on [Grouping Support]({%slug radpropertygrid-grouping%}). @@ -110,7 +110,7 @@ When ScrollIntoView is invoked for a nested PropertyDefinition, its parent’s f To guarantee that such operations will be successfully executed, both root and nested PropertyDefinitions should have a valid Binding set. ->tipIt works with multiple levels of hierarchy. +>tip It works with multiple levels of hierarchy. For sample code on how to perform the scroll please refer to the [ScrollIntoViewAsync section](#the-scrollintoviewasync-method) above. diff --git a/controls/radpropertygrid/features/selection.md b/controls/radpropertygrid/features/selection.md index b87a05af11..2fc40703f3 100644 --- a/controls/radpropertygrid/features/selection.md +++ b/controls/radpropertygrid/features/selection.md @@ -96,7 +96,7 @@ __Example 4: The viewmodel's SelectedDefinition property__ End Class ``` ->cautionAs of R2 2016, the **SelectedField** property, previously marked as obsolete, has officially been removed. +>caution As of R2 2016, the **SelectedField** property, previously marked as obsolete, has officially been removed. ## Events @@ -125,4 +125,4 @@ __Example 6: SelectionChanged event handler__ End Sub ``` ->cautionAs of R2 2016, the **SelectedFieldChanged** event, previously marked as obsolete, has officially been removed. +>caution As of R2 2016, the **SelectedFieldChanged** event, previously marked as obsolete, has officially been removed. diff --git a/controls/radpropertygrid/features/virtualization.md b/controls/radpropertygrid/features/virtualization.md index 778bd4691a..6e13eeb3b7 100644 --- a/controls/radpropertygrid/features/virtualization.md +++ b/controls/radpropertygrid/features/virtualization.md @@ -16,7 +16,7 @@ Since __Q1 2013__ RadPropertyGrid supports __UI Virtualization__. It processes o The following tutorial shows how to bind to a collection of business objects and virtualize the items displayed in a RadPropertyGrid element using the __IsVirtualizing__ property. ->tipBy default __IsVirtualizing__ property is set to __False__. +>tip By default __IsVirtualizing__ property is set to __False__. Here is a simple RadPropertyGrid declaration. @@ -46,4 +46,4 @@ __Example 3: Setting IsVirtualizing property__ ``` ->tipA complete example of RadPropertyGrid UI Virtualization is available in {% if site.site_name == 'Silverlight' %}[this online demo](https://demos.telerik.com/silverlight/#PropertyGrid/Virtualization){% endif %}{% if site.site_name == 'WPF' %}[this online demo](https://demos.telerik.com/wpf/#PropertyGrid/Virtualization){% endif %}. \ No newline at end of file +>tip A complete example of RadPropertyGrid UI Virtualization is available in {% if site.site_name == 'Silverlight' %}[this online demo](https://demos.telerik.com/silverlight/#PropertyGrid/Virtualization){% endif %}{% if site.site_name == 'WPF' %}[this online demo](https://demos.telerik.com/wpf/#PropertyGrid/Virtualization){% endif %}. \ No newline at end of file diff --git a/controls/radpropertygrid/localization/localization.md b/controls/radpropertygrid/localization/localization.md index c526bee82e..9b7b9eaa68 100644 --- a/controls/radpropertygrid/localization/localization.md +++ b/controls/radpropertygrid/localization/localization.md @@ -25,7 +25,7 @@ Here is a list of the supported languages: * __Dutch__ * __Turkish__ ->tipTo learn more about the ways to localize the RadControls please read the common topic about [Localization]({%slug common-localization%}). +>tip To learn more about the ways to localize the RadControls please read the common topic about [Localization]({%slug common-localization%}). ## Resource Keys diff --git a/controls/radpropertygrid/styles-and-templates/group-style-selectors.md b/controls/radpropertygrid/styles-and-templates/group-style-selectors.md index 9f5ed0ee90..5d342d0fb0 100644 --- a/controls/radpropertygrid/styles-and-templates/group-style-selectors.md +++ b/controls/radpropertygrid/styles-and-templates/group-style-selectors.md @@ -134,7 +134,7 @@ The RadPropertyGrid should have the following appearance after the applied chang ![{{ site.framework_name }} RadPropertyGrid with Group Style Selector](images/RadPropertyGrid-group-style-selector.png) ->tipIf you are using [Implicit Themes]({%slug styling-apperance-implicit-styles-overview%}), you should base the style on the one defined for the corresponding theme. +>tip If you are using [Implicit Themes]({%slug styling-apperance-implicit-styles-overview%}), you should base the style on the one defined for the corresponding theme. ## See Also diff --git a/controls/radpropertygrid/styles-and-templates/overview.md b/controls/radpropertygrid/styles-and-templates/overview.md index f72f76c2b4..75138131fd 100644 --- a/controls/radpropertygrid/styles-and-templates/overview.md +++ b/controls/radpropertygrid/styles-and-templates/overview.md @@ -12,7 +12,7 @@ position: 0 This section is intended to give you a broad understanding of the possible ways by which you can change the visual appearance of RadPropertyGrid and its elements. There is also comprehensive information about their ControlTemplates. You will need this information, if you want to customize their appearance. ->tipTo learn how to style {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %} RadControls read the common topic about [Setting a Theme (Using Implicit Styles)]({%slug styling-apperance-implicit-styles-overview%}). +>tip To learn how to style {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %} RadControls read the common topic about [Setting a Theme (Using Implicit Styles)]({%slug styling-apperance-implicit-styles-overview%}). >There is also another way to obtain the template of a particular visual element.In the installation folder on your PC, go to __Themes__ folder (__Themes.Implicit in case you're using__) and select the theme that you use in your application. Then drill down to find the respective __Telerik.Windows.Controls.Data.xaml__ file in that directory. From this resource dictionary you can extract any needed resources. diff --git a/controls/radpropertygrid/styles-and-templates/templates-structure.md b/controls/radpropertygrid/styles-and-templates/templates-structure.md index c786863587..b1de9e1aea 100644 --- a/controls/radpropertygrid/styles-and-templates/templates-structure.md +++ b/controls/radpropertygrid/styles-and-templates/templates-structure.md @@ -16,7 +16,7 @@ Like most UI controls, RadPropertyGrid allows you to template it in order to cha * [PropertyGridField Template Structure](#propertygridfield-template) ->tipFor more information about templating and how to modify the default templates read the common topic on [Implicit Styles]({%slug styling-apperance-implicit-styles-overview%}). +>tip For more information about templating and how to modify the default templates read the common topic on [Implicit Styles]({%slug styling-apperance-implicit-styles-overview%}). Using [Implicit Styles]({%slug styling-apperance-implicit-styles-overview%}) gives you the ability to easily extract and edit the default ControlTemplates of the controls. You can follow [this article]({%slug styling-apperance-editing-control-templates%}) on two different approaches on how to extract the ControlTemplates. diff --git a/controls/radradialmenu/commands/radialmenu.md b/controls/radradialmenu/commands/radialmenu.md index 3cc478cf8a..e4c9fd450b 100644 --- a/controls/radradialmenu/commands/radialmenu.md +++ b/controls/radradialmenu/commands/radialmenu.md @@ -49,7 +49,7 @@ __RadialMenuCommand__ class exposes the following properties: * __Owner__ - gets the RadRadialMenu instance that has executed this command. ->importantCustom commands have higher priority than the default commands. +>important Custom commands have higher priority than the default commands. The next example will show how to implement custom command that will be executed when the user navigates to the children of a menu item: diff --git a/controls/radradialmenu/features/contextmenu.md b/controls/radradialmenu/features/contextmenu.md index 1d0f80797d..81caec518f 100644 --- a/controls/radradialmenu/features/contextmenu.md +++ b/controls/radradialmenu/features/contextmenu.md @@ -32,7 +32,7 @@ __Example 1: Setting ShowEventName/HideEventName properties__ ``` ->importantThe values set to ShowEventName/HideEventName should be valid event names of the target element. +>important The values set to ShowEventName/HideEventName should be valid event names of the target element. ## Using the static RadialMenuCommands class diff --git a/controls/radradialmenu/how-to/howto-customize-tooltip.md b/controls/radradialmenu/how-to/howto-customize-tooltip.md index cc5cc522c8..be148daab5 100644 --- a/controls/radradialmenu/how-to/howto-customize-tooltip.md +++ b/controls/radradialmenu/how-to/howto-customize-tooltip.md @@ -59,7 +59,7 @@ Figure 1: Custom ToolTipContent You could customize the Style and Template of the ToolTip of the __RadRadialMenu__ by creating a Style based on the default __MenuToolToolTipStyle__ with a TargetType set to __MenuToolTip__. ->tipThe default __MenuToolTipStyle__ could be extracted the UI for {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %} installation folder. Go into the __Themes.Implicit__ folder and select the theme that you have chosen to use. Drill down to find the Telerik.Windows.Controls.Navigation.xaml file in the directory that corresponds to your theme. From this resource dictionary extract the __MenuToolToolTipStyle__ and copy it into your project. +>tip The default __MenuToolTipStyle__ could be extracted the UI for {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %} installation folder. Go into the __Themes.Implicit__ folder and select the theme that you have chosen to use. Drill down to find the Telerik.Windows.Controls.Navigation.xaml file in the directory that corresponds to your theme. From this resource dictionary extract the __MenuToolToolTipStyle__ and copy it into your project. __Example 3__ shows a quick sample of a custom MenuToolTipStyle. diff --git a/controls/radradialmenu/styles-and-templates/setting-theme.md b/controls/radradialmenu/styles-and-templates/setting-theme.md index 2720bcdd77..09b70c6869 100644 --- a/controls/radradialmenu/styles-and-templates/setting-theme.md +++ b/controls/radradialmenu/styles-and-templates/setting-theme.md @@ -12,7 +12,7 @@ position: 0 The purpose of this article is to show you how to set a built-in theme to __RadRadialMenu__. ->tipDetailed information about the use of implicit styles can be found [here]({%slug styling-apperance-implicit-styles-overview%}). +>tip Detailed information about the use of implicit styles can be found [here]({%slug styling-apperance-implicit-styles-overview%}). So, in order to set a theme to the RadialMenu, you should merge the following xaml files in App.xaml file: diff --git a/controls/radribbonview/styling-and-appearance/styling-groupchrome.md b/controls/radribbonview/styling-and-appearance/styling-groupchrome.md index 48b1ef0b78..2e31a3fd55 100644 --- a/controls/radribbonview/styling-and-appearance/styling-groupchrome.md +++ b/controls/radribbonview/styling-and-appearance/styling-groupchrome.md @@ -38,7 +38,7 @@ After clicking 'OK', Expression Blend will generate the default style of the __G {% if site.site_name == 'WPF' %} Change the elements' properties until you get the desired look. ->tipYou can also modify the triggers defined for the __GroupChrome__. They are located in the 'Triggers' pane. +>tip You can also modify the triggers defined for the __GroupChrome__. They are located in the 'Triggers' pane. ![{{ site.framework_name }} RadRibbonView ](images/RibbonView_Styling_GroupChrome_Triggers.png) {% endif %} {% if site.site_name == 'Silverlight' %} diff --git a/controls/radrichtextbox/document-elements/table/table-ui.md b/controls/radrichtextbox/document-elements/table/table-ui.md index 1a79bc4489..536b4fdc36 100644 --- a/controls/radrichtextbox/document-elements/table/table-ui.md +++ b/controls/radrichtextbox/document-elements/table/table-ui.md @@ -52,6 +52,6 @@ Additionally, the built-in context menu of the __RadRichTextBox__ gives the user ![Rad Rich Text Box Features Layout Elements Tables 06](images/RadRichTextBox_Features_LayoutElements_Tables_06.png) ->tipTo wire these dialogs to your own UI you can use the __ShowTablePropertiesDialog()__ method of __RadRichTextBox__ or the __ShowTablePropertiesCommand__. +>tip To wire these dialogs to your own UI you can use the __ShowTablePropertiesDialog()__ method of __RadRichTextBox__ or the __ShowTablePropertiesCommand__. diff --git a/controls/radrichtextbox/features-keyboard-support.md b/controls/radrichtextbox/features-keyboard-support.md index 569405e460..443d18de97 100644 --- a/controls/radrichtextbox/features-keyboard-support.md +++ b/controls/radrichtextbox/features-keyboard-support.md @@ -13,7 +13,7 @@ position: 10 {% if site.site_name == 'Silverlight' %} Telerik __RichTextBox__ for Silverlight supports commands in a way that is similar to the commanding mechanism in WPF. It is only natural that some of these commands be triggered on key combinations. There are default key-bindings defined for the most widely used commands. ->importantNote that the browser could handle some of the shortcuts and some of them cannot be even enabled. RadRichTextBox is not capable of modifying this behavior as it is up to the browser. +>important Note that the browser could handle some of the shortcuts and some of them cannot be even enabled. RadRichTextBox is not capable of modifying this behavior as it is up to the browser. {% endif %} {% if site.site_name == 'WPF' %} diff --git a/controls/radrichtextbox/features-ui-virtualization.md b/controls/radrichtextbox/features-ui-virtualization.md index 48b50ac0b5..5282f1be8c 100644 --- a/controls/radrichtextbox/features-ui-virtualization.md +++ b/controls/radrichtextbox/features-ui-virtualization.md @@ -12,7 +12,7 @@ position: 13 __RadRichTextBox__ supports __UI Virtualization__, which enables it to processes only information that is loaded in the viewable area. In this way, UI elements are created only for the parts of the document actually shown on screen. This reduces the memory footprint of the application and speeds up the loading time, thus additionally enhancing the UI performance. ->importantTry not to place RadRichTextBox in controls/panels which will measure it with infinity. For example, __ScrollViewer__, __StackPanel__ and Grid with __Row.Height="Auto"__ or __Column.Width="Auto"__ will measure with infinity. In these cases, RadRichTextBox is measured with infinity and cannot determine what part of the document is shown in the viewport, therefore the virtualization turns off. +>important Try not to place RadRichTextBox in controls/panels which will measure it with infinity. For example, __ScrollViewer__, __StackPanel__ and Grid with __Row.Height="Auto"__ or __Column.Width="Auto"__ will measure with infinity. In these cases, RadRichTextBox is measured with infinity and cannot determine what part of the document is shown in the viewport, therefore the virtualization turns off. ## See Also * [Import/Export]({%slug radrichtextbox-features-import-export%}) diff --git a/controls/radrichtextbox/features/clipboard-support.md b/controls/radrichtextbox/features/clipboard-support.md index 0631435407..aa2b6ef527 100644 --- a/controls/radrichtextbox/features/clipboard-support.md +++ b/controls/radrichtextbox/features/clipboard-support.md @@ -60,7 +60,7 @@ __Example 2: Wiring UI to the commands related to the clipboard__ ## Key Bindings ->tipIn order to copy, paste or cut, the standard keyboard shortcuts can also be used - __Ctrl + C__, __Ctrl + V__, __Ctrl + X__. +>tip In order to copy, paste or cut, the standard keyboard shortcuts can also be used - __Ctrl + C__, __Ctrl + V__, __Ctrl + X__. To learn more about the default key-bindings of the editor and ways to override them, you can refer to the [Keyboard Support]({%slug radrichtextbox-features-keyboard-support%}) article. @@ -124,7 +124,7 @@ You can also reorder the clipboard handlers to use first HTML paste and fallback The API allows you to customize the content which is being copied or pasted in RadRichTextBox. ->tipYou can handle the [CommandExecuting event]({%slug radrichtextbox-features-commands%}#command-related-events) so you can catch the moment of the operation's execution. +>tip You can handle the [CommandExecuting event]({%slug radrichtextbox-features-commands%}#command-related-events) so you can catch the moment of the operation's execution. ### ClipboardEx Class diff --git a/controls/radrichtextbox/features/code-block.md b/controls/radrichtextbox/features/code-block.md index 8ae9200bfb..4f6ddc6bbd 100644 --- a/controls/radrichtextbox/features/code-block.md +++ b/controls/radrichtextbox/features/code-block.md @@ -59,7 +59,7 @@ Additionally, you can enable the display of line numbers and the alternating lin The inner representation of the code block in the document is achieved by surrounding the content with __CodeAnnotationRangeStart__ and __CodeAnnotationRangeEnd__. ->tipMore about annotations you can learn in the respective help article [here]({%slug radrichtextbox-features-document-elements-annotations%}). +>tip More about annotations you can learn in the respective help article [here]({%slug radrichtextbox-features-document-elements-annotations%}). To remove the code block you can use the __DeleteCodeBlock()__ method of __RadRichTextBox__ accepting __CodeAnnotationRangeStart__ as parameter: @@ -101,6 +101,6 @@ You can also register or change which style will be used for which classificatio ``` ->tipYou can download a runnable project showing how to add custom code formatting language from our online SDK repository [here](https://github.com/telerik/xaml-sdk), the example is listed as __RadRichTextBox / CustomCodeFormattingLanguage__. +>tip You can download a runnable project showing how to add custom code formatting language from our online SDK repository [here](https://github.com/telerik/xaml-sdk), the example is listed as __RadRichTextBox / CustomCodeFormattingLanguage__. diff --git a/controls/radrichtextbox/features/commands.md b/controls/radrichtextbox/features/commands.md index 9145687698..a06f825639 100644 --- a/controls/radrichtextbox/features/commands.md +++ b/controls/radrichtextbox/features/commands.md @@ -18,7 +18,7 @@ __RadRichTextBox__ exposes a full set of commands that provide an alternative to In order to use the command with a UI Element that supports commanding, you have to bind the __Command__ property of the element to the respective command of the __RadRichTextBox__. ->tipTo see a list of all the commands exposed by __RadRichTextBox__, visit {% if site.site_name == 'Silverlight' %}[this topic](https://docs.telerik.com/devtools/silverlight/api/telerik.windows.documents.richtextboxcommands){% endif %}{% if site.site_name == 'WPF' %}[this topic](https://docs.telerik.com/devtools/wpf/api/telerik.windows.documents.richtextboxcommands){% endif %}. +>tip To see a list of all the commands exposed by __RadRichTextBox__, visit {% if site.site_name == 'Silverlight' %}[this topic](https://docs.telerik.com/devtools/silverlight/api/telerik.windows.documents.richtextboxcommands){% endif %}{% if site.site_name == 'WPF' %}[this topic](https://docs.telerik.com/devtools/wpf/api/telerik.windows.documents.richtextboxcommands){% endif %}. Here is an example with a __RadToggleButtonControl__. @@ -82,7 +82,7 @@ Now the button will respond to the current state of the selection. You can also use the functionality provided by the __RadRichTextBoxRibbonUI__ class in order to get the event handling out of the box. ->tipThe __RadRichTextBoxRibbonUI__ provides you with a fully predefined UI for RadRichTextBox. To learn how to use it read [this topic]({%slug radrichtextbox-features-radrichtextboxribbonui%}). +>tip The __RadRichTextBoxRibbonUI__ provides you with a fully predefined UI for RadRichTextBox. To learn how to use it read [this topic]({%slug radrichtextbox-features-radrichtextboxribbonui%}). If you are building your UI manually, for example using a **RadRibbonView** control, you have to only bind the command to the __RadRichTextBoxRibbonUI__.__RichTextCommand__ attached property of the desired __RadRibbonView__ control. Here is an example with a __RadRibbonToggleButton__. @@ -103,7 +103,7 @@ If you are building your UI manually, for example using a **RadRibbonView** cont The __RadRibbonToggleButton__ will get automatically toggled whenever the context of the caret is an italic text. ->tipMore about the specific buttons introduced with __RadRibbonView__ you can find [here](http://www.telerik.com/help/wpf/allmembers_t_telerik_windows_documents_richtextboxcommands_richtextboxcommands.html). +>tip More about the specific buttons introduced with __RadRibbonView__ you can find [here](http://www.telerik.com/help/wpf/allmembers_t_telerik_windows_documents_richtextboxcommands_richtextboxcommands.html). ![Rad Rich Text Box Features Commands 02](images/RadRichTextBox_Features_Commands_02.png) diff --git a/controls/radrichtextbox/features/comments.md b/controls/radrichtextbox/features/comments.md index 0b98a172b1..5b5f82c4b5 100644 --- a/controls/radrichtextbox/features/comments.md +++ b/controls/radrichtextbox/features/comments.md @@ -55,7 +55,7 @@ Here is an example usage of these commands: ->tipIn order to learn more about commands and how to use them refer to [this article]({%slug radrichtextbox-features-commands%}). +>tip In order to learn more about commands and how to use them refer to [this article]({%slug radrichtextbox-features-commands%}). ## Working with Comments Programmatically diff --git a/controls/radrichtextbox/features/format-painter.md b/controls/radrichtextbox/features/format-painter.md index f826e63826..0281bac18d 100644 --- a/controls/radrichtextbox/features/format-painter.md +++ b/controls/radrichtextbox/features/format-painter.md @@ -34,7 +34,7 @@ The following commands related to the copying of formatting are available in the ->tipIn order to learn more about commands and how to use them refer to the [Commands topic]({%slug radrichtextbox-features-commands%}). +>tip In order to learn more about commands and how to use them refer to the [Commands topic]({%slug radrichtextbox-features-commands%}). >There are also shortcuts implemented for easier usage: >- *Ctrl+Shift+C* copies the formatting. diff --git a/controls/radrichtextbox/features/line-numbering.md b/controls/radrichtextbox/features/line-numbering.md index 3de0ca8979..df491577f8 100644 --- a/controls/radrichtextbox/features/line-numbering.md +++ b/controls/radrichtextbox/features/line-numbering.md @@ -30,7 +30,7 @@ The following commands related to the numbering of lines are available in the ** * **SuppressLineNumberingForCurrentParagraphCommand**: Disables the numbering for the currently selected paragraph(s). * **ShowLineNumberingDialogCommand**: Opens the dialog enabling users to set different line numbering options. ->tipIn order to learn more about commands and how to use them refer to the [Commands topic]({%slug radrichtextbox-features-commands%}). +>tip In order to learn more about commands and how to use them refer to the [Commands topic]({%slug radrichtextbox-features-commands%}). ## Using Line Numbering Programmatically diff --git a/controls/radrichtextbox/features/read-only-ranges.md b/controls/radrichtextbox/features/read-only-ranges.md index a89bddd4df..53f79ce1cf 100644 --- a/controls/radrichtextbox/features/read-only-ranges.md +++ b/controls/radrichtextbox/features/read-only-ranges.md @@ -19,7 +19,7 @@ The following article explains how to use read only ranges in RadRichTextBox Read only ranges are a convenient way to restrict some of the content of a particular document from editing. When content is in a read only range, users are unable to edit, format or delete it. What is more, manipulating the document from code with __RadRichTextBox__'s API or commands is also not possible. Additionally, the predefined UI - __RadRichTextBoxRibbonUI__ corresponds to the state of the document when the caret is located in a read only region by fading out the parts which operate with the document content in order to notify users they cannot edit this content. ->tip__RadRichTextBox__ also provides another, more advanced option for restricting content which allows particular users or groups of users to edit different parts of a document. For more information on this check the documentation of the [Document Protection]({%slug radrichtextbox-features-document-protection%}) feature. +>tip __RadRichTextBox__ also provides another, more advanced option for restricting content which allows particular users or groups of users to edit different parts of a document. For more information on this check the documentation of the [Document Protection]({%slug radrichtextbox-features-document-protection%}) feature. A read only annotation range is represented in __RadDocument__'s structure by two paired annotation markers – a __ReadOnlyRangeStart__ instance and a __ReadOnlyRangeEnd__ instance. Both are inline elements, thus users are able to edit the document prior and after the annotation markers. More on Annotations you can find [here]({%slug radrichtextbox-features-document-elements-annotations%}). @@ -47,7 +47,7 @@ When the document is measured (for example, shown in a __RadRichTextBox__), you ``` ->tipGenerally, editing the content of a read only range is not possible through the UI and through __RadRichtextBox__'s API. However, when manipulating a document using __RadDocumentEditor__ you can set the __RespectReadOnlyRanges__ property of __RadDocumentEditor__ to *false* and read only ranges will be ignored. +>tip Generally, editing the content of a read only range is not possible through the UI and through __RadRichtextBox__'s API. However, when manipulating a document using __RadDocumentEditor__ you can set the __RespectReadOnlyRanges__ property of __RadDocumentEditor__ to *false* and read only ranges will be ignored. ### Insert in Non-measured Document diff --git a/controls/radrichtextbox/features/search.md b/controls/radrichtextbox/features/search.md index 4bfc51043d..ea49121600 100644 --- a/controls/radrichtextbox/features/search.md +++ b/controls/radrichtextbox/features/search.md @@ -15,7 +15,7 @@ published: True __RadRichTextBox__ supports searching the contents of the document along with providing some methods for manipulating the selection. Used in combination, they become quite a powerful tool enabling scenarios like highlighting of specific parts of the document or replacing words and collocations. ->tipTo learn more about the selection API read the [Selection]({%slug radrichtextbox-features-selection%}) topic. +>tip To learn more about the selection API read the [Selection]({%slug radrichtextbox-features-selection%}) topic. The simplest scenario – finding a string in the content of the document can be implemented with the following code: diff --git a/controls/radrichtextbox/features/spellcheck.md b/controls/radrichtextbox/features/spellcheck.md index f09bcc7967..197cb7294b 100644 --- a/controls/radrichtextbox/features/spellcheck.md +++ b/controls/radrichtextbox/features/spellcheck.md @@ -115,7 +115,7 @@ Here is an example of such a dictionary that adds the words in the "CustomDictio > * __Application__: The dictionary is available only for the particular application. ->tipWhen adding a dictionary that implements the __ICustomWordDictionary__ interface object use the __AddCustomDictionary(ICustomWordDictionary customDictionary, CultureInfo culture)__ method of the __DocumentSpellChecker__ class. You can also associate a custom dictionary to a specific culture. The method to remove it is __RemoveCustomDictionary(ICustomWordDictionary customDictionary, CultureInfo culture)__. +>tip When adding a dictionary that implements the __ICustomWordDictionary__ interface object use the __AddCustomDictionary(ICustomWordDictionary customDictionary, CultureInfo culture)__ method of the __DocumentSpellChecker__ class. You can also associate a custom dictionary to a specific culture. The method to remove it is __RemoveCustomDictionary(ICustomWordDictionary customDictionary, CultureInfo culture)__. __Example 4: Creating a custom dictionary__ diff --git a/controls/radrichtextbox/getting-started/features-formatting-api.md b/controls/radrichtextbox/getting-started/features-formatting-api.md index 3c021f1453..e72418f79e 100644 --- a/controls/radrichtextbox/getting-started/features-formatting-api.md +++ b/controls/radrichtextbox/getting-started/features-formatting-api.md @@ -23,7 +23,7 @@ If you want to format the content of __RadRichTextBox__ at run time, you have to The __RadRichTextBox__ exposes methods that change the style of the selected text or the paragraph. When a method is called, the respective style is applied to the selected text. If there is no selection available, the style is applied to the word in which the caret is located. ->tipRadRichTextBox provides a fully functional formatting UI out of the box. To learn more about it read the [RadRichTextBoxRibbonUI]({%slug radrichtextbox-features-radrichtextboxribbonui%}) topic. +>tip RadRichTextBox provides a fully functional formatting UI out of the box. To learn more about it read the [RadRichTextBoxRibbonUI]({%slug radrichtextbox-features-radrichtextboxribbonui%}) topic. Here is an example of a toggle button that upon checking should make the selection or the current word bold. In the handler of the __Click__ event of the __RadToggleButton__, the __ToggleBold()__ method of __RadRichTextBox__ is called. @@ -61,7 +61,7 @@ Here is an example of a toggle button that upon checking should make the selecti __RadRichTextBox__ supports headers and footers. They are represented through separate instances of __RadRichTextBox__. When a document has headers and footers you can use the __ActiveDocumentEditor__ property of __RadRichTextBox__ to get the editor instance where the caret is currently situated. ->tipYou can find more about the Header and Footer functionality in [this article]({%slug radrichtextbox-features-headers-and-footers%}). +>tip You can find more about the Header and Footer functionality in [this article]({%slug radrichtextbox-features-headers-and-footers%}). The following example inserts the word "text" at the CaretPosition. diff --git a/controls/radrichtextbox/how-to/switching-icons-at-runtime.md b/controls/radrichtextbox/how-to/switching-icons-at-runtime.md index bc44aedb7e..64027c9d7c 100644 --- a/controls/radrichtextbox/how-to/switching-icons-at-runtime.md +++ b/controls/radrichtextbox/how-to/switching-icons-at-runtime.md @@ -29,7 +29,7 @@ __Example 1: Creating IconSources__ ``` ->tipTo browse all icons you can download the source code of the controls from your Telerik account. The images are located at {%if site.site_name == 'WPF' %}\Telerik\_UI\_for\_WPF\_Source\_[Version]\Controls\RichTextBox\RichTextBoxUI\Images{%endif%}{%if site.site_name == 'Silerlight' %}\Telerik\_UI\_for\_Silerlight\_Source\_[Version]\Controls\RichTextBox\RichTextBoxUI\Images{%endif%}. +>tip To browse all icons you can download the source code of the controls from your Telerik account. The images are located at {%if site.site_name == 'WPF' %}\Telerik\_UI\_for\_WPF\_Source\_[Version]\Controls\RichTextBox\RichTextBoxUI\Images{%endif%}{%if site.site_name == 'Silerlight' %}\Telerik\_UI\_for\_Silerlight\_Source\_[Version]\Controls\RichTextBox\RichTextBoxUI\Images{%endif%}. ## See Also diff --git a/controls/radrichtextbox/how-to/update-current-color-in-ui.md b/controls/radrichtextbox/how-to/update-current-color-in-ui.md index 75f3b84284..2f7262560e 100644 --- a/controls/radrichtextbox/how-to/update-current-color-in-ui.md +++ b/controls/radrichtextbox/how-to/update-current-color-in-ui.md @@ -29,7 +29,7 @@ __Example 1: Add FormattingColorPicker__ ->tipTo learn more about the commands exposed by the __RadRichTextBox__ and how to use them read [here]({%slug radrichtextbox-features-commands%}). +>tip To learn more about the commands exposed by the __RadRichTextBox__ and how to use them read [here]({%slug radrichtextbox-features-commands%}). ### ActiveColor property diff --git a/controls/radrichtextbox/import-export/docx/docxformatprovider.md b/controls/radrichtextbox/import-export/docx/docxformatprovider.md index 973dd1267e..071348efc3 100644 --- a/controls/radrichtextbox/import-export/docx/docxformatprovider.md +++ b/controls/radrichtextbox/import-export/docx/docxformatprovider.md @@ -59,7 +59,7 @@ __Example 4: Export a document to a byte array__ The resulting documents can be opened in any application that supports DOCX documents. ->tipHowever, the format providers cannot be used in XAML and you have to implement a logic that will call their Import() and Export() methods. This is something that you might not want to be concerned with when using RadRichTextBox in a data bound scenarios. For such cases, the [DataProvider]({%slug radrichtextbox-features-data-providers%}) classes are used. They wrap the FormatProviders' functionality and allow its usage in XAML. +>tip However, the format providers cannot be used in XAML and you have to implement a logic that will call their Import() and Export() methods. This is something that you might not want to be concerned with when using RadRichTextBox in a data bound scenarios. For such cases, the [DataProvider]({%slug radrichtextbox-features-data-providers%}) classes are used. They wrap the FormatProviders' functionality and allow its usage in XAML. ## See Also diff --git a/controls/radrichtextbox/import-export/features-data-providers.md b/controls/radrichtextbox/import-export/features-data-providers.md index f0265419bc..fef03b8a4d 100644 --- a/controls/radrichtextbox/import-export/features-data-providers.md +++ b/controls/radrichtextbox/import-export/features-data-providers.md @@ -26,7 +26,7 @@ The __RadRichTextBox__ control allows you to export and import its documents int * [__TxtFormatProvider__]({%slug radrichtextbox-import-export-txt-txtformatprovider%}) ->tipFor more information, check out the [Import/Export]({%slug radrichtextbox-features-import-export%}) topic. +>tip For more information, check out the [Import/Export]({%slug radrichtextbox-features-import-export%}) topic. However, the format providers cannot be used in XAML and you have to implement a logic that will call their Import() and Export() methods. This is something that you might not want to be concerned with when using __RadRichTextBox__ in a data bound scenarios. For such cases, the __DataProvider__ classes are used. They wrap the __FormatProviders'__ functionality and allow its usage in XAML. Currently, the following __DataProvider__ classes are available: @@ -46,7 +46,7 @@ However, the format providers cannot be used in XAML and you have to implement a * __TxtDataProvider__: Use when you want to bind plain text source to __RadRichTextBox__. ->tipData providers have to be declared in the visual tree and not the Resource dictionary of a control. You don't have to worry about the place in the visual tree where a provider is, as it does not have a visual representation. +>tip Data providers have to be declared in the visual tree and not the Resource dictionary of a control. You don't have to worry about the place in the visual tree where a provider is, as it does not have a visual representation. >important RadRichTextBox's data providers encapsulate the logic of the format providers that come with the control. What they do internally is import/export the document using the respective format provider. By default, the property in your view model will be updated on each document change. As this triggers an export to the document you might notice some delay when typing in the control. You could try customizing this by setting the **UpdateSourceTrigger** property of the data provider to **LostFocus** or **Explicit**. @@ -73,9 +73,9 @@ The __DataProviders__ can be easily used to bind __RadRichTextBox__ to a XAML, H | **Docx** | DocxDataProvider | {% if site.site_name == 'Silverlight' %} ->tipIt is best to declare data providers in the visual tree, as this way the binding will be properly updated when the data context is changed. You don't have to worry about the place in the visual tree where the provider is, as it does not have a visual representation.{% endif %} +>tip It is best to declare data providers in the visual tree, as this way the binding will be properly updated when the data context is changed. You don't have to worry about the place in the visual tree where the provider is, as it does not have a visual representation.{% endif %} ->tipEach __DataProvider__ class is located in the same assembly as the corresponding __FormatProvider__ class. For example, the __XamlFormatProvider__ class is in the __Telerik.Windows.Documents.FormatProviders.Xaml.dll__ assembly. Only the __TxtDataProvider__ is located in the __Telerik.Windows.Documents__ assembly. In order to use a data provider, make sure to have referenced the required assembly. +>tip Each __DataProvider__ class is located in the same assembly as the corresponding __FormatProvider__ class. For example, the __XamlFormatProvider__ class is in the __Telerik.Windows.Documents.FormatProviders.Xaml.dll__ assembly. Only the __TxtDataProvider__ is located in the __Telerik.Windows.Documents__ assembly. In order to use a data provider, make sure to have referenced the required assembly. >The __DataProviders__ can be accessed via the default Telerik namespace: diff --git a/controls/radrichtextbox/import-export/features-import-export.md b/controls/radrichtextbox/import-export/features-import-export.md index 8e4fec9e56..ed0b077652 100644 --- a/controls/radrichtextbox/import-export/features-import-export.md +++ b/controls/radrichtextbox/import-export/features-import-export.md @@ -28,7 +28,7 @@ __RadRichTextBox__ allows you to export and import its content. This is useful i * __PDF__: To export documents to __PDF__ you have to use the [__PdfFormatProvider__]({%slug radrichtextbox-import-export-pdf-pdfformatprovider%}) class. ->tipEach __FormatProvider__ class is located in a separate assembly matching its name. For example, the __XamlFormatProvider__ class is in the __Telerik.Windows.Documents.FormatProviders.Xaml.dll__ assembly. The only exception is the __TxtFormatProvider__, which is included in __Telerik.Windows.Documents__. +>tip Each __FormatProvider__ class is located in a separate assembly matching its name. For example, the __XamlFormatProvider__ class is in the __Telerik.Windows.Documents.FormatProviders.Xaml.dll__ assembly. The only exception is the __TxtFormatProvider__, which is included in __Telerik.Windows.Documents__. ## Specifics diff --git a/controls/radrichtextbox/import-export/plain-text/txt-txtformatprovider.md b/controls/radrichtextbox/import-export/plain-text/txt-txtformatprovider.md index 8c10e09fe8..39d655784b 100644 --- a/controls/radrichtextbox/import-export/plain-text/txt-txtformatprovider.md +++ b/controls/radrichtextbox/import-export/plain-text/txt-txtformatprovider.md @@ -70,7 +70,7 @@ __Example 4: Export a document to a string__ string output = provider.Export(document); ``` ->tipHowever, the format providers cannot be used in XAML and you have to implement a logic that will call their Import() and Export() methods. This is something that you might not want to be concerned with when using RadRichTextBox in a data bound scenarios. For such cases, the [DataProvider]({%slug radrichtextbox-features-data-providers%}) classes are used. They wrap the FormatProviders' functionality and allow its usage in XAML. +>tip However, the format providers cannot be used in XAML and you have to implement a logic that will call their Import() and Export() methods. This is something that you might not want to be concerned with when using RadRichTextBox in a data bound scenarios. For such cases, the [DataProvider]({%slug radrichtextbox-features-data-providers%}) classes are used. They wrap the FormatProviders' functionality and allow its usage in XAML. ## See Also diff --git a/controls/radrichtextbox/import-export/rtf/rtfformatprovider.md b/controls/radrichtextbox/import-export/rtf/rtfformatprovider.md index 263d38c11f..9b93702b49 100644 --- a/controls/radrichtextbox/import-export/rtf/rtfformatprovider.md +++ b/controls/radrichtextbox/import-export/rtf/rtfformatprovider.md @@ -71,7 +71,7 @@ __Example 4: Export a document to a string__ The resulting documents can be opened in any application that supports RTF documents. ->tipHowever, the format providers cannot be used in XAML and you have to implement a logic that will call their Import() and Export() methods. This is something that you might not want to be concerned with when using RadRichTextBox in a data bound scenarios. For such cases, the [DataProvider]({%slug radrichtextbox-features-data-providers%}) classes are used. They wrap the FormatProviders' functionality and allow its usage in XAML. +>tip However, the format providers cannot be used in XAML and you have to implement a logic that will call their Import() and Export() methods. This is something that you might not want to be concerned with when using RadRichTextBox in a data bound scenarios. For such cases, the [DataProvider]({%slug radrichtextbox-features-data-providers%}) classes are used. They wrap the FormatProviders' functionality and allow its usage in XAML. ## See Also diff --git a/controls/radrichtextbox/ui-for-applying-rich-text-formatting/applying-styles.md b/controls/radrichtextbox/ui-for-applying-rich-text-formatting/applying-styles.md index c511c771ef..4d68a7bc45 100644 --- a/controls/radrichtextbox/ui-for-applying-rich-text-formatting/applying-styles.md +++ b/controls/radrichtextbox/ui-for-applying-rich-text-formatting/applying-styles.md @@ -43,7 +43,7 @@ It is also possible to apply a style using the Styles dialog as shown in the pic Other than using the API to declare a style, you can also use the UI. ->tipMore info on how to create a style from code can be found in the [Styles article]({%slug radrichtextbox-features-styles%}) +>tip More info on how to create a style from code can be found in the [Styles article]({%slug radrichtextbox-features-styles%}) ![Rad Rich Text Box UI For Applying Rich Text Formatting Applying Styles 03](images/RadRichTextBox_UI_For_Applying_Rich_Text_Formatting_Applying_Styles_03.png) @@ -82,7 +82,7 @@ The predefined set of Styles in RadDocument cannot be deleted using the UI. Only ![Rad Rich Text Box UI For Applying Rich Text Formatting Applying Styles 06](images/RadRichTextBox_UI_For_Applying_Rich_Text_Formatting_Applying_Styles_06.png) ->tipIt is possible to remove the default styles from the Quick Styles by using the Modify option and unchecking the Add to Quick Styles checkbox. +>tip It is possible to remove the default styles from the Quick Styles by using the Modify option and unchecking the Add to Quick Styles checkbox. ![Rad Rich Text Box UI For Applying Rich Text Formatting Applying Styles 07](images/RadRichTextBox_UI_For_Applying_Rich_Text_Formatting_Applying_Styles_07.png) diff --git a/controls/radrichtextbox/ui-for-applying-rich-text-formatting/features-radrichtextboxribbonui.md b/controls/radrichtextbox/ui-for-applying-rich-text-formatting/features-radrichtextboxribbonui.md index 304d58fd78..843d96f542 100644 --- a/controls/radrichtextbox/ui-for-applying-rich-text-formatting/features-radrichtextboxribbonui.md +++ b/controls/radrichtextbox/ui-for-applying-rich-text-formatting/features-radrichtextboxribbonui.md @@ -54,7 +54,7 @@ If you take a closer look at the generated code there are a few things that must >You can take a look at the XAML that is generated by following the steps in this topic in the [Telerik Editor](https://github.com/telerik/xaml-sdk/tree/master/RichTextBox/TelerikEditor) SDK example. ->tipTo learn more about the commands exposed by the __RadRichTextBox__ and how to use them read [here]({%slug radrichtextbox-features-commands%}). +>tip To learn more about the commands exposed by the __RadRichTextBox__ and how to use them read [here]({%slug radrichtextbox-features-commands%}). By knowing that the UI is connected to the __RadRichTextBox__ via its __DataContext__, you can easily implement a scenario where you have more than one __RadRichTextBox__ controls ruled by one UI. You just have to change the __DataContext__ of the UI depending on which __RadRichTextBox__ is active. An example implementation of this scenario is available in our SDK repository: [ChangeRibbonUIDataContext](https://github.com/telerik/xaml-sdk/tree/master/RichTextBox/ChangeRibbonUIDataContext) diff --git a/controls/radrichtextbox/ui-for-applying-rich-text-formatting/ui-for-applying-formatting-table-styles-gallery.md b/controls/radrichtextbox/ui-for-applying-rich-text-formatting/ui-for-applying-formatting-table-styles-gallery.md index 56eaf55c06..a3e9f9f5b3 100644 --- a/controls/radrichtextbox/ui-for-applying-rich-text-formatting/ui-for-applying-formatting-table-styles-gallery.md +++ b/controls/radrichtextbox/ui-for-applying-rich-text-formatting/ui-for-applying-formatting-table-styles-gallery.md @@ -35,7 +35,7 @@ In order to take advantage of the TableStylesGallery you have to add references * Telerik.Windows.Controls.RichTextBoxUI ->tipAll pop-ups that RadRichTextBox uses (context menu, dialogs, etc.) as well as all controls used in [RadRichTextBoxRibbonUI]({%slug radrichtextbox-features-radrichtextboxribbonui%}) are located in the Telerik.Windows.Controls.RichTextBoxUI assembly. However, you can use the TableStylesGallery alone without the whole predefined ribbon. +>tip All pop-ups that RadRichTextBox uses (context menu, dialogs, etc.) as well as all controls used in [RadRichTextBoxRibbonUI]({%slug radrichtextbox-features-radrichtextboxribbonui%}) are located in the Telerik.Windows.Controls.RichTextBoxUI assembly. However, you can use the TableStylesGallery alone without the whole predefined ribbon. The below snippet is an example of TableStylesGallery: diff --git a/controls/radscheduleview/events/overview.md b/controls/radscheduleview/events/overview.md index 396dcee7ea..92883cf5a0 100644 --- a/controls/radscheduleview/events/overview.md +++ b/controls/radscheduleview/events/overview.md @@ -16,9 +16,9 @@ __RadScheduleView__ provides a couple of useful events that can be used for cust Event naming convention is the standard naming convention for data manipulation events similar to web and windows programming. Every operation has a before event (ending with -__ing__) and after event (ending with -__ed__). An example of these are __AppointmentDeleting__ and __AppointmentDeleted__ event of __RadScheduleView__. ->tipAll __event arguments__ of the before operation events (ending with -ing) derive from the __CancelRoutedEventArgs__ class. That's why all of the before operation events (ending with -__ing__) can be canceled by setting event arguments' __Cancel__ property to __True__. +>tip All __event arguments__ of the before operation events (ending with -ing) derive from the __CancelRoutedEventArgs__ class. That's why all of the before operation events (ending with -__ing__) can be canceled by setting event arguments' __Cancel__ property to __True__. ->tipAll event arguments of the after operation events (ending with -ed) derive directly from the __RadRoutedEventArgs__ class. +>tip All event arguments of the after operation events (ending with -ed) derive directly from the __RadRoutedEventArgs__ class. ## Data Events diff --git a/controls/radscheduleview/features/appointments/custom-appointment.md b/controls/radscheduleview/features/appointments/custom-appointment.md index bacdcd76ea..b4dd23fd74 100644 --- a/controls/radscheduleview/features/appointments/custom-appointment.md +++ b/controls/radscheduleview/features/appointments/custom-appointment.md @@ -26,7 +26,7 @@ To create a custom appointment class you can start off with either of the follow Let's create a simple task tracking system. For our Custom Appointment class we will inherit from __Appointment__. Our tracking system will need to show an additional field for the task progress – an indication of whether the task has finished or not. In order to enable editing in transactions of the new property we need to use the __Storage__ method of the __AppointmentBase__ class to access the instance which owns the fields. We will name our custom appointment class __Task.__ __Example 1__ shows the creation of the Custom Appointment class: ->importantWhen inheriting the AppointmentBase class it is required to create a parameter-less constructor for the the custom class. +>important When inheriting the AppointmentBase class it is required to create a parameter-less constructor for the the custom class. __Example 1: Create Custom Appointment__ @@ -176,7 +176,7 @@ __Example 3: Bind the IsDone property__ #### __Figure 2: Result from Example 3__ ![RadScheduleView with custom EditAppointmentDialogStyle](images/custom_appointment2.PNG) ->tipThe important thing to note here is that we can bind to our new properties using __Occurrence.Appointment__. +>tip The important thing to note here is that we can bind to our new properties using __Occurrence.Appointment__. ## Changing the Style of the AppointmentItem diff --git a/controls/radscheduleview/features/appointments/snapappointments.md b/controls/radscheduleview/features/appointments/snapappointments.md index 90f3f38ad8..527b6d16cc 100644 --- a/controls/radscheduleview/features/appointments/snapappointments.md +++ b/controls/radscheduleview/features/appointments/snapappointments.md @@ -42,7 +42,7 @@ And the result is: ![radscheduleview snapappointments 2](images/radscheduleview_snapappointments_2.png) ->tipYou can check [Configuring the TimeRuler ticks]({%slug radscheduleview-features-timeruler-ticks-configuration%}) article for more details about MinorTickLength property. +>tip You can check [Configuring the TimeRuler ticks]({%slug radscheduleview-features-timeruler-ticks-configuration%}) article for more details about MinorTickLength property. ## Customizing the SnapBehavior diff --git a/controls/radscheduleview/features/custom-dialogs.md b/controls/radscheduleview/features/custom-dialogs.md index 5963755e06..ee576e45a2 100644 --- a/controls/radscheduleview/features/custom-dialogs.md +++ b/controls/radscheduleview/features/custom-dialogs.md @@ -44,7 +44,7 @@ Other important properties of the AppointmentDialogViewModel class include: - IsReadOnly – a boolean property bound to the IsEnabled property of all the controls in the dialog. This allows to make the dialog read-only by cancelling the AppointmentEditing event of the ScheduleView – in this case the EditAppointmetDialog will be shown but all the fields will be disabled. ->tipCheck [here]({%slug radscheduleview-features-appointments-custom-appointment%}) for more details about customizing EditAppointmentDialog. +>tip Check [here]({%slug radscheduleview-features-appointments-custom-appointment%}) for more details about customizing EditAppointmentDialog. * EditRecurrenceDialog – shown when a recurrence is created or edited: @@ -53,7 +53,7 @@ Other important properties of the AppointmentDialogViewModel class include: __EditRecurrenceDialogStyle__ property is used to customize this dialog. The DataContext of the dialog is a RecurrenceDialogViewModel object. It provides information about the RecurrencePattern which is set to the RecurrenceRule of the appointment. ->tipMore information about the recurring patterns can be found [here]({%slug radscheduleview-features-recurrences-overview%}). +>tip More information about the recurring patterns can be found [here]({%slug radscheduleview-features-recurrences-overview%}). * DeleteAppointmentConfirmDialog - shown when the selected appointments are going to be deleted: diff --git a/controls/radscheduleview/features/inline-editing.md b/controls/radscheduleview/features/inline-editing.md index 6bdd827109..b9395f32a4 100644 --- a/controls/radscheduleview/features/inline-editing.md +++ b/controls/radscheduleview/features/inline-editing.md @@ -28,7 +28,7 @@ Inline editing lets you edit the appointment's subject right where you see it in ![radscheduleview inline editing 03](images/radscheduleview_inline_editing_03.png) ->tipPressing the __Enter__ key will apply your changes, while pressing the __Esc__ key will reject them. +>tip Pressing the __Enter__ key will apply your changes, while pressing the __Esc__ key will reject them. >It is important to know that if you edit an appointment which is result of recurrence, then the changes will be applied to the whole series. @@ -36,7 +36,7 @@ Inline editing lets you edit the appointment's subject right where you see it in The RadScheduleView exposes a property __IsInlineEditingEnabled__ which allows you to enable\disable the inline editing behavior. ->tipThe default value of the __IsInlineEditingEnabled__ property is True. Which means that the inline editing behavior is allowed by default. +>tip The default value of the __IsInlineEditingEnabled__ property is True. Which means that the inline editing behavior is allowed by default. If you want to disable the inline editing behavior, you should set the __IsInlineEditingEnabled__ property to False. diff --git a/controls/radscheduleview/features/recurrence/recurrences-draggingrecurrentappointment.md b/controls/radscheduleview/features/recurrence/recurrences-draggingrecurrentappointment.md index 638c3e60bd..e8e8ff0096 100644 --- a/controls/radscheduleview/features/recurrence/recurrences-draggingrecurrentappointment.md +++ b/controls/radscheduleview/features/recurrence/recurrences-draggingrecurrentappointment.md @@ -33,7 +33,7 @@ First, let’s have the following recurrent appointment added to the Appointment ); ``` ->tipYou could check [here]({%slug radscheduleview-features-recurrences-overview%}) for more details about recurrent appointments. +>tip You could check [here]({%slug radscheduleview-features-recurrences-overview%}) for more details about recurrent appointments. If the user drags and drops a single occurrence of this appointment: diff --git a/controls/radscheduleview/features/recurrence/recurrences-recurrencepattern.md b/controls/radscheduleview/features/recurrence/recurrences-recurrencepattern.md index 6febaf50ea..c0fedf2c86 100644 --- a/controls/radscheduleview/features/recurrence/recurrences-recurrencepattern.md +++ b/controls/radscheduleview/features/recurrence/recurrences-recurrencepattern.md @@ -91,7 +91,7 @@ If you want to set the __frequency__ of the recurrence, you need to set the __Re * __None__ __However, these values are invalid recurrence frequency and should not be used.__ ->tipThe default value of the __RecurrencePattern__'s __Frequency__ property is __RecurrenceFrequency.None__. Which means that the __Frequency__ property is a mandatory property and you should always set it. +>tip The default value of the __RecurrencePattern__'s __Frequency__ property is __RecurrenceFrequency.None__. Which means that the __Frequency__ property is a mandatory property and you should always set it. >Minutely and Hourly Frequency can be set only with code ( not from the EditAppointmentDialog). In order to display these options, you should [customize the EditAppointmentDialogStyle]({%slug radscheduleview-features-custom-dialogs%}) and add them in the template manually. @@ -129,23 +129,23 @@ When you want to set the days of the week of the recurrence, you need to set the * __None__ ->tipThe default value of the __RecurrencePattern__'s __DaysOfWeekMask__ property is __RecurrenceDays.None__. However, the __DaysOfWeekMask__ is not a mandatory property. +>tip The default value of the __RecurrencePattern__'s __DaysOfWeekMask__ property is __RecurrenceDays.None__. However, the __DaysOfWeekMask__ is not a mandatory property. ->tip__RecurrenceDays.WeekDays__ is equivalent to __RecurrenceDays.Monday | RecurrenceDays.Tuesday | RecurrenceDays.Wednesday | RecurrenceDays.Thursday | RecurrenceDays.Friday__. +>tip __RecurrenceDays.WeekDays__ is equivalent to __RecurrenceDays.Monday | RecurrenceDays.Tuesday | RecurrenceDays.Wednesday | RecurrenceDays.Thursday | RecurrenceDays.Friday__. ->tip__RecurrenceDays.WeekendDays__ is equivalent to __RecurrenceDays.Saturday | RecurrenceDays.Sunday.__ +>tip __RecurrenceDays.WeekendDays__ is equivalent to __RecurrenceDays.Saturday | RecurrenceDays.Sunday.__ ->tip__RecurrenceDays.EveryDay__ is equivalent to __RecurrenceDays.Monday | RecurrenceDays.Tuesday | RecurrenceDays.Wednesday | RecurrenceDays.Thursday | RecurrenceDays.Friday | RecurrenceDays.Saturday | RecurrenceDays.Sunday__. +>tip __RecurrenceDays.EveryDay__ is equivalent to __RecurrenceDays.Monday | RecurrenceDays.Tuesday | RecurrenceDays.Wednesday | RecurrenceDays.Thursday | RecurrenceDays.Friday | RecurrenceDays.Saturday | RecurrenceDays.Sunday__. ->tip__Enum__ members are often used in logical operation to create a combination of values. Often you should set more than one value of the __DaysOfWeekMask__ property, like in the [Example](#examples) section at the end of the topic. +>tip __Enum__ members are often used in logical operation to create a combination of values. Often you should set more than one value of the __DaysOfWeekMask__ property, like in the [Example](#examples) section at the end of the topic. ## Interval If you want to set the number of days between each recurrence, you need to specify the __RecurrencePattern__'s __Interval__ property. ->tipThe default value of the __RecurrencePattern__'s __Interval__ property is 1. +>tip The default value of the __RecurrencePattern__'s __Interval__ property is 1. ->tipCombining the __Interval__ property with the __DaysOfWeekMask__ and __Frequency__ pattern gives you even more flexibility when creating recurring appointments. For more information take a look at the [Example](#examples) section at the end of the topic. +>tip Combining the __Interval__ property with the __DaysOfWeekMask__ and __Frequency__ pattern gives you even more flexibility when creating recurring appointments. For more information take a look at the [Example](#examples) section at the end of the topic. ## DaysOfMonth @@ -290,9 +290,9 @@ The result of the above example will be a __RecurrencePattern__ which will creat ![RadScheduleView RecurrencePattern](images/radscheduleview_recurrencypattern_2.png) ->tipSometimes you may want to create an appointment that occurs during the __weekend__ days, instead of every __week__ day. The only thing you should change is to set the __DaysOfWeekMask__ property to __RecurrenceDays.WeekendDays__. +>tip Sometimes you may want to create an appointment that occurs during the __weekend__ days, instead of every __week__ day. The only thing you should change is to set the __DaysOfWeekMask__ property to __RecurrenceDays.WeekendDays__. ->tipIf you want to create an appointment that occurs every specific week day (Monday, Tuesday, etc.), you need only to set the correct value for the __DaysOfWeekMask__ property. For example, in order to create an appointment that occurs every Friday, set the __DaysOfWeekMask__ property to __RecurrenceDays.Friday__. +>tip If you want to create an appointment that occurs every specific week day (Monday, Tuesday, etc.), you need only to set the correct value for the __DaysOfWeekMask__ property. For example, in order to create an appointment that occurs every Friday, set the __DaysOfWeekMask__ property to __RecurrenceDays.Friday__. ## How to Create an Appointment that Occurs on Every n Days? @@ -327,7 +327,7 @@ Executing the previous pattern will result in creating an appointment that occur ![RadScheduleView RecurrencePattern](images/radscheduleview_recurrencypattern_3.png) ->tipIn this example, the key moment is setting the __Interval__ property. For example, if you want the number of days between each recurrence to be 4, 5, 6 or n days, then you just need to set the correct value to the __Interval__ property. +>tip In this example, the key moment is setting the __Interval__ property. For example, if you want the number of days between each recurrence to be 4, 5, 6 or n days, then you just need to set the correct value to the __Interval__ property. ## How to Create an Appointment that Occurs on Every "n-th" Day of the Month and the Interval Between Each Recurrence is "m" Months? diff --git a/controls/radscheduleview/features/recurrence/recurrences-recurrencerule.md b/controls/radscheduleview/features/recurrence/recurrences-recurrencerule.md index 9c3bb421a5..9eadb4d960 100644 --- a/controls/radscheduleview/features/recurrence/recurrences-recurrencerule.md +++ b/controls/radscheduleview/features/recurrence/recurrences-recurrencerule.md @@ -46,7 +46,7 @@ The __RecurrenceRule__ class exposes an __Exceptions__ property, which allows yo The __RecurrenceRule__ class has only one public constructor, which accepts a __RecurrencePattern__ as a parameter. ->tipThe __RecurrencePattern__ is a mandatory part of the __RecurrenceRule__. Which means that when creating a new __RecurrenceRule__ you must associate the rule with a recurrence pattern. +>tip The __RecurrencePattern__ is a mandatory part of the __RecurrenceRule__. Which means that when creating a new __RecurrenceRule__ you must associate the rule with a recurrence pattern. diff --git a/controls/radscheduleview/features/viewdefinitions/configure-visiblerange.md b/controls/radscheduleview/features/viewdefinitions/configure-visiblerange.md index f02e9963b5..7ba57fe716 100644 --- a/controls/radscheduleview/features/viewdefinitions/configure-visiblerange.md +++ b/controls/radscheduleview/features/viewdefinitions/configure-visiblerange.md @@ -21,7 +21,7 @@ TimelineViewDefinition | CurrentDate | 7 >The VisibleRangeEnd is VisibleRangeStart+VisibleDays for all view definitions. ->tipThe easiest way to create a WeekViewDefinition that behaves like the DayViewDefinition is to use a DayViewDefinition and set its VisibleDays=7. +>tip The easiest way to create a WeekViewDefinition that behaves like the DayViewDefinition is to use a DayViewDefinition and set its VisibleDays=7. For advanced customization of the VisibleRange the ViewDefinitionBase class provides two virtual methods: diff --git a/controls/radscheduleview/howto/update-resources.md b/controls/radscheduleview/howto/update-resources.md index bf61885859..b46749563e 100644 --- a/controls/radscheduleview/howto/update-resources.md +++ b/controls/radscheduleview/howto/update-resources.md @@ -155,7 +155,7 @@ So checking/unchecking the checkboxes will update the visible Resources in the V ![radscheduleview updateresources 3](images/radscheduleview_updateresources_3.png) ->tipYou can check this approach in RadScheduleView Grouping and Filtering demo {% if site.site_name == 'Silverlight' %}[here](https://demos.telerik.com/silverlight/#ScheduleView/Grouping/GroupingAndFiltering){% endif %}{% if site.site_name == 'WPF' %}[here](https://demos.telerik.com/wpf/){% endif %}. +>tip You can check this approach in RadScheduleView Grouping and Filtering demo {% if site.site_name == 'Silverlight' %}[here](https://demos.telerik.com/silverlight/#ScheduleView/Grouping/GroupingAndFiltering){% endif %}{% if site.site_name == 'WPF' %}[here](https://demos.telerik.com/wpf/){% endif %}. ## Adding/removing resources at run time diff --git a/controls/radscheduleview/styles-and-templates/appointment-style.md b/controls/radscheduleview/styles-and-templates/appointment-style.md index a2c2648d97..07c94cb973 100644 --- a/controls/radscheduleview/styles-and-templates/appointment-style.md +++ b/controls/radscheduleview/styles-and-templates/appointment-style.md @@ -60,11 +60,11 @@ __Example 2: Defining the local namespace__ xmlns:local="clr-namespace:Telerik.Windows.Controls;assembly=Telerik.Windows.Controls.ScheduleView" ``` ->importantIf you are using the default OfficeBlack theme or you've set a different theme with StyleManager, you should copy all the referenced resources from the RadScheduleView XAML file into your project. If you are using [Implicit Styles]({%slug styling-apperance-implicit-styles-overview%}) and merge the ResourceDictionaries, you will be able to reference the needed resources directly. +>important If you are using the default OfficeBlack theme or you've set a different theme with StyleManager, you should copy all the referenced resources from the RadScheduleView XAML file into your project. If you are using [Implicit Styles]({%slug styling-apperance-implicit-styles-overview%}) and merge the ResourceDictionaries, you will be able to reference the needed resources directly. Note that you have both __HorizontalStyle__ and __VerticalStyle__. RadScheduleView supports __Orientation__ for all its view definitions. Therefore a HorizontalStyle is applied when the appointment is horizontally oriented, while the VerticalStyle is applied when the appointment is vertically oriented. ->tipWhen making changes to the generated AppointmentStyleSelector, you should apply those changes to both the HorizontalStyle and the VerticalStyle in order for your appointments to look consistent in all views. +>tip When making changes to the generated AppointmentStyleSelector, you should apply those changes to both the HorizontalStyle and the VerticalStyle in order for your appointments to look consistent in all views. So, let's for example modify the background color and style of the appointments: @@ -169,7 +169,7 @@ __Example 5: Custom AppointmentStyleSelector__ } ``` ->tipNote that you need to ensure that both horizontal and vertical cases have their corresponding styles - __horizontal styles__ are applied when the appointments have horizontal orientation (either by default or when the view they are placed in has been explicitly set a horizontal orientation), __vertical styles__ are applied when the appointments have vertical orientation(either by default or when the view they are placed in has been explicitly set a vertical orientation). +>tip Note that you need to ensure that both horizontal and vertical cases have their corresponding styles - __horizontal styles__ are applied when the appointments have horizontal orientation (either by default or when the view they are placed in has been explicitly set a horizontal orientation), __vertical styles__ are applied when the appointments have vertical orientation(either by default or when the view they are placed in has been explicitly set a vertical orientation). We add all needed Resources and group our ScheduleView by the "Room" ResourceType: diff --git a/controls/radscheduleview/styles-and-templates/customizing-dragvisual.md b/controls/radscheduleview/styles-and-templates/customizing-dragvisual.md index 250d6dde95..ca605034ca 100644 --- a/controls/radscheduleview/styles-and-templates/customizing-dragvisual.md +++ b/controls/radscheduleview/styles-and-templates/customizing-dragvisual.md @@ -109,7 +109,7 @@ There are two approaches for customizing the DragVisualStyle according to the wa >The complete definition of the DragVisualStyle can be found in UI for {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %} installation folder in Themes.Impicit folder. Select the theme that you’re using and open Telerik.Windows.Controls.ScheduleView.xaml. Then search for “DragVisualStyle” in this XAML file. ->importantYou should reference the Telerik NoXaml assemblies when using implicit styles. +>important You should reference the Telerik NoXaml assemblies when using implicit styles. * In case you’re using the default OfficeBlack theme or you've set a different theme with StyleManager:You should extract the complete DragVisualStyle from the RadScheduleView XAML file. The needed XAML file can be found in the UI for {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %}s installation folder. Go into the Themes folder and select the theme that you have chosen to use. Drill down to find the Telerik.Windows.Controls.ScheduleView.xaml file in the directory that corresponds to your theme. From this resource dictionary extract the DragVisualStyle and all the resources it uses, such as brushes and styles, into your own project. Then you will be able to make the needed customizations, for example: diff --git a/controls/radscheduleview/styles-and-templates/styling-timeruleritems.md b/controls/radscheduleview/styles-and-templates/styling-timeruleritems.md index 078c0fdeca..36a385ad78 100644 --- a/controls/radscheduleview/styles-and-templates/styling-timeruleritems.md +++ b/controls/radscheduleview/styles-and-templates/styling-timeruleritems.md @@ -276,7 +276,7 @@ To create a custom TimeRulerItemStyleSelector, inherit the __OrientedTimeRulerIt End Class ``` ->tipIf you need to take advantage of the __activeViewDefinition__ in the body of the SelectStyle method, it is important to inherit the __OrientedTimeRulerItemStyleSelector__, which is located in __Telerik.Windows.Controls__ namespace, rather than the regular StyleSelector class. +>tip If you need to take advantage of the __activeViewDefinition__ in the body of the SelectStyle method, it is important to inherit the __OrientedTimeRulerItemStyleSelector__, which is located in __Telerik.Windows.Controls__ namespace, rather than the regular StyleSelector class. We use the __Type__ property of the __TickData__ class to determine whether the item is a major or a minor tick. Other properties of the TickData class include: __DateData__, __DateTime__, __Duration__ and __Offset__. diff --git a/controls/radscheduleview/styles-and-templates/templating-timeruleritems.md b/controls/radscheduleview/styles-and-templates/templating-timeruleritems.md index 291950dab5..6cfa1e07d1 100644 --- a/controls/radscheduleview/styles-and-templates/templating-timeruleritems.md +++ b/controls/radscheduleview/styles-and-templates/templating-timeruleritems.md @@ -41,7 +41,7 @@ The next figures show the templates in the different ViewDefinitions of __RadSch #### __Figure 7: TimeRulerItems templates in MonthViewDefinition__ ![{{ site.framework_name }} RadScheduleView TimeRulerItems templates in MonthViewDefinition](images/radscheduleview_templating_timeruleritems_07.png) ->tipMinor tick templates are by design empty. This could be easily changed by assigning a StringFormat through the [Formatting properties]({%slug radscheduleview-features-formatting%}) of the ViewDefinitions. +>tip Minor tick templates are by design empty. This could be easily changed by assigning a StringFormat through the [Formatting properties]({%slug radscheduleview-features-formatting%}) of the ViewDefinitions. Example 1 shows how to configure DayViewDefinition and the corresponding VerticalDayMajorItem and VerticalDayMinorItem templates in order to achieve a more detailed view of the TimeRuler. diff --git a/controls/radscheduleview/styles-and-templates/templating-tooltip.md b/controls/radscheduleview/styles-and-templates/templating-tooltip.md index bcd1dcff9c..c169c98e50 100644 --- a/controls/radscheduleview/styles-and-templates/templating-tooltip.md +++ b/controls/radscheduleview/styles-and-templates/templating-tooltip.md @@ -77,7 +77,7 @@ And you want to replace the default ToolTip with custom one which shows the full >Note that the ToolTip receives object of type AppointmentItemProxy as a DataContext which contains the actual Appointment. You can easily bind to its properties like shown above. ->importantIf you are using a custom Appointment with custom properties you won't be able to bind directly to them. You should access them through the Appointment property of the AppointmentItemProxy object the following way: Appointment.*CustomProperty*. +>important If you are using a custom Appointment with custom properties you won't be able to bind directly to them. You should access them through the Appointment property of the AppointmentItemProxy object the following way: Appointment.*CustomProperty*. Aftewards you just need to set the DataTemplate as a __ToolTipTemplate__ the following way: diff --git a/controls/radslider/features/multiple-thumbs.md b/controls/radslider/features/multiple-thumbs.md index c3fe559da2..b2e0594cf1 100644 --- a/controls/radslider/features/multiple-thumbs.md +++ b/controls/radslider/features/multiple-thumbs.md @@ -111,7 +111,7 @@ __Example 2: Styling the thumbs individually__ ``` ->importantPlease note that when using the [StyleManager theming approach]({%slug common-styling-apperance-setting-theme-wpf%}) you need to also define the **Height** for the middle thumb. This has been demonstrated in the following [knowledge base article]({%slug kb-slider-style-middle-thumb-style-manager%}). +>important Please note that when using the [StyleManager theming approach]({%slug common-styling-apperance-setting-theme-wpf%}) you need to also define the **Height** for the middle thumb. This has been demonstrated in the following [knowledge base article]({%slug kb-slider-style-middle-thumb-style-manager%}). Alternatively, you can set the ThumbStyle, **SelectionMiddleThumbStyle** and AlternateThumbStyle properties on the RadSlider control itself and they will be passed onto all thumbs from the **Thumbs** collection. diff --git a/controls/radspellchecker/features/spellchecking-gridcell.md b/controls/radspellchecker/features/spellchecking-gridcell.md index b95fba4931..cbb3bf206f 100644 --- a/controls/radspellchecker/features/spellchecking-gridcell.md +++ b/controls/radspellchecker/features/spellchecking-gridcell.md @@ -10,7 +10,7 @@ position: 1 # SpellChecking GridCell ->tipFor a quick review of the basics you can take a look at the [Getting Started]({%slug radspellchecker-getting-started%}) topic. +>tip For a quick review of the basics you can take a look at the [Getting Started]({%slug radspellchecker-getting-started%}) topic. Basically, there are two ways to spellcheck a grid cell: diff --git a/controls/radspellchecker/getting-started.md b/controls/radspellchecker/getting-started.md index 533cf6f7ee..376a5d46a8 100644 --- a/controls/radspellchecker/getting-started.md +++ b/controls/radspellchecker/getting-started.md @@ -12,7 +12,7 @@ position: 1 __RadSpellChecker__ is a control that allows you to spellcheck a number of controls including __TextBox__, __RichTextBox__, __RadRichTextBox__, __RadGridView__, __DataGrid__ or any other control that complies with certain requirements. ->tip__RadRichTextBox__ has a built-in spell checker (RadDocumentSpellChecker) that provides similar functionality and the benefit of underlining the incorrect words with a red curly line. If you would like to use __RadSpellChecker__ instead of the default spell checker you should disable the document spell checker by setting the property __IsSpellCheckingEnabled__ = ”False”. This can be done, for example, in order to create a similar look of the RadRichTextBoxes and the TextBoxes in your application. +>tip __RadRichTextBox__ has a built-in spell checker (RadDocumentSpellChecker) that provides similar functionality and the benefit of underlining the incorrect words with a red curly line. If you would like to use __RadSpellChecker__ instead of the default spell checker you should disable the document spell checker by setting the property __IsSpellCheckingEnabled__ = ”False”. This can be done, for example, in order to create a similar look of the RadRichTextBoxes and the TextBoxes in your application. ## Adding Telerik Assemblies Using NuGet diff --git a/controls/radspreadsheet/features/ui-data-validation.md b/controls/radspreadsheet/features/ui-data-validation.md index bebebf1599..1546a1339e 100644 --- a/controls/radspreadsheet/features/ui-data-validation.md +++ b/controls/radspreadsheet/features/ui-data-validation.md @@ -22,7 +22,7 @@ You can easily set data validation rules using the data validation dialog which ![Rad Spreadsheet UI Data Validation 01](images/RadSpreadsheet_UI_Data_Validation_01.png) ->tipDetailed information on the different validation rules is available in the [Data Validation for SpreadProcessing article](https://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/features/data-validation). +>tip Detailed information on the different validation rules is available in the [Data Validation for SpreadProcessing article](https://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/features/data-validation). The dialog contains two other tabs - one allowing to customize the input message that is shown when the cell is selected, and one allowing to change the alert shown when there is an error in the cell. diff --git a/controls/radspreadsheet/features/ui-hidden-rows-columns.md b/controls/radspreadsheet/features/ui-hidden-rows-columns.md index b57cd83761..cebb5a864f 100644 --- a/controls/radspreadsheet/features/ui-hidden-rows-columns.md +++ b/controls/radspreadsheet/features/ui-hidden-rows-columns.md @@ -42,7 +42,7 @@ Another option which will automatically hide a row or a column is to set its siz ![Rad Spreadsheet UI Hidden Rows and Columns 03](images/RadSpreadsheet_UI_Hidden_Rows_Columns_03.png) ->tipPlease, note that this behavior is different from the behavior of the [model](https://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/working-with-rows-and-columns/hidden-rows-columns) where setting the size of the rows and columns will not affect their hidden state. +>tip Please, note that this behavior is different from the behavior of the [model](https://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/working-with-rows-and-columns/hidden-rows-columns) where setting the size of the rows and columns will not affect their hidden state. ## Unhiding @@ -60,7 +60,7 @@ Following this, the ribbon and context menu options items can be used. Similarly to hiding rows and columns, you can unhide them by dragging the thumb which has appeared on the place of their heading. In addition, you can also apply auto fit to them. This is done by double-clicking the thumb. ->tipThe autofit behavior of the columns is different from the behavior of the columns. An empty column will not expand when autofitted, unlike an empty row. +>tip The autofit behavior of the columns is different from the behavior of the columns. An empty column will not expand when autofitted, unlike an empty row. ## See Also diff --git a/controls/radspreadsheet/features/ui-worksheet-editor-context-menu.md b/controls/radspreadsheet/features/ui-worksheet-editor-context-menu.md index 886c1e3a30..dda6faa4b1 100644 --- a/controls/radspreadsheet/features/ui-worksheet-editor-context-menu.md +++ b/controls/radspreadsheet/features/ui-worksheet-editor-context-menu.md @@ -15,7 +15,7 @@ position: 1 By default the WorksheetEditor of RadSpreadsheet does not have a context menu. However, the control exposes a __WorksheetEditorContextMenu__ property of type __RadContextMenu__ that allows you to plug and arrange easily a context menu. This article demonstrates how to assign the editor a menu using XAML. ->tipRadContextMenu is a flexible control that aims to provide additional commands and features. You will be able to find more information regarding RadContextMenu in the section of our online documentation dedicated to the control [here]({%slug contextmenu-overview1%}). +>tip RadContextMenu is a flexible control that aims to provide additional commands and features. You will be able to find more information regarding RadContextMenu in the section of our online documentation dedicated to the control [here]({%slug contextmenu-overview1%}). ## Set Worksheet Editor's Context Menu @@ -25,5 +25,5 @@ You can find an example of this in our SDK repository [here](https://github.com/ Note that the code defines a RadSpreadsheet instance with DataContext set to the CommandDescriptors property. This is necessary since the items of the menu use the commands exposed by the current set of command descriptors of RadSpreadsheet. Also, several of the bindings use a BoolToVisibilityValueConverter. This is required since some of the commands offered in the menu are not available all of the time. For example, changing the active cell mode to edit mode replaces the set of command descriptors and some of the new descriptors are disabled while the active editor is opened. Using the BoolToVisibilityValueConverter ensures that only the items for enabled descriptors will be visible. In this particular scenario, if the user opens a context menu when the editor is in edit mode, the insert, delete, format cells and hyperlink are not visible. ->tipYou can download a runnable project of the previous example from our online SDK repository [here](https://github.com/telerik/xaml-sdk), the example is listed as __Spreadsheet / WorksheetEditorContextMenu__. +>tip You can download a runnable project of the previous example from our online SDK repository [here](https://github.com/telerik/xaml-sdk), the example is listed as __Spreadsheet / WorksheetEditorContextMenu__. diff --git a/controls/radspreadsheet/howto/switching-icons-at-runtime.md b/controls/radspreadsheet/howto/switching-icons-at-runtime.md index 650c34104a..075a6dcfb2 100644 --- a/controls/radspreadsheet/howto/switching-icons-at-runtime.md +++ b/controls/radspreadsheet/howto/switching-icons-at-runtime.md @@ -27,7 +27,7 @@ __Example 1: Creating IconSources__ ``` ->tipTo browse all icons you can download the source code of the controls from your Telerik account. The images are located at {%if site.site_name == 'WPF' %}\Telerik\_UI\_for\_WPF\_Source\_[Version]\Controls\Spreadsheet\Controls\Images\Light.{%endif%} {%if site.site_name == 'Silverlight' %} \Telerik\_UI\_for\_Silverlight\_Source\_[Version]\Controls\Spreadsheet\Controls\Images\Light.{%endif%} +>tip To browse all icons you can download the source code of the controls from your Telerik account. The images are located at {%if site.site_name == 'WPF' %}\Telerik\_UI\_for\_WPF\_Source\_[Version]\Controls\Spreadsheet\Controls\Images\Light.{%endif%} {%if site.site_name == 'Silverlight' %} \Telerik\_UI\_for\_Silverlight\_Source\_[Version]\Controls\Spreadsheet\Controls\Images\Light.{%endif%} ## See Also diff --git a/controls/radspreadsheet/localization.md b/controls/radspreadsheet/localization.md index 00ca0c6268..6e3e03a02e 100644 --- a/controls/radspreadsheet/localization.md +++ b/controls/radspreadsheet/localization.md @@ -52,7 +52,7 @@ RadSpreadsheet is a complex control and its strings for localization are numerou The three files should keep the same resource keys, whereas the values must be the translated ones. ->tipIt is easiest to copy the default __RadSpreadsheetResources.resx__ file and rename it. Afterwards, go through all string and change only the Values for the strings that will be used in your application. +>tip It is easiest to copy the default __RadSpreadsheetResources.resx__ file and rename it. Afterwards, go through all string and change only the Values for the strings that will be used in your application. The last step is to instantiate the __LocalizationManager__ class and set its __ResourceManager__ to the resources that have been just created. diff --git a/controls/radspreadsheet/model.md b/controls/radspreadsheet/model.md index 1019eb5d12..8b5ba73b18 100644 --- a/controls/radspreadsheet/model.md +++ b/controls/radspreadsheet/model.md @@ -10,7 +10,7 @@ position: 5 # Model ->important__RadSpreadsheet__ operates with a rich document model that is completely decoupled from UI. The documentation of the model can be found in the RadSpreadProcessing section of the documentation for Telerik Document Processing [here](https://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/overview). +>important __RadSpreadsheet__ operates with a rich document model that is completely decoupled from UI. The documentation of the model can be found in the RadSpreadProcessing section of the documentation for Telerik Document Processing [here](https://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/overview). The primary document that the model uses to manipulate and store data is called a __workbook__. Each __workbook__ contains at least one __worksheet__ that is defined as a collection of cells organized in rows and columns. A __worksheet__ can also be viewed as a tabular working surface that you use to enter and organize your data. Typically, a single __workbook__ holds together several __worksheets__ that contain related information. For example, a workbook named *Annual Budget* can contain four worksheets that split the data for each quarter. diff --git a/controls/radspreadsheet/overview.md b/controls/radspreadsheet/overview.md index 4e094effd5..c05738b1c4 100644 --- a/controls/radspreadsheet/overview.md +++ b/controls/radspreadsheet/overview.md @@ -22,7 +22,7 @@ __RadSpreadsheet__ is a control that allows editing tabular data utilizing a var ![Rad Spreadsheet Overview ](images/RadSpreadsheet_Overview.png) ->important__RadSpreadsheet__ operates with a rich document model that is completely decoupled from UI. The documentation of the model can be found in the RadSpreadProcessing section of the documentation for Telerik Document Processing [here](https://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/overview). +>important __RadSpreadsheet__ operates with a rich document model that is completely decoupled from UI. The documentation of the model can be found in the RadSpreadProcessing section of the documentation for Telerik Document Processing [here](https://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/overview). ## Features diff --git a/controls/radspreadsheet/ui-virtualization.md b/controls/radspreadsheet/ui-virtualization.md index 6d2a64bc3f..098c300dc3 100644 --- a/controls/radspreadsheet/ui-virtualization.md +++ b/controls/radspreadsheet/ui-virtualization.md @@ -12,7 +12,7 @@ position: 9 __RadSpreadsheet__ supports __UI Virtualization__ (enabled by default), which enables it to processes only information that is loaded in the viewable area. In this way, UI elements are created only for the parts of the document actually shown on screen. This reduces the memory footprint of the application and speeds up the loading time, thus additionally enhancing the UI performance. ->importantTry not to place RadSpreadsheet in controls/panels which will measure it with infinity. For example, __ScrollViewer__, __StackPanel__ and Grid with __Row.Height="Auto"__ or __Column.Width="Auto"__ will measure with infinity. In these cases, RadSpreadsheet is measured with infinity and cannot determine what part of the document is shown in the viewport, therefore the virtualization turns off. +>important Try not to place RadSpreadsheet in controls/panels which will measure it with infinity. For example, __ScrollViewer__, __StackPanel__ and Grid with __Row.Height="Auto"__ or __Column.Width="Auto"__ will measure with infinity. In these cases, RadSpreadsheet is measured with infinity and cannot determine what part of the document is shown in the viewport, therefore the virtualization turns off. ## See Also diff --git a/controls/radtabbedwindow/styles-and-templates.md b/controls/radtabbedwindow/styles-and-templates.md index a10552562a..4edbfd8b54 100644 --- a/controls/radtabbedwindow/styles-and-templates.md +++ b/controls/radtabbedwindow/styles-and-templates.md @@ -27,7 +27,7 @@ Via the **AddButtonStyle** property, you can control the appearance of the butto ``` ->importantIf you are using the default Office_Black theme (you have not merged a theme assembly) or you've set a different theme with the [StyleManager]({%slug styling-apperance-implicit-styles-overview%}), you should copy the **AddItemsButtonStyle** and all the referenced resources from the **Telerik.Windows.Controls.Navigation.xaml** file into your project. +>important If you are using the default Office_Black theme (you have not merged a theme assembly) or you've set a different theme with the [StyleManager]({%slug styling-apperance-implicit-styles-overview%}), you should copy the **AddItemsButtonStyle** and all the referenced resources from the **Telerik.Windows.Controls.Navigation.xaml** file into your project. ## ItemContainerStyle @@ -47,7 +47,7 @@ You can use the **ItemContainerStyle** property to style the individual RadTabIt ``` ->importantIf you are using the default Office_Black theme (you have not merged a theme assembly) or you've set a different theme with the [StyleManager]({%slug styling-apperance-implicit-styles-overview%}), you should copy the **RadTabbedWindowTabItemStyle** and all the referenced resources from the **Telerik.Windows.Controls.Navigation.xaml** file into your project. +>important If you are using the default Office_Black theme (you have not merged a theme assembly) or you've set a different theme with the [StyleManager]({%slug styling-apperance-implicit-styles-overview%}), you should copy the **RadTabbedWindowTabItemStyle** and all the referenced resources from the **Telerik.Windows.Controls.Navigation.xaml** file into your project. ## ItemContainerStyleSelector @@ -114,7 +114,7 @@ You can also define a **StyleSelector** and conditionally style the tab items vi ``` ->importantPlease note that to use the ItemContainerStyleSelector property, you need to clear the ItemContainerStyle by setting it to **null**. +>important Please note that to use the ItemContainerStyleSelector property, you need to clear the ItemContainerStyle by setting it to **null**. ## ItemTemplate and ItemTemplateSelector diff --git a/controls/radtabcontrol/features/keyboard-support.md b/controls/radtabcontrol/features/keyboard-support.md index ac8ea90295..ff46bcae47 100644 --- a/controls/radtabcontrol/features/keyboard-support.md +++ b/controls/radtabcontrol/features/keyboard-support.md @@ -24,7 +24,7 @@ Set the __IsTabStop__ property to include/exclude the control in the tab navigat * __KeyUp__– get notified when the user has released a keyboard key. ->tipTo obtain the pressed key, the object that raised the event or some other information, use the instance of __System.Windows.Input.KeyEventArgs__ passed as a parameter to the event handler method. +>tip To obtain the pressed key, the object that raised the event or some other information, use the instance of __System.Windows.Input.KeyEventArgs__ passed as a parameter to the event handler method. ```XAML diff --git a/controls/radtabcontrol/getting-started/populating-with-tabs.md b/controls/radtabcontrol/getting-started/populating-with-tabs.md index d701af280c..ce96287ce5 100644 --- a/controls/radtabcontrol/getting-started/populating-with-tabs.md +++ b/controls/radtabcontrol/getting-started/populating-with-tabs.md @@ -27,7 +27,7 @@ There are several ways to populate a tab control with tab items and they are: Each one of the approaches described above is applicable for certain cases and that’s why you have to choose the one that best fits your requirements. ->tipBear in mind that the XAML file is the best place to declare your user interface; use the code-behind only when you cannot do that in XAML. +>tip Bear in mind that the XAML file is the best place to declare your user interface; use the code-behind only when you cannot do that in XAML. ## See Also diff --git a/controls/radtabcontrol/populating-with-tabs/populating-add-remove-tabs.md b/controls/radtabcontrol/populating-with-tabs/populating-add-remove-tabs.md index 5042d49238..36eddc2a64 100644 --- a/controls/radtabcontrol/populating-with-tabs/populating-add-remove-tabs.md +++ b/controls/radtabcontrol/populating-with-tabs/populating-add-remove-tabs.md @@ -70,7 +70,7 @@ Each one of the __RadTabItem__ nodes in the example above represents declaration For example insert the following line ____ after the "Web Sites" tab item and new tab item will be added to the tab control. ![{{ site.framework_name }} RadTabControl Add New Tab Declaratively](images/RadTabControl_Figure_00250.png) ->tipConsider declaring tabs in XAML instead of adding them by code whenever it’s possible. This includes situations when you know what tabs you need at design time.Declaring tabs in XAML is also a preferable choice when you are working with a designer that will style the control using Expression Blend. +>tip Consider declaring tabs in XAML instead of adding them by code whenever it’s possible. This includes situations when you know what tabs you need at design time.Declaring tabs in XAML is also a preferable choice when you are working with a designer that will style the control using Expression Blend. ## See Also diff --git a/controls/radtilelist/features/selection.md b/controls/radtilelist/features/selection.md index b577da5b02..5099f1fa0d 100644 --- a/controls/radtilelist/features/selection.md +++ b/controls/radtilelist/features/selection.md @@ -47,7 +47,7 @@ The __SelectedItem__ property corresponds to the item the user has clicked or ta __SelectedItems__ is a collection of items containing all selected items in the control when SelectionMode is set to Multiple or Extended. ->importantThe __SelectedItems__ collection will remain empty when SelectionMode is set to Single and you change the selected item. However, when in Multiple or Extended selection mode, __SelectedItem__ will be set to the last item added to the selected items that is still included in the selection. +>important The __SelectedItems__ collection will remain empty when SelectionMode is set to Single and you change the selected item. However, when in Multiple or Extended selection mode, __SelectedItem__ will be set to the last item added to the selected items that is still included in the selection. ## Reacting to changes in the selection diff --git a/controls/radtimeline/features/intervals-formatters.md b/controls/radtimeline/features/intervals-formatters.md index 06e2c4af03..7e2f150ce7 100644 --- a/controls/radtimeline/features/intervals-formatters.md +++ b/controls/radtimeline/features/intervals-formatters.md @@ -167,4 +167,4 @@ The table shows the available formatters per Interval: ->tipYou can customize the interval formats through the [FormatterProvider]({%slug radtimeline-features-formatter-provider%}). \ No newline at end of file +>tip You can customize the interval formats through the [FormatterProvider]({%slug radtimeline-features-formatter-provider%}). \ No newline at end of file diff --git a/controls/radtransitioncontrol/features/radtransition-data-binding.md b/controls/radtransitioncontrol/features/radtransition-data-binding.md index 9526c2a435..9a3df64acb 100644 --- a/controls/radtransitioncontrol/features/radtransition-data-binding.md +++ b/controls/radtransitioncontrol/features/radtransition-data-binding.md @@ -53,7 +53,7 @@ You can also bind the __RadTransitionControl__ to another __Control__ in your __ In this case the data item representing the __SelectedItem__ is the __DataContext__ of the __ControlTemplate__. ->tipIn the [Getting Started]({%slug radtransition-getting-started%}) topic you can find an example of a __RadTransitionControl__ bound to a __ListBox__, which lists photos. +>tip In the [Getting Started]({%slug radtransition-getting-started%}) topic you can find an example of a __RadTransitionControl__ bound to a __ListBox__, which lists photos. ## See Also diff --git a/controls/radtransitioncontrol/features/radtransition-integration-with-content-controls.md b/controls/radtransitioncontrol/features/radtransition-integration-with-content-controls.md index 56c67c925b..55ee1eeeec 100644 --- a/controls/radtransitioncontrol/features/radtransition-integration-with-content-controls.md +++ b/controls/radtransitioncontrol/features/radtransition-integration-with-content-controls.md @@ -12,7 +12,7 @@ position: 4 The __RadTransitionControl__ can be easily integrated in other more complex __ContentControls__ in order to extend their functionality. For example - __ScrollViewer__, __HeaderedContentControl__ etc. ->tipYou can also integrate the __RadTransitionControl__ in any control that somehow visualizes content. +>tip You can also integrate the __RadTransitionControl__ in any control that somehow visualizes content. To integrate a __RadTransitionControl__ with a more complex __ContentControl__, you have to replace the __ContentControl__ or the __ContentPresenter__ of the latter one __ControlTemplate__ with an instance of the __RadTransitionControl__ and to configure the __TemplateBindings__ for the __Content__ and the __ContentTemplate__ properties. @@ -121,7 +121,7 @@ The first __ContentPresenter__ is responsible for the header and the second one Next, configure the __RadTransitionControl__ to match your needs. For example, define its __Transition__. ->tipTo learn more about working with the __RadTransitionControl__ read [this topic]({%slug radtransition-features-working-with-radtransitioncontrol%}). To learn more about transition effects read the [Transitions]({%slug radtransition-features-transitions%}) topic. +>tip To learn more about working with the __RadTransitionControl__ read [this topic]({%slug radtransition-features-working-with-radtransitioncontrol%}). To learn more about transition effects read the [Transitions]({%slug radtransition-features-transitions%}) topic. >In order to use the built-in __transition effects__ you have to add the following namespace to your __UserControl__: > xmlns:telerikTransitions="clr-namespace:Telerik.Windows.Controls.TransitionEffects;assembly=Telerik.Windows.Controls" diff --git a/controls/radtransitioncontrol/features/radtransition-transitions.md b/controls/radtransitioncontrol/features/radtransition-transitions.md index 79687a32dd..3eb21343f0 100644 --- a/controls/radtransitioncontrol/features/radtransition-transitions.md +++ b/controls/radtransitioncontrol/features/radtransition-transitions.md @@ -12,7 +12,7 @@ position: 1 The __RadTransitionControl__ applies a transition effect to its content when it gets changed. There are several built-in effects, but you are able to create your own via the __HLSL__ language. ->tipYou are also capable of specifying the transition [duration]({%slug radtransition-features-working-with-radtransitioncontrol%}#transition-duration) and [an animation easing function]({%slug radtransition-features-working-with-radtransitioncontrol%}#transition-easing). +>tip You are also capable of specifying the transition [duration]({%slug radtransition-features-working-with-radtransitioncontrol%}#transition-duration) and [an animation easing function]({%slug radtransition-features-working-with-radtransitioncontrol%}#transition-easing). ## Built-in Transition Effects @@ -121,7 +121,7 @@ The __MotionBlurredZoomTransition__ is basically a fade transition with motion b * __OutBlurRatio__ - specifies the ratio of the motion blur effect applied to the old content. The default value is __-0.3__. A value of __0__ will neutralize the motion blur. A __negative value__ will direct the motion blur outside of the object and it will behave like it had been zoomed out. A motion blur with a __positive value__ will give the impression of zooming in. ->tipSetting the __InBlurRatio__ and the __OutBlurRatio__ to 0 will make the __MotionBlurredZoomTransition__ behave like a normal __FadeTransition__. +>tip Setting the __InBlurRatio__ and the __OutBlurRatio__ to 0 will make the __MotionBlurredZoomTransition__ behave like a normal __FadeTransition__. * __Samples__ - for each pixel in point __P__ it creates a line that contains that point and the __Center__ point. Then __Samples__ count of points are selected from the new content and Samples count of points of the old content are selected forming two sets of points for the old and the new values. The distance of the selected points to the __P__ depends on __InBlurRatio__ and __OutBlurRatio__ and the __progress__ inverting the values for example from 0.3, -0.3 to -0.3, 0.3 will make the image to go zoom out instead of zoom in. The colors in the two sets of points are summed up and the average values of these two groups are selected as the old and the new color. The final pixel color for __P__ is the sum of these two values get with different weight depending on the __progress__. The default value is __7__. diff --git a/controls/radtransitioncontrol/features/radtransition-working-with-radtransitioncontrol.md b/controls/radtransitioncontrol/features/radtransition-working-with-radtransitioncontrol.md index 2beba0e805..8dfb352a10 100644 --- a/controls/radtransitioncontrol/features/radtransition-working-with-radtransitioncontrol.md +++ b/controls/radtransitioncontrol/features/radtransition-working-with-radtransitioncontrol.md @@ -12,7 +12,7 @@ position: 0 Tha __RadTransitionControl__ is a __ContentControl__ that can apply a transition effect to its content, when it gets changed. The content of the __RadTransitionControl__ can vary from simple strings to complex __UserControls__, as for any __ContentControl__. The transition effect can be chosen among the built-in ones or you can create a custom one. ->tipFor a quick review of the basic features in a sample scenario you can take a look at the [Getting Started]({%slug radtransition-getting-started%}) topic. +>tip For a quick review of the basic features in a sample scenario you can take a look at the [Getting Started]({%slug radtransition-getting-started%}) topic. To learn more about the __RadTransitionControl__ features, you can take a look at the following sections inside this topic: @@ -47,7 +47,7 @@ You can also bind the __Content__ of the __RadTransitionControl__ to a data obje When the content of the __RadTransitionControl__ gets changed, the control can apply a transition effect to the change. By default there is no effect specified and in order to specify one you have to use the __Transition__ property. ->tipThere are several built-in transition effects, which are located in the __Telerik.Windows.Control.TransitionEffects__ namespace of the __Telerik.Windows.Controls__ assembly. In order to use them you have to add the following namespace declaration: +>tip There are several built-in transition effects, which are located in the __Telerik.Windows.Control.TransitionEffects__ namespace of the __Telerik.Windows.Controls__ assembly. In order to use them you have to add the following namespace declaration: @@ -82,10 +82,10 @@ The duration of the transition effect is determined by the __Duration__ property The __RadTransitionControl__ allows you to apply an easing function to the transition effect. The easing functions make the animation much more realistic and smoother. There is a set of predefined easing functions in {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %} and you are allowed to create custom ones, too. {% if site.site_name == 'Silverlight' %} ->tipTo learn more about the easing functions read [here](http://msdn.microsoft.com/en-us/library/cc189019%28VS.95%29.aspx#easing_functions). +>tip To learn more about the easing functions read [here](http://msdn.microsoft.com/en-us/library/cc189019%28VS.95%29.aspx#easing_functions). {% endif %} {% if site.site_name == 'WPF' %} ->tipTo learn more about the easing functions read [here](http://msdn.microsoft.com/en-us/library/ee308751%28v=VS.100%29.aspx). +>tip To learn more about the easing functions read [here](http://msdn.microsoft.com/en-us/library/ee308751%28v=VS.100%29.aspx). {% endif %} By default there is no easing function specified for the __RadTransitionControl__. To specify one you have to set the __Easing__ property to the desired function. diff --git a/controls/radtransitioncontrol/how-to/radtransition-create-custom-transitions.md b/controls/radtransitioncontrol/how-to/radtransition-create-custom-transitions.md index b88dffa471..2a5432b05c 100644 --- a/controls/radtransitioncontrol/how-to/radtransition-create-custom-transitions.md +++ b/controls/radtransitioncontrol/how-to/radtransition-create-custom-transitions.md @@ -95,7 +95,7 @@ In it you have to override the __CreateTransitionEffect()__ method and return an The __Shader Effect__ can also have some constants that can be passed through the wrapper. For example, the previously used __CircleRevealTransitionEffect__ accepts a fuzzy amount constant, which value can make the transition smoother. ->tipIn order to pass arguments to the Shader Effect you must be familiar with it. It is important to pass the correct constants with the correct values. +>tip In order to pass arguments to the Shader Effect you must be familiar with it. It is important to pass the correct constants with the correct values. In order to pass the fuzzy amount constant create an appropriate __DependencyProperty__ in your __CircleRevealTransitionEffect__ class. diff --git a/controls/radtransitioncontrol/radtransition-getting-started.md b/controls/radtransitioncontrol/radtransition-getting-started.md index 5b9e06ffa2..faad19dcc1 100644 --- a/controls/radtransitioncontrol/radtransition-getting-started.md +++ b/controls/radtransitioncontrol/radtransition-getting-started.md @@ -74,7 +74,7 @@ __Example 3: Sample RadListBox definition__ The content of the __RadTransitionControl__ should be represented by the content of the __SelectedItem__ in the __RadListBox__. This can be done by using element to element binding. ->tipYou can learn more about binding the __RadTransitionControl__ in the [Data Binding]({%slug radtransition-features-data-binding%}) topic. +>tip You can learn more about binding the __RadTransitionControl__ in the [Data Binding]({%slug radtransition-features-data-binding%}) topic. __Example 4: Binding RadTransitionControl Content__ @@ -110,7 +110,7 @@ If you run your application at this point, the content of the __RadTransitionCon The __RadTransitionControl__ automatically detects when the content is changed and applies a transition to the content. The default transition is __MotionBlurredZoomTransition__. ->tipTo learn more about the transitions in the __RadTransitionControl__ read the [Transitions]({%slug radtransition-features-transitions%}) topic. +>tip To learn more about the transitions in the __RadTransitionControl__ read the [Transitions]({%slug radtransition-features-transitions%}) topic. As the built-in transition effects are located in the __Telerik.Windows.Controls.TransitionEffects__ namespace of the __Telerik.Windows.Controls__ assembly, you have to add the following namespace declaration in your __UserControl__: diff --git a/controls/radtreelistview/features/data-binding.md b/controls/radtreelistview/features/data-binding.md index abf780878f..d8cc24a9e4 100644 --- a/controls/radtreelistview/features/data-binding.md +++ b/controls/radtreelistview/features/data-binding.md @@ -14,7 +14,7 @@ position: 4 Displaying data in the __RadGridView__ depends on the data binding mechanism. The entry point for the data to be bound is the __ItemsSource__ property, which you must set in order to display data in your __RadGridView__ control. ->tipFor additional information regarding data binding and populating the __RadTreeListView__ with data you can check the respective topics in the [RadGridView's documentation]({%slug gridview-data-overview%}). +>tip For additional information regarding data binding and populating the __RadTreeListView__ with data you can check the respective topics in the [RadGridView's documentation]({%slug gridview-data-overview%}). ## Setting the ItemsSource property @@ -37,7 +37,7 @@ As a typical data control the __RadGridView__ displays data by binding to a sour Unlike the standard items control, the __RadGridView__'s __ItemsSource__ property is declared to be of type __System.Object__. Of course, standard .NET collections that implement the __IEnumerable__ interface are fully supported as well. If you want the insertions or the deletions in the collection to be automatically applied to the UI, the collection to which you bind must also implement the __INotifyCollectionChanged__ interface. Coupling in your code, it may be more convenient to manipulate data in the original data source instead of using the __RadGridView__ API. __RadGridView__ listens to data source collection change events and reflects those changes in its visual representation. In Silverlight there is a built-in implementation of a data collection that exposes the __INotifyCollectionChanged__ interface – the __ObservableCollection__ class. ->tipConsider using __ObservableCollection__ or one of the other existing collection classes like __List__, __Collection__, instead of implementing your own collection. If the scenario requires a custom collection to be implemented, use the __IList__ interface, which provides individual access by index to its items and the best performance. +>tip Consider using __ObservableCollection__ or one of the other existing collection classes like __List__, __Collection__, instead of implementing your own collection. If the scenario requires a custom collection to be implemented, use the __IList__ interface, which provides individual access by index to its items and the best performance. Introduced to the __System.ComponentModel__ namespace collection views are fully supported as well. __RadGridView__ will automatically pick up group descriptions, sort descriptions, or will filter settings defined on the collection view and will use those settings to display data. diff --git a/controls/radtreelistview/features/managing-data.md b/controls/radtreelistview/features/managing-data.md index 160161acba..0908596739 100644 --- a/controls/radtreelistview/features/managing-data.md +++ b/controls/radtreelistview/features/managing-data.md @@ -14,7 +14,7 @@ position: 5 Telerik's __RadTreeListView__ allows you not only to display sets of data, but also to manage them. You are able to use the standard operations - __Insert__, __Update__ and __Delete__. You can also validate the data. Besides using this functionality, you are able to control it via the several events raised at the most important key points of the operation. ->tipAs the __RadTreeListView__ directly inherits the __RadGridView__ it uses the same data management mechanism. To learn more read the [respective topics]({%slug gridview-managing-data-overview%}) in the __RadGridView's__ documentation. +>tip As the __RadTreeListView__ directly inherits the __RadGridView__ it uses the same data management mechanism. To learn more read the [respective topics]({%slug gridview-managing-data-overview%}) in the __RadGridView's__ documentation. ## Managing Collections diff --git a/controls/radtreelistview/features/row-details.md b/controls/radtreelistview/features/row-details.md index 5dfa6b0b39..6d19969361 100644 --- a/controls/radtreelistview/features/row-details.md +++ b/controls/radtreelistview/features/row-details.md @@ -22,7 +22,7 @@ Another benefit of the __Row Details__ is the option of placing the __Details Pr ____ ->tipThe row and the row details share the same data context, so you are free to bind the elements in your template to any of the properties of the data item. +>tip The row and the row details share the same data context, so you are free to bind the elements in your template to any of the properties of the data item. As the __Row Details__ feature is inherited from the __RadGridView__, you can find more detailed information and examples in [its documentation]({%slug radgridview-row-details-overview%}). diff --git a/controls/radtreelistview/how-to/scrollintoview.md b/controls/radtreelistview/how-to/scrollintoview.md index ecef42a33d..d4dcf8befa 100644 --- a/controls/radtreelistview/how-to/scrollintoview.md +++ b/controls/radtreelistview/how-to/scrollintoview.md @@ -331,7 +331,7 @@ Clicking the second button will update the UI only when the bring operation is f End Sub ``` ->tipPlease have in mind that running the application without debugger (__Ctrl + F5__ when in VS) will result in faster user experience. +>tip Please have in mind that running the application without debugger (__Ctrl + F5__ when in VS) will result in faster user experience. >tip Find a runnable project of the previous example in the [WPF Samples GitHub repository](https://github.com/telerik/xaml-sdk/tree/master/TreeView/TreeListViewBringItemIntoView). diff --git a/controls/radtreelistview/localization.md b/controls/radtreelistview/localization.md index b8204eb8fd..f693964dee 100644 --- a/controls/radtreelistview/localization.md +++ b/controls/radtreelistview/localization.md @@ -22,7 +22,7 @@ Here is a list of the supported languages: * Dutch * Turkish ->tipTo learn more about the ways in which to localize the RadControls, please read the common topic about [Localization]({%slug common-localization%}). +>tip To learn more about the ways in which to localize the RadControls, please read the common topic about [Localization]({%slug common-localization%}). ## Resource Keys diff --git a/controls/radtreelistview/overview.md b/controls/radtreelistview/overview.md index 26be25b19f..daa9ab917d 100644 --- a/controls/radtreelistview/overview.md +++ b/controls/radtreelistview/overview.md @@ -52,7 +52,7 @@ Telerik __RadTreeListView__ combines the powerful data-driven features from __Ra Check out the control's demos at: [https://demos.telerik.com/wpf/](https://demos.telerik.com/wpf/) ->tipYou can find more examples on how to implement various scenarios available for download from our online SDK repository [here](https://github.com/telerik/xaml-sdk/), the examples are listed under __TreeListView__. +>tip You can find more examples on how to implement various scenarios available for download from our online SDK repository [here](https://github.com/telerik/xaml-sdk/), the examples are listed under __TreeListView__. {% if site.site_name == 'WPF' %} ## Telerik UI for WPF Support and Learning Resources diff --git a/controls/radtreeview/features/lines-support.md b/controls/radtreeview/features/lines-support.md index da6d17f204..b7dd4493f5 100644 --- a/controls/radtreeview/features/lines-support.md +++ b/controls/radtreeview/features/lines-support.md @@ -26,7 +26,7 @@ You can also control the visibility of the lines between the root items (the ite ![Rad Tree View Features Lines Support 002](images/RadTreeView_Features_LinesSupport_002.png) ->tipFor more information about the visual structure of the __RadTreeView__, check out the [Visual Structure]({%slug radtreeview-visual-structure%}) topic. +>tip For more information about the visual structure of the __RadTreeView__, check out the [Visual Structure]({%slug radtreeview-visual-structure%}) topic. ## Change the LineColor diff --git a/controls/radtreeview/localization.md b/controls/radtreeview/localization.md index a47fba9bd7..e9c2b6c389 100644 --- a/controls/radtreeview/localization.md +++ b/controls/radtreeview/localization.md @@ -22,7 +22,7 @@ Here is a list of the supported languages: * Dutch * Turkish ->tipTo learn more about the ways to localize the UI for {{ site.framework_name }} controls please read the common topic on [Localization]({%slug common-localization%}). +>tip To learn more about the ways to localize the UI for {{ site.framework_name }} controls please read the common topic on [Localization]({%slug common-localization%}). ## Resource Keys diff --git a/controls/radwindow/features/closing.md b/controls/radwindow/features/closing.md index 0f0dd52c85..6f5eb3ed76 100644 --- a/controls/radwindow/features/closing.md +++ b/controls/radwindow/features/closing.md @@ -29,7 +29,7 @@ __Example 1: Closing a RadWindow__ radWindow.Close() ``` ->tipWhen the __RadWindow__ gets closed, the __Closed__ event is raised. More about events can be found [here]({%slug radwindow-events-overview%}). +>tip When the __RadWindow__ gets closed, the __Closed__ event is raised. More about events can be found [here]({%slug radwindow-events-overview%}). ## Prevent Closing diff --git a/controls/radwindow/features/minimizingmaximazing.md b/controls/radwindow/features/minimizingmaximazing.md index 8b71c9dafe..6b0ee24904 100644 --- a/controls/radwindow/features/minimizingmaximazing.md +++ b/controls/radwindow/features/minimizingmaximazing.md @@ -20,9 +20,9 @@ After being minimized or maximized the respective button is replaced by a __Rest #### __Figure 2: RadWindow Restore Button__ ![RadWindow Restore Button](images/RadWindow_Minimize_Maximize_02.png) ->tipEvery time when the __RadWindow__ gets minimized or maximized, it changes its state. More about the __RadWindow__ states can be found [here]({%slug radwindow-features-states%}). +>tip Every time when the __RadWindow__ gets minimized or maximized, it changes its state. More about the __RadWindow__ states can be found [here]({%slug radwindow-features-states%}). ->tipThe __RestoreMinimizedLocation__ property allows the __RadWindow__ to store its size and position for the __Normal__ and the __Minimized__ states. +>tip The __RestoreMinimizedLocation__ property allows the __RadWindow__ to store its size and position for the __Normal__ and the __Minimized__ states. ## See Also diff --git a/controls/radwindow/features/moving.md b/controls/radwindow/features/moving.md index b5c080f813..354a249512 100644 --- a/controls/radwindow/features/moving.md +++ b/controls/radwindow/features/moving.md @@ -14,7 +14,7 @@ The user can move the window by clicking on the __RadWindow__'s header and then ![{{ site.framework_name }} RadWindow Move by Drag](images/RadWindow_Features_Moving_01.png) ->tipWhen the __RadWindow__ gets moved, the __LayoutChangeStarted__ and the __LayoutChangeEnded__ events are raised. More about the events can be found [here]({%slug radwindow-events-overview%}). +>tip When the __RadWindow__ gets moved, the __LayoutChangeStarted__ and the __LayoutChangeEnded__ events are raised. More about the events can be found [here]({%slug radwindow-events-overview%}). To disable the moving of the __RadWindow__ via the UI you have to set the __CanMove__ property to __False__. diff --git a/controls/radwindow/features/positioning.md b/controls/radwindow/features/positioning.md index e6d28abd37..431d5576fd 100644 --- a/controls/radwindow/features/positioning.md +++ b/controls/radwindow/features/positioning.md @@ -20,7 +20,7 @@ The __WindowStartupLocation__ property is an enumeration that provides you with * __CenterOwner__: Positions the __RadWindow__ in the center of its owner, if there is one. ->tipThe __Owner__ property specifies the control, that owns the __RadWindow__. When the WindowStartupLocation is __CenterOwner__, the __RadWindow__ will get centered relatively to its owner. Note that the __Owner__ property should be of type __RadWindow__{% if site.site_name == 'WPF' %} or __WPF Window__{% endif %}. +>tip The __Owner__ property specifies the control, that owns the __RadWindow__. When the WindowStartupLocation is __CenterOwner__, the __RadWindow__ will get centered relatively to its owner. Note that the __Owner__ property should be of type __RadWindow__{% if site.site_name == 'WPF' %} or __WPF Window__{% endif %}. >If you assign the __Owner__ to be a __RadWindow__, make sure that you have opened the owner window prior to opening the child. Otherwise, you will get an __InvalidOperationException__. @@ -30,7 +30,7 @@ The __WindowStartupLocation__ property is an enumeration that provides you with When the __WindowStartupLocation__ is set to __Manual__ you can use the __Top__ and __Left__ properties to specify the absolute distance in pixels from the top-left corner of the page. ->tipYou can use these properties to cascade the windows in your application. +>tip You can use these properties to cascade the windows in your application. ## See Also diff --git a/controls/radwindow/features/window-header.md b/controls/radwindow/features/window-header.md index 7e8b38c1d6..627f975b81 100644 --- a/controls/radwindow/features/window-header.md +++ b/controls/radwindow/features/window-header.md @@ -14,7 +14,7 @@ The __RadWindow__ allows you to display a header in the top part of it. To speci If you have a window-specific header, use the __Header__ property. ->tipAs the __Header__ property is of type object you can set it to any control that you like. If you want to have a more complex icon content that consists of more than one control, be sure to wrap them inside a layout control and pass the layout control as content. +>tip As the __Header__ property is of type object you can set it to any control that you like. If you want to have a more complex icon content that consists of more than one control, be sure to wrap them inside a layout control and pass the layout control as content. >It's not a good practice do declare your __RadWindow__ as visual element in XAML. The only scenario, when it is meaningful to use the __RadWindow__ in XAML, is when it represents the entire user control. To learn more about that read [here]({%slug radwindow-how-to-use-radwindow-as-user-control%}). diff --git a/controls/radwindow/features/working-with-radwindow.md b/controls/radwindow/features/working-with-radwindow.md index 7d0949b01a..9b808ea44c 100644 --- a/controls/radwindow/features/working-with-radwindow.md +++ b/controls/radwindow/features/working-with-radwindow.md @@ -35,7 +35,7 @@ After the reference is available, you can declare a __RadWindow__. Here is an ex When you want to display the __RadWindow__ you have two options - to display it as a __window__ or as a __modal dialog window__. ->tipTo learn more about modal windows read [here]({%slug radwindow-features-modal-windows%}). +>tip To learn more about modal windows read [here]({%slug radwindow-features-modal-windows%}). Call the __Show()__ method of the __RadWindow__ instance to open it as a __normal window__. @@ -61,7 +61,7 @@ Call the __ShowDialog()__ method of the __RadWindow__ instance to open it as a _ ![{{ site.framework_name }} RadWindow Shown As Modal Dialog](images/RadWindow_Working_with_RadWindow_01.png) ->tipLearn more about positioning the __RadWindow__ by reading the [Positioning]({%slug radwindow-features-positioning%}) topic. +>tip Learn more about positioning the __RadWindow__ by reading the [Positioning]({%slug radwindow-features-positioning%}) topic. ## Add content to the RadWindow @@ -69,7 +69,7 @@ To add a content to the __RadWindow__ you can use either the __Content__ or the If you have a window-specific content, use the __Content__ property. ->tipAs the __Content__ property is of type object you can set it to any control you like. If you want to have a more complex content that consists of more than one control, be sure to wrap them inside a layout control and pass the layout control as content.You can also set the content of the __RadWindow__ to a __UserControl__. +>tip As the __Content__ property is of type object you can set it to any control you like. If you want to have a more complex content that consists of more than one control, be sure to wrap them inside a layout control and pass the layout control as content.You can also set the content of the __RadWindow__ to a __UserControl__. >The only scenario, where you can add content to the __RadWindow__ at design-time, is when the __RadWindow__ represents an entire user control. To learn more about that read [here]({%slug radwindow-how-to-use-radwindow-as-user-control%}). diff --git a/controls/radwindow/getting-started.md b/controls/radwindow/getting-started.md index 423a6db1b1..5a470feba8 100644 --- a/controls/radwindow/getting-started.md +++ b/controls/radwindow/getting-started.md @@ -72,7 +72,7 @@ __Example 2: Adding RadWindow in code__ To open the __RadWindow__ you have to call its __Show()__ method. ->tipIn order to make the window modal you have to call the __ShowDialog()__ method. To learn more about modal windows read [here]({%slug radwindow-features-modal-windows%}). +>tip In order to make the window modal you have to call the __ShowDialog()__ method. To learn more about modal windows read [here]({%slug radwindow-features-modal-windows%}). __Example 3: Calling the Show() method__ @@ -89,9 +89,9 @@ __Example 3: Calling the Show() method__ To add content to the __RadWindow__ you have to use the __Content__ property or the __ContentTemplate__ property. ->tipAs the __Content__ property is of type object you can set it to any control that you like. If you want to have a more complex content that consists of more than one control, be sure to wrap them inside a layout control and pass the layout control as content.You can also set the content of the __RadWindow__ to a __UserControl__. +>tip As the __Content__ property is of type object you can set it to any control that you like. If you want to have a more complex content that consists of more than one control, be sure to wrap them inside a layout control and pass the layout control as content.You can also set the content of the __RadWindow__ to a __UserControl__. ->tipYou can skip the in-line setting of the __Content__ property and define the content directly under the __RadWindow__ tag. +>tip You can skip the in-line setting of the __Content__ property and define the content directly under the __RadWindow__ tag. >The only scenario, where you can add content to the __RadWindow__ at design-time, is when the __RadWindow__ represents an entire user control. To learn more about that read [here]({%slug radwindow-how-to-use-radwindow-as-user-control%}). diff --git a/controls/radwindow/how-to/close-the-radwidnow-through-its-content.md b/controls/radwindow/how-to/close-the-radwidnow-through-its-content.md index 225b014673..7efa589e82 100644 --- a/controls/radwindow/how-to/close-the-radwidnow-through-its-content.md +++ b/controls/radwindow/how-to/close-the-radwidnow-through-its-content.md @@ -18,7 +18,7 @@ To close the __RadWindow__ through its content you have to get the instance of t ## Content, directly set to the RadWindow ->tipTo learn more about how to use the __RadWindow__ as user control read [this topic]({%slug radwindow-how-to-use-radwindow-as-user-control%}). +>tip To learn more about how to use the __RadWindow__ as user control read [this topic]({%slug radwindow-how-to-use-radwindow-as-user-control%}). Here is a sample __RadWindow__, used as user control, with a button in it: @@ -60,7 +60,7 @@ As the button is in the same control like the __RadWindow__, you can get the __R End Sub ``` ->tipInstead of event handler you can use a __RadButton__ with the __Close__ command for the __RadWindow__. Here is an example: +>tip Instead of event handler you can use a __RadButton__ with the __Close__ command for the __RadWindow__. Here is an example: @@ -75,7 +75,7 @@ As the button is in the same control like the __RadWindow__, you can get the __R In this scenario the __Button__ is placed inside a __UserControl__, which is passed as the __Content__ of the __RadWindow__. In this case you cannot access the __RadWindow__ directly from the __UserControl__ as it is not aware of its existance. In order to close the __RadWindow__ when the button is clicked, you have to use the __ParentOfType\()__ extension method to get the __RadWindow__ instance. ->tipThe __ParentOfType\()__ is available when you use the __Telerik.Windows.Controls__ namespace from the __Telerik.Windows.Controls__. It returns the first element of this type up in the __Visual Tree__. +>tip The __ParentOfType\()__ is available when you use the __Telerik.Windows.Controls__ namespace from the __Telerik.Windows.Controls__. It returns the first element of this type up in the __Visual Tree__. diff --git a/controls/radwindow/how-to/use-keyboard-to-get-user-response.md b/controls/radwindow/how-to/use-keyboard-to-get-user-response.md index 82afcdfcdf..98bb9bc708 100644 --- a/controls/radwindow/how-to/use-keyboard-to-get-user-response.md +++ b/controls/radwindow/how-to/use-keyboard-to-get-user-response.md @@ -20,7 +20,7 @@ __ResponseButton__ is an attached property that specifies the behavior of the de Here is an example of how to create a window that responds to __Enter__ and __ESC__ keyboard strokes. The example uses the RadWindow as a user control: ->tipTo learn more about how to use the __RadWindow__ as user control read [this topic]({%slug radwindow-how-to-use-radwindow-as-user-control%}). +>tip To learn more about how to use the __RadWindow__ as user control read [this topic]({%slug radwindow-how-to-use-radwindow-as-user-control%}). diff --git a/controls/radwindow/how-to/use-radwindow-as-user-control.md b/controls/radwindow/how-to/use-radwindow-as-user-control.md index ab62fc42fa..dd74849d24 100644 --- a/controls/radwindow/how-to/use-radwindow-as-user-control.md +++ b/controls/radwindow/how-to/use-radwindow-as-user-control.md @@ -49,7 +49,7 @@ Also in the code behind your user control should inherit the __RadWindow__ inste End Class ``` ->tipIf you have installed UI for {{ site.framework_name }}, you can easily create the __RadWindow UserControl__ with the Telerik templates - just click Add -> New Item... in the project Context Menu and choose "Telerik Scenario" from the installed templates. In the Scenario Wizard select __RadWindow__. +>tip If you have installed UI for {{ site.framework_name }}, you can easily create the __RadWindow UserControl__ with the Telerik templates - just click Add -> New Item... in the project Context Menu and choose "Telerik Scenario" from the installed templates. In the Scenario Wizard select __RadWindow__. In the XAML you can declare the content of the __RadWindow__ directly in XAML and use the code-behind to wire-up some logic, as you would do with an __UserControl__. You can also set the properties of the __RadWindow__. This way you can have a configured __RadWindow__ at design time and the only thing you have to do is to show it, when needed.