Support of inline cursors

In a query.
select b.APP_ID
, NVL(b.RECORD_SERIES, 'TO BE ASSIGNED') as "Category"
, 'ACTIVE' as "archiveStatus"
, cursor(select a."author" as "author"
from authors a
          where a.ae_id=b.APP_ID
          and a."author" is not null
) as "authors"
, cursor(SELECT a."name"
, a."totalFileSize"
, a.ac_id
, a."file"
, a."format"
, a."filePath"
, a."size"
, a."status"
, a."checksum"
FROM documents a
where a.ae_id = b.APP_ID ) as "documents"     
FROM main_table b
Current version 4 of SQL Developer only displays oracle.jdbc.driver.OracleResultSetImpl@18a62f6     in the grid. Will the final release allow for drillable nested queries like this?

select b.APP_ID
, NVL(b.RECORD_SERIES, 'TO BE ASSIGNED') as "Category"
, 'ACTIVE' as "archiveStatus"
, cursor(select a."author" as "author"
from authors a
where a.ae_id=b.APP_ID
and a."author" is not null
) as "authors"
, cursor(SELECT a."name"
, a."totalFileSize"
, a.ac_id
, a."file"
, a."format"
, a."filePath"
, a."size"
, a."status"
, a."checksum"
FROM documents a
where a.ae_id = b.APP_ID ) as "documents"
FROM main_table b
This type of query is used in my case to generate XML. The inline cursor will pull a multi row result for a given row. Much like a nested table would.

Similar Messages

  • [svn] 3203: Add support for inline two-way data binding (syntax is @{expr}) .

    Revision: 3203<br />Author:   [email protected]<br />Date:     2008-09-14 05:11:47 -0700 (Sun, 14 Sep 2008)<br /><br />Log Message:<br />-----------<br />Add support for inline two-way data binding (syntax is @{expr}).  Also add support for two-way data binding via the <mx:Binding> tag and the new property twoWay=boolean (default is false).<br /><br />Code Reviewer: Paul<br />QA: tests for this feature need to be added to the regression test suite<br />Doc: new feature which needs to be documented<br /><br />Modified Paths:<br />--------------<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/InterfaceCompiler.java<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/analyzer/SyntaxAnalyzer.java <br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/AbstractBuilder.java <br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/AnonymousObjectGraph Builder.java<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/DocumentBuilder.java <br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/ModelBuilder.java<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/ServiceRequestBuilde r.java<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/XMLBuilder.java<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/XMLListBuilder.java< br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/dom/BindingNode.java<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/lang/TextParser.java<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/BindingExpression.java<b r />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/MxmlDocument.java<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler_en.properties

    EvilDave UK wrote:
    Surely there's a more practical way around this without having to reboot?
    Before you go to the trouble of going through all those steps, be warned that attempting to use Dreamweaver CS4 with SVN could even cause Dreamweaver to crash after updating to SVN 1.6.2. I, too, have abandoned SVN integration with Dreamweaver until the problems are sorted out. I reported this problem to Adobe a couple of weeks ago, and spent a long time working with an Adobe engineer, who was able to reproduce the problem, but not offer a solution. Hopefully, the next version of Dreamweaver will have more robust support for Subversion.

  • Inline power support

    Hi,
    Does the new ESW switches support "Cisco Inline Power" Some Service Providers are using CP-7940/60 with SIP image as a service and need switches that automatically detects that the device only support Inline Power..
    regards
    /Bjorn

    The ESW 500 series of switches does power up the 7960 / 7940 phones (pre standard) via POE.

  • Is the Cursor.cursor info property from 5.1.1 supported in 6.1?

    I have compiled a 5.1.1 application to 6.1 and see that the wfm graph property Cursor.Cursor Info cluster is present and wired. When I create a new waveform graph in 6.1 I can't find this property. Is it still supported?

    The cursor properties from 5.1 are still there (plus a few more), just not bundled into a cluster CursorInfo. For example, CursorInfo.Cursorname is now just Cursor.CursorName
    If you need them bundled as a cluster, for compatability or convenience, you'll have to bundle the individual properties into a cluster.
    If you're working within the same VI, you can copy the property node (using +drag) then right click and select "Link to" and you'll be able to reassign this property node to a new graph.
    Tim

  • When type Japanese characters they appear not at cursor place. How to solve?

    Hi,
    There is some troubles at Japanese text input. When start to type Japanese (or Chinese) characters they appear not at cursor place, it's very inconvenient for using. How could it be solved?
    Some screenshots done in demo TLF site http://labs.adobe.com/technologies/textlayout/demos/
    Regards,
    Ann

    It would be strange if this would be the desired behavior. The problem is - the position of the "input box" on the screen is changing and is not even predictable.
    I am using Windows XP.
    Here it is in one position
    Here I clicked on the Font drop-down - so now I have the position there, and whatever I do, it stays there.
    Unless I click on Data sourse drop-down - then I have it there
    This input box does not return to the editor, although after hitting Enter I do get the characters at the place of the cursor.
    But it makes it basically unusable for japanese and some other languages - if there are any other controls in the application, the input box moves to them if I click there, and does not return. Besides, in many cases it overlaps already inputted text, which is very inconvenient for the user.
    Where is this input box supposed to be by design, I wonder? And how do I keep it there?
    Another question - is the support for inline input planned and if so, when?

  • Retrieving cursor from a stored procedure

    Hi,
    Is there any means to retrieve a cursor from a stored procedure using java.sql.* package, without using database specific type code like OracleTypes.CURSOR?
    Regards,
    Shalin.

    Hi,
    I had some across this problem some time ago. Although, there is no direct answer to this solution, there is a "kloog" that you can apply.
    Please note that the signature for registerOutParameter(int parameterIndex, int sqlType), and note that where ever sqlType is mentioned it is an int.
    Now JDBC is an interface and the implementation is given by Oracle. So to register an "out" parameter all you have to do is registerOutParameter(1, OracleTypes.CURSOR). It works!
    Or otherwise try and find out what the int value of CURSOR is and replace. This is because not all databases can support returning a "cursor" type, since ORACLE and few other databases have a concept of "STORED PROCEDURE" and PLSQL is specific to ORACLE.
    I hope this helps!
    Cheers,
    John.

  • Hardware Color Cursor Problem in Windows 8.1

    I have 2 issues related to the cursor on Win8.1 with 2 display adapters.  It seems Windows 8.x problem.
    Issue #1, Primary display adapter is using hardware color cursor and secondary adapter is software cursor. It will have cursor left over on the secondary screen when the cursor is moving from
    secondary screen to primary screen.
    Issue #2, Primary display adapter is using hardware color cursor and secondary adapter is software cursor. There will be 2 cursors on the left upper corner of the primary display screen when
    dragging the cursor around the upper left corner of the primary display screen.
    So the problem seems caused by 2nd display adapter doesn't support hardware color cursor then will create these two problems.  
    If I switched to software cursor in the Control panel, then there will not have these problems. Also if both use hardware cursor, then there is no problem.  
    Can anyone help to confirm if this is the Windows 8.x bug or not?
    Thank you very much.
    Regards,
    Francis

    Hi Francis Fung,
    When checking in Mouse Properties, I couldn't find any settings that would allow me to change to software cursor under any tabs like Buttons, Pointers, Pointer Options, Wheel and Hardware(reference)
    Some specific mouse would have its own functions, make sure that we follow the instructions to configure the settings, for the two adapter issue, please also consider seek help at the manufacturer side and see if any further help would be offerred there.
    Thank you for your understanding.
    Best regards
    Michael Shao
    TechNet Community Support

  • Harry, Why won't Portal Developers Support Oracle Support???

    I just got off the phone with Oracle support and the response is
    that they can't provide assistance on my TAR because the portal
    developers won't give them the info. Why?
    All I have been asking for are the columns/tables in PORTAL30
    and/or PORTAL30_SSO that store the page name (and display name),
    owner, etc. for each page, content area, application, etc. This
    way I can more easily generate a script to do the page/content
    area exports/imports instead of going through the navigator and
    clicking edit on each object. And how about a data model like
    Apps offers its users -- surely one exists so why not share it?
    Bob

    I'm using this procedure to list all my pages. For now I just
    run this in Portal and copy/paste it into an export dos-batch
    script which exports all the specified pages. Later I will
    update the procudure so that it generates the export script
    automatically.
    Create or Replace PROCEDURE SUPPORT.DUMP_PAGES
    as
    CURSOR page_cur IS
    SELECT NAME
    FROM PORTAL30.WWPOB_PAGE$
    WHERE CREATED_BY='USERNAME';
    begin
    FOR page IN page_cur
    LOOP
    -- Syntax I need in my export script...
    htp.p('call E:\support_dump\dump_page.bat ' ||
    page.name || '<BR>');
    END LOOP;
    htp.p('<P>');
    FOR page IN page_cur
    LOOP
    -- Syntax I need in my importt script...
    htp.p('call E:\support_dump\imp_page.bat ' ||
    page.name || '<BR>');
    END LOOP;
    end;

  • How to change html-css cursor style in Adobe Air?

    We all know how to change cursor style in  Html pages, of course using css such as,
    'cursor: url("move.cur"),  move'.
    But when I use it in Adobe Air, it will not show the standard  cursor style in browser, but the special ones in Adobe. For example, the  'move' cursor shows like a hand(the same with the move hand in Acrobat  Reader), not like a crosshair.
    I tried to use 'url' option in CSS,  but it doesn't work in Adobe Air(I'm sure that it works in html  browsers).
    I am really confused. And looking forward to your  solutions.

    Hi flexo222,
    Currently Adobe AIR does not support custom CSS cursors and only some of the "default" cursors available in CSS.
    You could however use the following ActionScript workaround if you don't need a very complex behavior:
      * on mouseOver have the default cursor hidden
      * on mouseMove have a custom cursor drawn and positioned via ActionScript
      * on mouseOut have the custom cursor hidden and the default cursor shown.
    I have attached a sample that should make things clearer. Feel free to ask if there's anything not clear.
    Cheers,
    Mihai

  • Does Discoverer Desktop 10g allows Inline queries??

    Can anyone working on 10g tell me, whether Disco 10g allows the use of Inline queries while working with Discoverer Desktop & importing SQL.
    I am currently working on 4 & it doesn't allow.
    Thanks

    Thanks for your reply Steve, I am agree with you on your explanation. But still there are situations when you need to have alternate solutions.
    So my Question is still as it is Whether 10g supports using Inline queries while Importing SQLs or not.

  • ISE inline posture limitation.

    Hi all,
    Can any one help me in configuration of ISE in inline posture mode. and What are the limitation of this mode.

    The following are known limitations for Inline Posture in Cisco ISE, Release 1.0.
    • Inline Posture is not supported in a virtual environment, such as VMware.
    • Backup and restore is not available for Inline Posture nodes in Cisco ISE, Release 1.0.
    • The Simple Network Management Protocol (SNMP) Agent is not supported by Inline Posture.
    • The Cisco Discovery Protocol (CDP) is not supported by Inline Posture.
    For more information over configuration and others you can see the attached PDF    

  • Sensitive cursors

    Moved this post from the SQL PL/SQL forum. Apologies if you had to read this twice..
    All,
    I have a rather general question about oracle support for sensitive cursors, I need to establish a scrollable result set and "see" changes to the selected data, updated by a different process. There is some mention of oracle support for scrollable cursors that are sensitive, implemented in the JDBC driver.
    Is there something similar that I could use to enhance my OPEN cursor implementation in OCI.
    thanks in advance,
    badri

    A scrollable cursor provides support for forward and backward access into the result set from a given position, using either absolute or relative row number offsets into the result set.
    You can use scrollable cursor to see updated data if client side Caching is not used.
    Oracle does not support DML operations on scrollable cursors. A cursor cannot be made scrollable if the LONG datatype is part of the select list.
    Moreover, fetches from a scrollable statement handle are based on the snapshot at execution time. OCI client prefetching works with OCI scrollable cursors. The size of the client prefetch cache can be controlled by the existing OCI attributes OCI_ATTR_PREFETCH_ROWS and OCI_ATTR_PREFETCH_MEMORY.
    Example of Access on a Scrollable Cursor
    Assume that a result set is returned by the SQL query:
    SELECT empno, ename FROM emp
    and that the table EMP has 14 rows. One use of scrollable cursors is:
    /* execute the scrollable cursor in the scrollable mode */
    OCIStmtExecute(svchp, stmthp, errhp, (ub4)0, (ub4)0, (CONST OCISnapshot *)NULL,
    (OCISnapshot *) NULL, OCI_STMT_SCROLLABLE_READONLY );
    /* Fetches rows with absolute row numbers 6, 7, 8. After this call,
    OCI_ATTR_CURRENT_POSITION = 8, OCI_ATTR_ROW_COUNT = 8 */
    checkprint(errhp, OCIStmtFetch2(stmthp, errhp, (ub4) 3,
    OCI_FETCH_ABSOLUTE, (sb4) 6, OCI_DEFAULT);
    /* Fetches rows with absolute row numbers 6, 7, 8. After this call,
    OCI_ATTR_CURRENT_POSITION = 8, OCI_ATTR_ROW_COUNT = 8 */
    checkprint(errhp, OCIStmtFetch2(stmthp, errhp, (ub4) 3,
    OCI_FETCH_RELATIVE, (sb4) -2, OCI_DEFAULT);
    /* Fetches rows with absolute row numbers 14. After this call,
    OCI_ATTR_CURRENT_POSITION = 14, OCI_ATTR_ROW_COUNT = 14 */
    checkprint(errhp, OCIStmtFetch2(stmthp, errhp, (ub4) 1,
    OCI_FETCH_LAST, (sb4) 0, OCI_DEFAULT);
    /* Fetches rows with absolute row number 1. After this call,
    OCI_ATTR_CURRENT_POSITION = 1, OCI_ATTR_ROW_COUNT = 14 */
    checkprint(errhp, OCIStmtFetch2(stmthp, errhp, (ub4) 1,
    OCI_FETCH_FIRST, (sb4) 0, OCI_DEFAULT);
    /* Fetches rows with absolute row numbers 2, 3, 4. After this call,
    OCI_ATTR_CURRENT_POSITION = 4, OCI_ATTR_ROW_COUNT = 14 */
    checkprint(errhp, OCIStmtFetch2(stmthp, errhp, (ub4) 3,
    OCI_FETCH_NEXT, (sb4) 0, OCI_DEFAULT);
    /* Fetches rows with absolute row numbers 3,4,5,6,7. After this call,
    OCI_ATTR_CURRENT_POSITION = 7, OCI_ATTR_ROW_COUNT = 14. It is assumed
    the user's define memory is allocated. */
    checkprint(errhp, OCIStmtFetch2(stmthp, errhp, (ub4) 5,
    OCI_FETCH_PRIOR, (sb4) 0, OCI_DEFAULT);
    checkprint (errhp, status)
    ub4 rows_fetched;
    /* This checks for any OCI errors before printing the results of the fetch call
    in the define buffers */
    checkerr (errhp, status);
    checkerr(errhp, OCIAttrGet((CONST void *) stmthp, OCI_HTYPE_STMT,
    (void *) &rows_fetched, (uint *) 0, OCI_ATTR_ROWS_FETCHED, errhp));
    ...

  • Poe881 Router and Cisco Inline Power (pre-standard PoE)

    I have a number of 881 Routers and 79x0 IP Phones. These phones use "Cisco Inline Power", aka "pre-standard PoE". In other words, they are not compatible with standard 802.3af PoE.
    It would be possible for me to install a daughtercard and DC adapter in the 881 routers and provide PoE to two of the ethernet ports. My question is whether the 881 (when equipped for PoE) will support Cisco Inline Power, or if it will only support 802.3af.
    For reference, the 200 and 300 series Small Business switches support these phones with a software upgrade. See this link: https://supportforums.cisco.com/document/71841/200-and-300-switches-now-supports-cisco-pre-standard-poe-legacy-poe
    Many thanks,
    Tom

    My question is whether the 881 (when equipped for PoE) will support Cisco Inline Power, or if it will only support 802.3af.
    Hi Tom,
    I don't have an 880 but I have a large fleet of 890 and all of them have PoE and I know these 890 support 802.3af easily.

  • Why my cursor didn't change in Dreamweaver?

    abbr:hover {
         cursor: url(/images/aero_arrow_xl.cur), pointer;
    The cursor aero_arrow_xl.cur is taken or copied from the cursor directory under the Windows folder.
    The aero_arrow_xl.cur is not shown, instead the pointer is only shown.
    And the same situation is in other cases, for example:
    abbr:hover {
    cursor: url(images/awesome.cur), url(images/awesome_cursor.png), pointer;
    awesome.cur is not shown, nor awesome_cursor.png is not shown, instead the ponter is always shown.

    Verify that your links are correct.
    Your first example shows a site root relative link (with the leading /). Unless you have a local server set up, it won't function correctly when previewing in a browser.
    Your second link example in bold looks correct but without being privvy to your folder structure and whether you are using the css in an external file. It's very hard to say.
    Could you post a link to a page where it's not working.
    Also, cursor images seem to be a bit "stickier" than a normal image in the browser cache. Make sure you clear your cache to preview them.
    Finally, which browsers are you checking this in, some of the older ones have no support for custom cursor images.

  • Weekly build notes listings

    Since there are major changes going on in the TLF weekly builds, and the ASDocs aren't up to date, and the changes made are not searchable, I thought people might want the list dumped on here so changes to particular classes would show up in a forum search.  To see the changes made in Build 360, check out the TLF Blog post on it ( http://blogs.adobe.com/tlf/2009/02/tlf_api_changes_in_build_370_1.html ).
    Here's the list.  Maybe this could become a common practice.
    Build 432, Fri May 15 2009
    Changes in build 437 (2009/05/22)
        * remove flashx.textLayout.edit.UndoManager and flashx.textLayout.IUndoManager
        * Fix 2330964 BackgroundColor Placed incorrectly from TextLineFactory. Actually was in 436.
        * Fix 2326588 TextContainerManager Does Not Support Background Color
        * Fix 2330946 Remove TextContainerManager.trunctationOptions property
        * Fix 2337918 Please expose the scrollToPosition() API in TextContainerManager
        * Fix 2336672 Preserve selection when switching editingMode in TextContainerManager
        * Setting editingMode to the current editingMode should do nothing in TextContainerManager
    Changes in build 436 (2009/05/22)
        * Fix 2331711 TextContainerManager now sends a DamageEvent from setText().
        * Fix 2326543 bug where selection wasn't being extended on mouse drag.
        * add [RichTextContent] metadata to SpanElement and FlowGroupElement mxmlChildren properties
        * Fix 2337740 Flex bug SDK-20964 TCM rcycling bug
        * Partial fix 2330964 background color placed incorrectly from TextLineFactory
        * Remove vestigal experiment with Tables code
        * Fix 2321538. On the Mac, the keyboard shortcuts for cmd-A,C,V,X were not working.
        * Fix 2326543, "drag select of scrolling flows doesn't expand selection".
        * Fix 2329527. Content bounds being reported was slightly different between the factory and TextFlow composer.
        * Fix 2328695 TextContainerManager Stops Receiving FocusIn Events. This is a complete fix - previously this bug was worked around
        * Added TextLineFactoryBase.isTruncated
        * Fix 2315119 - Graphic will be redrawn when link applied.
    Changes in build 434 (2009/05/22)
        * Fix 2323921: RichText truncation doesn't work in all cases
    Build 432, Fri May 15 2009
    Changes in build 432 (2009/05/14)
        * Fixed regression that broke truncation feature
        * Added TextLineFactoryBase.isTruncated
        * Changed text line factory behavior such that scrolling is turned off when truncation options are set
    Build 427, Fri May 8 2009
    Changes in build 427 (2009/05/07)
        * Fix bug - RTE in computeSelectinIndexInContainer
        * Namespace change -- mxml namespace for TLF was "library:adobe/flashx/textLayout". Now it is: library://ns.adobe.com/flashx/textLayout".
        * Fix bug - Scrolled TextContainerManager Can be Difficult To Create Point Selection
    Changes in build 426 (2009/05/06)
        * Fix bug - TextFlow double-deletes text when pressing the backspace or delete key
    Build 422, Fri May 1 2009
    Changes in build 422 (2009/04/30)
        * API Changes: TextContainerManager now has a getContentBounds function, in place of individual getters for contentLeft, contentTop, etc. ContainerController also now has a getContentBounds function, in place of individual getters. Added functions to TextContainerManager to support custom classes for ISelectionManager and IEditManager (see createSelectionManager and createEditManager).
        * API changes for TextContainerManager:
              o getInteractionManager renamed to beginInteraction(), and added a new function endInteraction() which clients should use after beginInteraction() to signal that they are done with selecting/editing. This tells the TextContainerManager that it can go back to factory mode, which is more efficient.
              o invalidateInteractionManager() removed and replaced with two new functions, invalidateSelectionFormats() which clients should called when SelectionFormats have changed, and invalidateUndoManager which clients should call to change the undo manager.
        * API Changes for InputManager
              o InputManager renamed as TextContainerManager
              o IInputManagerClient removed, now you can subclass InputManager and override its methods
        * API Changes:
              o InputManager
                    + damaged property renamed to isDamaged() function
                    + focusSelectionFormat renamed to focusedSelectionFormat
                    + container retyped to Sprite
                    + compositionWidth and compositionHeight removed as constructor parameters, now you need to set the properties on the InputManager you create
              o ContainerController
                    + container retyped to Sprite
              o ISelectionManager
                    + focusSelectionFormat renamed to focusedSelectionFormat
              o IConfiguration & Configuration
                    + focusSelectionFormat renamed to focusedSelectionFormat
        * API Changes:
              o ISelectionManager
                    + setSelection deselects if negative numbers are passed in.
                    + selectAll removed, you can call ISelection.setSelection() to get the same behavior, if you need to redraw the selection, call ISelectionManager.textFlow.flowComposer.updateAllControllers().
                    + flushPendingEvents moved to IInteractionHandler
                    + notifyInsertOrDelete moved to IInteractionHandler
              o IUndoManager
                    + clear renamed to clearAll().
                    + undoLastOperation renamed to undo()
                    + redoLastOperation renamed to redo()
        * API Change: SelectionEvent now contains a SelectionState, not an ElementRange; this is much cheaper for us to provide. ElementRange is now tlf_internal. ElementRange.firstLeafPosition renamed to absoluteStart, ElementRange.lastLeafPosition renamed to absoluteEnd.
        * API Change: TextScrap.copyTextScrap renamed to clone.
        * API Changes to InputManager. defaultInputManagerConfiguration renamed to defaultConfiguration. composeToController renamed to compose(), and updateToController renamed to updateContainer().
        * API Changes:
              o ISelectionManager:
                    + Event handling functions moved out of ISelectionManager into new interface, IInteractionHandler
                    + selectionFormat renamed to currentSelectionFormat
                    + selectionState renamed to function getSelectionState()
                    + setSelection now takes default parameters to select the entire flow
                    + noFocusSelectionFormat renamed to unfocusedSelectionFormat
              o SelectionFormat:
                    + blockAlpha reanmed to rangeAlpha
                    + blockBlendMode renamed to rangeBlendMode
                    + blockColor renamed to rangeColor
              o IEditManager:
                    + added get undoManager()
                    + added changeElementID()
                    + added changeElementStyleName()
              o SelectionManager:
                    + activeMark and anchorMark are now private
                    + selectionChanged is private
                    + setSelectionState is tlf_internal
              o EditManager:
                    + stage is private
                    + ChangeElementIdOperation renamed to ChangeElementIDOperation
    Changes in build 420 (2009/04/28)
        * API change: Removed the misleadingly named and superfluous TextFlowLine.textIndent. Documented and ensured consistent use of TextFlowLine.lineOffset as lhe line's offset in pixels from the appropriate container inset (as dictated by paragraph direction and container block progression), prior to alignment of lines in the paragraph.
        * API change: more changes to the factory classes. ITextLineCreator is now a property of the base class, so instead of passing it in the constructor you construct and then set the property in the factory. bounds property renamed to compositionBounds, and measuredBounds renamed to contentBounds. containerController property is now private.
        * API Change: moved ITextLineCreator interface from the elements package to the compose package.
        * PlainTextExporter is now public and has methods for controlling the paragraphSeparator and whether discretionary hyphens are included in the export. To use it, you can either construct it directly, or via the TextFilter class. Removed the newlineIndicator string from IConfiguration.
        * Fixed a bug where tabs in RTL text were being being offset by textIndent and marginRight values.
    Changes in build 419 (2009/04/24)
        * Once a mouseWheel event has been handled, mark with preventDefault so client applications don't also try to handle it.
        * Don't start compose if text is already composed. Optimization for callers of composeToPosition.
        * Always call resetContentTopLeft, to give more accurate top left positions, particularly for cases where the text is outdented and left aligned.
        * API CHANGE: TextLineFactory revised. It is now split into 3 classes, TextLineFactoryBase, StringTextLineFactory, and TextFlowTextLineFactory. Use StringTextLineFactory for creating TextLines from a String. Use TextFlowTextLineFactory for creating TextLines from a TextFlow. Static methods have been removed, so create a new factory in order to create lines. One factory may be reused many times, just resetting the values (text, bounds, truncation options, etc.) in between. See StaticHelloWorld.as for a simple example of how this works for Strings, see StaticTextFlow.as for a simple example of it with TextFlows.
    Build 418, Fri Apr 24 2009
    Changes in build 418 (2009/04/23)
        * API CHANGE: TextLineFactory revised. It is now split into 3 classes, TextLineFactoryBase, StringTextLineFactory, and TextFlowTextLineFactory. Use StringTextLineFactory for creating TextLines from a String. Use TextFlowTextLineFactory for creating TextLines from a TextFlow. Static methods have been removed, so create a new factory in order to create lines. One factory may be reused many times, just resetting the values (text, bounds, truncation options, etc.) in between. See StaticHelloWorld.as for a simple example of how this works for Strings, see StaticTextFlow.as for a simple example of it with TextFlows.
    Changes in build 417 (2009/04/22)
        * Fixed Vertical Justification behavior; it now increases the spacing between consecutive lines proportionally rather than spacing lines uniformly.
        * API Changes: Renamed DisplayObjectContainerController to ContainerController, and removed IContainerController and IInternalContainerController. Wherever you used to use "IContainerController" or "DisplayObjectContainerController" now just use "ContainerController".
              o Moved some functions that were public into the tlf_internal namespace: effectivePaddingLeft, effectivePaddingTop, effectivePaddingRight, and effectivePaddingBottom.
              o ColumnState.createColumnState removed. A ColumnState constructor now takes all the relevant values, so whereever you used to do this:
                    + var columnState:ColumnState = ColumnState.createColumnState(...your values here...);
              o you can now do this:
                    + var columnState:ColumnState = new ColumnState();
              o ColumnState.getColumnAtIndex(index) has been renamed to getColumnAt(index). So, once you have the columnState, you do, for instance:
                    + var columnRect:Rectangle = getColumnAt(0);
        * Fixed bug where spaces at end of a line would "overflow" into neighboring columns. New code keeps drawing of cursor at the column boundary and limits block selection drawing to the same bounds.
        * Enhancement to cursor navigation for Right to Left text systems. Previous code moved cursor according to logical order vs. visual order. Result was that a right arrow key press in Arabic, Hebrew or other RTL languages meant that the cursor actually moved left. New code moves cursor according to the visual order of the text based on the direction of the entire text flow. Note that changing the direction on a paragraph will not alter the behavior of the cursor, nor will the presence of LTR text within a RTL text flow. This means that if a TextFlow is set to Right to Left and a given paragraph is entirely in English and the paragraph is set to be Left to Right, the cursor will seem to move in the wrong direction. TLF does not support customization of cursor movement based on the locale or direction of anything except the parent TextFlow.
        * Fixed a bug that caused undoing an ApplyFormatToElementOperation to have no effect.
        * API Changes:
              o DisplayObjectContainer event handling functions renamed:
                    + processMouseOverEvent -> mouseOverHandler
                    + processMouseOutEvent -> mouseOutHandler
                    + processMouseWheelEvent -> mouseWheelHandler
                    + processMouseDownEvent -> mouseDownHandler
                    + processMouseUpEvent -> mouseUpHandler
                    + processMouseMoveEvent -> mouseMoveHandler
                    + processMouseDoubleClickEvent -> mouseDoubleClickHandler
                    + processFocusInEvent -> focusInHandler
                    + processFocusOutEvent -> focusOutHandler
                    + processActivateEvent -> activateHandler
                    + processDeactivateEvent -> deactivateHandler
                    + processKeyDownEvent -> keyDownHandler
                    + processKeyUpEvent -> keyUpHandler
                    + processTextInputEvent -> textInputHandler
                    + processContextMenuSelectHandler -> menuSelectHandler
                    + eventHandler -> editHandler
              o ISelectManager & SelectionManager & EditManager renamings:
                    + eventHandler -> editHandler
        * API Changes: renamed IContainerController.scrollLines to getScrollDelta, renamed InputManager.scrollLines to getScrollDelta, and removed constants for default container width and height.
    Changes in build 412 (2009/04/10)
        * API CHANGE: DisplayObjectContainerController methods processCopyEvent, processCutEvent, processPasteEvent, processSelectAllEvent collapsed into a single processEvent that handles all these basic events. Added to ISelectionManager a new function, processEvent for handling these same events in the SelectionManager, and removed processSelectAll, which is no longer used. cutTextScrap and pasteTextScrap moved from ISelectionManager to IEditManager, since these are editing operations.
    Build 411, Fri Apr 10 2009
    Changes in build 411 (2009/04/09)
        * Fixed a bug where noFocus selection format was not being set on re-activation
        * API CHANGES. These functions in IFlowComposer were renamed:
              o updateContainer -> updateToController
              o updateAllContainers -> updateControllers
              o composeContainer -> composeToController
              o composePosition -> composeToPosition
        * API CHANGE: Changing name of TextFlow.hostTextLayoutFormat to hostFormat
    Changes in build 410 (2009/04/08)
        * Fix bug where leading info used for composing the next line was being saved prematurely, causing incorrect layout if the current line needed to be composed in multiple passes.
    Build 409, Tue Apr 7 2009
    Changes in build 409 (2009/04/07)
        * Fix bug where clicking on container when height or width NaN doesn't work. When measuring, transparent hit detect region wasn't being redrawn to correct size after composition.
        * API CHANGE: Plain-text import/export changes. Newline indicators exported based on setting in IConfiguration.newLineIndicator. On import, LF/CR/CR+LF are all recognized as new line indicators.
        * Compose to container size with scrolling on -- previously was composing to double composer size. This may flush out some invalid line bugs.
        * Fixed a bug with blockProgression="rl" and compositionWidth=NaN, lines were getting improperly clipped out so that no text appeared.
        * API CHANGE: Renaming functions in IFormatResolver. invalidateAllTargets is now invalidateAll, and invalidateTarget is now invalidate. resolveTextLayoutFormat is now resolveFormat.
        * API CHANGE: eventMirror on FlowLeafElement and SubParagraphGroupElement is now tlf_internal.
        * API CHANGE: Moving TextRange from the edit package to the elements package.
    Changes in build 406 (2009/04/02)
        * API CHANGE: Renaming DamageEvent.damageStart to damageAbsoluteStart.
        * API Change: IConfiguration.includePartialLine renamed to overflowPolicy. Defined new class OverflowPolicy that describes the different policies that can be used to control whether lines that fall at the end of the container are included in the container, or not.
    Changes in build 405 (2009/04/01)
        * API CHANGE: IFlowComposer.firstDamagePosition renamed to damageStartPosition.
        * API CHANGE: Rename GeometryUtil.getRangeBounds to GeometryUtil.getHighlightBounds.
        * API CHANGE: ParagraphElement.getText now takes an additional optional parameter that specifies the terminator for the paragraph. By default, this is the Unicode paragraph terminator character (\u2029), but you can make it whatever you want, including a simple newline by passing a String for the paragraphTerminator. This change is backwards compatible for current callers of getText().
        * Fix clipping problem when text is placed above the container (6 lines aligned verticalAlign = bottom in a space that fits 4 lines).
    Changes in build 404 (2009/03/31)
        * Updating typgraphic case --Markup and API Change-- Now uses a new class TLFTypographicCase, and has different options. Support for "title" and "caps" dropped. Use TLFTypographicCase with TLF in preference to flash.text.engine.TypographicCase. "smallCaps" renamed to "capsToSmallCaps". "capsAndSmallCaps" renamed to "lowercaseToSmallCaps". Also made AUTO the default setting for kerning, which matches FXG spec.
    Changes in build 403 (2009/03/30)
        * format Markup Changes:
              o <TextLayoutFormat> now <format>
              o When referring to a format id, don't use brackets. So this:
                <TextLayoutFormat id="english" locale="en" fontFamily="Minion Pro"/>
                <p marginBottom="15" ><span format="{english}">This text is supposed to be in Minion Pro via a named character attribute</span></p>
                Is now this:
                <format id="english" locale="en" fontFamily="Minion Pro"/>
                <p marginBottom="15" ><span format="english">This text is supposed to be in Minion Pro via a named character attribute</span></p>
        * API Changes:
              o Rename FlowElement.textLayoutFormat -> format
              o Rename FlowElement.computedTextLayoutFormat -> computedFormat
              o Rename IContainerController.textLayoutFormat -> format
              o Rename IContainerController.textLayoutFormat -> computedFormat
              o Rename DisplayObjectContainerController.textLayoutFormat -> format
              o Rename DisplayObjectContainerController.textLayoutFormat -> computedFormat
    Changes in build 402 (2009/03/27)
        * verticalAlign of "middle" or "bottom" will now align to the compositionHeight (or compositionWidth in vertical text) even if the height of the text exceeds the compositionHeight. This means that lines that don't fit may be get pushed above the box, or (for middle) pushed both above and below. It also means that all lines will forced to compose to the end, so it will be quite slow to use verticalAlign in large text flows. Made some corresponding fixes to scrolling to make it work with text off the start of the container. Added some new test cases to exercise this functionality in all the different alignment settings.
        * Scrolling fixes for next/previous line with arrow keys. Fix a bug where the arrow key would move to the end of the line if the line required composition (e.g., the line was not previously in view). Also fixed a bug when scrolling up by a line where it would scroll down instead.
        * doOperation used to return an SelectionState, but with the exception of two places that were using it internally, all external callers only checked to see if it was null or not. null was being used to indicate failure, or nothing changed, which means that the operation is not placed on the undo stack. Now it returns a Boolean, true for success, false for failure. There may be further changes in this area to make FlowOperations simpler.
    Changes in build 397 (2009/03/20)
        * Made DisplayObjectContainerController's and FlowElement's TextLayoutFormat properties read/write (used to be write-only).
        * Merge ContainerControllerBase class into DisplayObjectContainerController.
        * Mark TextFlow class as final
    Changes in build 396 (2009/03/19)
        * Fix RTE in StandardFlowComposer.releaseLines
        * Fix possible source of the RTE on null reference from findFirstAndLastVisibleLines in ContainerControllerBase.
    Changes in build 394 (2009/03/17)
        * Fix issue with changes made in StatusChangeEvent to embedded graphics by blocking recursive composition. Bug 2298043
        * Add IFlowComposer.composeInProcess property.
        * Fixed problem where first part of a link could not be replaced by a new link. New code allows partial replacement of a link element with a selection which starts at the first character.
        * Fixed a problem where the cursor was getting set to the I-beam, and wouldn't set back.
    Changes in build 393 (2009/03/16)
        * Fix a bug where keyboard navigation with linked containers was causing a scroll because it was trying to scroll to a position not in the container.
    Changes in build 392 (2009/03/13)
        * Removed optimization that was preventing scrolling in the logical width direction if scrolling in the logical vertical direction was turned off.
        * Removed the container-level mouseMove and rollOver handlers which were changing the link state. These are now part of the LinkElement, and added only when they are needed.
    Changes in build 390 (2009/03/11)
        * Fix for application of attributes to a point selection where only the last attribute would be applied. New code applies all attributes applied to the point.
        * IContainerController.contentWidth (or contentHeight in vertical text) is now based on the actual text width, not the unjustified text width. This fixes some problems where scrolling wasn't working correctly because the reported width of the text was greater than the compositionWidth, but lines were wrapped. It does mean that to get the unjustified width you will have to set the textAlign to something other than "justify", recompose, and then get the resulting width.
        * Fix for unintended scroll when at the end of a TextFlow.
        * Fix for RTE when dragging over text generated from a factory, or non-TLF TextLines.
        * Changes for alignment and measurement. You can now set NaN for compositionWidth or compositionHeight, and TLF will compose and use the generated contentWidth or contentHeight for alignment, scrolling, etc. The composer now generates a topLeft for the bounds, so you can make a full "content bounds" using contentLeft, contentTop, contentWidth, and contentHeight.Note that this is logical bounds and not inked bounds, so there are some circumstances where ink will not fit in the content bounds.Fixed bugs in how the factory was doing vertical alignment that caused it to be a few pixels off.Fixed some incosistencies between how the standard flow composer worked and how the factory's simple composer works -- composition results should now be more uniform. Added a new test program, MeasurementGrid, for testing all this. It's still a work in progress.
    Changes in build 388 (2009/03/09)
        * Fixed issue where applying link or TCY to the last span of a paragraph caused a dangling span to remain with the para terminator.
        * Fixed issue where text would go into a link when it was the last element in a paragraph. Newly typed text now goes into a new span when the selection marker is at the last index.
    Changes in build 386 (2009/03/06)
        * Fixed issue with placement of underline and strikethrough on inline images.
        * Fixed placement of underline and strikethrough on text which has a baseline shift applied to it.
    Changes in build 385 (2009/03/04)
        * Combined SWC 'textLayout.swc' now included in the libs directory of the build. This includes everything from textLayout_core, textLayout_edit, and textLayout_conversion.
        * Combined RSLs now included in the rsl directory of the build. Both an unsigned SWF and signed SWZ are created. These include everything from textLayout_core, textLayout_edit, and textLayout_conversion.
    Changes in build 382 (2009/03/02)
        * Fix issue with composing a TextFlow containing just an empty ParagraphElement.
        * TextLineFactory will generate lines that included InlineGraphics whose source is a "class" - normally an embedded graphic.
        * Expose eventMirrors - use FlowElement.getEventMirror function to access the eventMirror.
    Changes in build 381 (2009/02/27)
        * Fixed issue with graphic assigned to ILG getting the wrong sizing.
        * Factory instance functions renamed to textLinesFromString and textLinesFromTextFlow. Static functions renamin unchanged.
    Changes in build 380 (2009/02/26)
        * Made backgroundColor work with TextLineFactory. This required an API change - the callback to the factory now must take a DisplayObject as its parameter, since it won't always be passed TextLines. Also, the background shapes themselves no longer include leading, so they do not exactly coincide with the selection bounds. This was another change to support calculating the shapes during composition as opposed to afterward. Also added a snapshot test as part of FactoryImportTest that uses backgroundColor, in addition to updating the existing unit tests.
    Changes in build 379 (2009/02/25)
        * Fixed for multiple containers ( we were getting incorrect textLength in the containers), as well as a fix that forces scrollToPosition to compose if the text isn't composed yet.
        * Fix so that we scroll to the active position of the selection after we extend the selection with a keyboard event. Also fixed some of the TextRangeUtil functions used for nextLine, etc. to make sure text is composed through selection before processing that depends on composition results.
        * Plain text import now consistently converts \r to space; previously it was converting only the first one. Still not clear what correct behavior should be.
    Changes in build 377 (2009/02/23)
        * Fix bug with importing trailing empty div elements.
    Changes in build 374 (2009/02/18)
        * Added support for TextField-style leading. A new leading model value allows lineHeight to be interpreted as the distance of line's ascent from the previous line's descent. Further, lineHeight can be negative. which specifies the criteria for truncation, the string used to indicate truncation and the format for this string.
    Changes in build 372 (2009/02/16)
        * Added "enableAccessibility" property to IConfiguration, defaults to false. Allows clients to avoid paying price for TextAccImpl objects unless needed.
        * Added support for truncation for text composed using TextLineFactory. The TextLineFactory methods now take a truncation options parameter, which specifies the criteria for truncation, the string used to indicate truncation and the format for this string.
    Changes in build 371 (2009/02/13)
        * Fixed a number of bugs relating to scrolling by line.
        * Measurement changes. Changed the way contentHeight and contentWidth are calculated, now they reflect the size of the text, regardless of alignment. Eliminated unjustifiedContentHeight and unjustifiedContentWidth; use contentHeight and contentWidth instead.
        * Fix RTE in damage when we try to damage back one line, for textFlow that doesn't have any leaf nodes.
        * Changed InlineGraphicElement so that GraphicElements (and the TextBlocks they are part of) don't get released. Fixes RTE on null pointer in places where we access the GraphicElement.
        * Fix bug deleting all of the last Span of a paragraph, plus some of the following paragraph.
    Changes in build 370 (2009/02/12)
        * Removed textFlow property from CompositionCompletionEvent. Use event.target to get to the TextFlow.
    Changes in build 369 (2009/02/11)
        * Fix issues in usage of hostTextLayoutFormat
        * Fix FXG export to not export styles with value "inherit"
        * lineBreak property no longer inherits by default
    Changes in build 368 (2009/02/10)
        * Fix for RTE that happens after cancelling an operation (calling preventDefault on a FlowOperationEvent).
    Changes in build 367 (2009/02/09)
        * ported to Flex 4.0.0.4836. All SWCs now build with this SDK.
    Changes in build 366 (2009/02/06)
        * FlowGroupElement addChild, addChildAt and replaceChildren methods now automatically delete new elements from any existing parents. Previously the code would test for parent on new elements and throw.
        * mxmlChildren FlowElement property which is normally used for mxml compilation of TextFlow objects now always deletes existing children
        * Fix a memory leak issue with the TextLayoutFormat cache
        * Fix cascade bug with non-inheriting attributes getting inherited
    Changes in build 365 (2009/02/05)
        * Changed TextLayoutFormat.backgroundColor to allow setting value of "transparent" (now the default). Because of this new value for backgroundColor, backgroundAlpha now defaults to 1.
    Changes in build 364 (2009/02/04)
        * Performance improvement for handling of TextFlow.hostTextLayoutFormat. The code now assumes that once set by the client the supplied object won't be changed. This avoids a copy.
    Changes in build 363 (2009/02/03)
        * Performance work. Remove getCanonical from TextLayoutFormat.
        * Fix for RTE cancelling SplitParagraphOperation.
        * Fixing some float bugs.

    Try searching discussions--see: http://discussions.apple.com/thread.jspa?threadID=684662
    only caveat is link is dated-I googled for newer...
    MacBook Pro 17" Mac mini (Intel)   Mac OS X (10.4.8)  

Maybe you are looking for