This is an automated email from the ASF dual-hosted git repository.
andreww pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/royale-docs.git
The following commit(s) were added to refs/heads/master by this push:
new dd7e5e7 Update jewel-group.md
dd7e5e7 is described below
commit dd7e5e7e73d75f6cbd5b82d3839b8f60a0d0b92b
Author: Andrew Wetmore <[email protected]>
AuthorDate: Fri Oct 2 17:45:49 2020 -0300
Update jewel-group.md
Minor text edits
---
component-sets/jewel/jewel-group.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/component-sets/jewel/jewel-group.md
b/component-sets/jewel/jewel-group.md
index 8de9ddb..83b73bc 100644
--- a/component-sets/jewel/jewel-group.md
+++ b/component-sets/jewel/jewel-group.md
@@ -36,7 +36,7 @@ Available since version __0.9.4__.
## Overview
-The Jewel Group class provides a light-weight container for visual elements.
By default the group has a Basic Layout, so you can size and position its
children with absolute positioning (the Basic layout groups the children, but
does not provide layout information). You can swap the layout for any other one
available (for instance horizontal or vertical) to arrange the children in
different ways. The group doesn't clip content, so elements inside the group
aren't hidden if they extend be [...]
+The Jewel Group class provides a lightweight container for visual elements. By
default the group has a Basic Layout, so you can size and position its children
with absolute positioning (the Basic layout groups the children, but does not
provide layout information). You can swap the layout for any other one
available (for instance horizontal or vertical) to arrange the children in
different ways. The group doesn't clip content, so elements inside the group
aren't hidden if they extend bey [...]
Also, the group has no scrolling support. For scrolling and clipping you can
use [Jewel Container](component-sets/jewel/container).
@@ -93,7 +93,7 @@ where `parent` is the container where the control will be
added.
## Relevant Events
-The most important event is `initComplete`, which indicates that the
initialization of the group is complete. You can use this when some action
coded in a callback functions need to be triggered when the group has
initialized and is ready to use.
+The most important event is `initComplete`, which indicates that
initialization of the group is complete. You can use this when some action
coded in a callback function need to be triggered when the group has
initialized and is ready to use.
You can attach callback listeners to the _initComplete_ event in __MXML__ as
follows:
@@ -101,7 +101,7 @@ You can attach callback listeners to the _initComplete_
event in __MXML__ as fol
<j:Group initComplete="initCompleteHandler(event)"/>
```
-the _initComplete_ event will use the `initCompleteHandler` callback function
you provide in __ActionScript__:
+the _initComplete_ event uses the `initCompleteHandler` callback function you
provide in __ActionScript__:
```mxml
<fx:Script>
