Symbian3/PDK/Source/GUID-D3F52BB9-7230-499C-9BB7-CFAEDBA8F48B.dita
changeset 5 f345bda72bc4
parent 3 46218c8b8afa
child 9 59758314f811
equal deleted inserted replaced
4:4816d766a08a 5:f345bda72bc4
    15 in some cases you may have to define a priority for the feedback areas. </p>
    15 in some cases you may have to define a priority for the feedback areas. </p>
    16 <p>Consider, for example, situations where a compound control has a simple
    16 <p>Consider, for example, situations where a compound control has a simple
    17 control inside its own area as illustrated in the figure below.</p>
    17 control inside its own area as illustrated in the figure below.</p>
    18 <fig id="GUID-C70125A6-393A-428D-A22B-7F6EEC72FAAF">
    18 <fig id="GUID-C70125A6-393A-428D-A22B-7F6EEC72FAAF">
    19 <title>Tactile feedback area priorities</title>
    19 <title>Tactile feedback area priorities</title>
    20 <image href="GUID-5BD8EE4B-3149-4331-91E0-7813DF4994E1_d0e76798_href.png" scale="70" placement="inline"/>
    20 <image href="GUID-5BD8EE4B-3149-4331-91E0-7813DF4994E1_d0e107134_href.png" scale="70" placement="inline"/>
    21 </fig>
    21 </fig>
    22 <p>In both situations, the compound control wants to give one type of feedback,
    22 <p>In both situations, the compound control wants to give one type of feedback,
    23 but there should be a different type of feedback (or no feedback at all) for
    23 but there should be a different type of feedback (or no feedback at all) for
    24 the simple control. Both controls can register themselves to area registry,
    24 the simple control. Both controls can register themselves to area registry,
    25 but the problem is making sure that simple control has a higher priority than
    25 but the problem is making sure that simple control has a higher priority than
    34 </ol></p>
    34 </ol></p>
    35 <p>In many cases the first option is most natural choice, but you can also
    35 <p>In many cases the first option is most natural choice, but you can also
    36 use the second option in case the situation changes after the areas have been
    36 use the second option in case the situation changes after the areas have been
    37 already added to the area registry.</p>
    37 already added to the area registry.</p>
    38 <note><p>The priority order will only remain as long as the next area is added
    38 <note><p>The priority order will only remain as long as the next area is added
    39 to the registry, i.e. moving some area to first priority will only keep it
    39 to the registry, that is, moving some area to first priority will only keep
    40 as the top priority area as long as the next area is added to the registry.
    40 it as the top priority area as long as the next area is added to the registry.
    41 (Registry entries of one window are kept in a stack, and new areas are always
    41 (Registry entries of one window are kept in a stack, and new areas are always
    42 added on top.)</p></note>
    42 added on top.)</p></note>
    43 </conbody></concept>
    43 </conbody></concept>