[svn:fx-3.x] 10415: Fix the defaultButton bug in FocusManager

Revision: 10415
Author:   [email protected]
Date:     2009-09-18 15:27:59 -0700 (Fri, 18 Sep 2009)
Log Message:
Fix the defaultButton bug in FocusManager
QE Notes: None
Doc Notes: None
Bugs: SDK-21780
Reviewer: Corey
API Change: No
Is noteworthy for integration: No
tests: checkintests mustella/browser/FocusManager
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21780
Modified Paths:
    flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/managers/FocusManager.as

Similar Messages

  • Sure wish 2.0.1 fixed THE worst bug of all.  (Ring Tone Volume Issue)

    Man, I was so excited to get the 2.0.1 update because I was SURE that Apple would fix the biggest bug of them all with the update.
    Nope.
    Of course not.
    My ring tone volume level is still 100% tied to my iPod volume level.
    100% stupidity.
    Please fix it Apple. Please?

    Man, I was so excited to get the 2.0.1 update because I was SURE that Apple would fix the biggest bug of them all with the update.
    Nope.
    Of course not.
    My ring tone volume level is still 100% tied to my iPod volume level.
    100% stupidity.
    Please fix it Apple. Please?

  • When is there going to be an update to fix the voicemail bug.  Voicemails dont delete.  The calandar doesnt work good either., When is there going to be an update to fix the voicemail bug.  Voicemails dont delete.  The calandar doesnt work good either.

    When is there going to be an update to fix the voicemail bug.  Voicemails do not delete.  The outlookcalandar doesnt work good either.,  If i change things on calander they dont change in outlook?

    There is no "voicemail bug".  Mine works just fine.
    Try resetting your iPhone.  Hold the on/off and home buttons together for about 10 seconds till the Apple logo appears.  You will not lose any data.

  • [svn:fx-trunk] 10214: This fixes the problem that if two text components share the same textFlow there is an infinite loop involving updateDisplayList - damageHandler - invalidateDisplaylist - back to updateDisplayList.

    Revision: 10214
    Author:   [email protected]
    Date:     2009-09-13 07:33:58 -0700 (Sun, 13 Sep 2009)
    Log Message:
    This fixes the problem that if two text components share the same textFlow there is an infinite loop involving updateDisplayList -> damageHandler -> invalidateDisplaylist -> back to updateDisplayList.  The bug file was for TextArea which is RET but the same bug was in RichText as well.
    This example with a renderer exposed it because the typicalItem that is composed to figure out sizes and the actual first item in the list share the same textFlow.  It actually has nothing to do with useVirtualDisplay other than it was sharing a textFlow.
    It turns out that the TextFlowFactory dispatches damage events every time the textFlow is composed.  Unlike when the flowComposer is used, it always considers the flow damaged.  It was exacerbated by each of the two components having a damage handler for the same textFlow.
    The solution is to use the textFlow generation number.  In the damageHandler if the generation is the last known generation number, assume no changes, and return immediately from the damage handler.
    QE notes: There are 1 TextArea, 6 TextInput and 2 NumericStepper failuers, with or without my changes.  The common link seems to be DispatchKeyEvent.  Most were testing maxChar, displayAsPassword and restrict.  I tested these and they seem to be working correctly.
    Doc notes:
    Bugs: SDK-23002
    Reviewer: Gordon
    Tests run: checkintests, TextArea, TextInput and NumericStepper
    Is noteworthy for integration: no
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-23002
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/RichEditableText.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/RichText.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/RichEditable TextContainerManager.as

    Revision: 10214
    Author:   [email protected]
    Date:     2009-09-13 07:33:58 -0700 (Sun, 13 Sep 2009)
    Log Message:
    This fixes the problem that if two text components share the same textFlow there is an infinite loop involving updateDisplayList -> damageHandler -> invalidateDisplaylist -> back to updateDisplayList.  The bug file was for TextArea which is RET but the same bug was in RichText as well.
    This example with a renderer exposed it because the typicalItem that is composed to figure out sizes and the actual first item in the list share the same textFlow.  It actually has nothing to do with useVirtualDisplay other than it was sharing a textFlow.
    It turns out that the TextFlowFactory dispatches damage events every time the textFlow is composed.  Unlike when the flowComposer is used, it always considers the flow damaged.  It was exacerbated by each of the two components having a damage handler for the same textFlow.
    The solution is to use the textFlow generation number.  In the damageHandler if the generation is the last known generation number, assume no changes, and return immediately from the damage handler.
    QE notes: There are 1 TextArea, 6 TextInput and 2 NumericStepper failuers, with or without my changes.  The common link seems to be DispatchKeyEvent.  Most were testing maxChar, displayAsPassword and restrict.  I tested these and they seem to be working correctly.
    Doc notes:
    Bugs: SDK-23002
    Reviewer: Gordon
    Tests run: checkintests, TextArea, TextInput and NumericStepper
    Is noteworthy for integration: no
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-23002
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/RichEditableText.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/RichText.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/RichEditable TextContainerManager.as

  • [svn:osmf:] 13544: Attempt to fix the broken command line build.

    Revision: 13544
    Revision: 13544
    Author:   [email protected]
    Date:     2010-01-15 17:13:13 -0800 (Fri, 15 Jan 2010)
    Log Message:
    Attempt to fix the broken command line build.
    Modified Paths:
        osmf/trunk/apps/samples/framework/DynamicStreamingSample/DynamicStreamingSample-build-con fig.xml

    If there was a magic bullet to keeping clients healthy, then keeping clients healthy would not be an issue.
    However, ConfigMgr 2012 does have a a built-in client health tool called ccmeval -- this is run using a scheduled task on client systems every day and does a very good job of keeping clients healthy.
    Using a task sequence or anything directly deployed by ConfigMgr won't work because its a catch-22: how is the ConfigMgr agent supposed to run a deployment if it or a dependent component is not healthy.
    Other things to keep clients healthy:
    - Don't give users local admin privileges.
    - Beat users that hard shutdown or reboot systems (this is IMO the number 1 cause of client health issues)
    - Get rid of XP
    - Use client startup script that supplements ccmeval
    Jason | http://blog.configmgrftw.com

  • [svn:osmf:] 13639: Attempt to fix the command line build.

    Revision: 13639
    Revision: 13639
    Author:   [email protected]
    Date:     2010-01-19 14:58:36 -0800 (Tue, 19 Jan 2010)
    Log Message:
    Attempt to fix the command line build.
    Modified Paths:
        osmf/trunk/apps/samples/framework/DynamicStreamingSample/DynamicStreamingSample-build-con fig.xml

    Hi,
    I am  new to this field.
    I imported the strobe media playback to my flash builder.
    I am getting the error
    unknown configuration variable 'swf-version'
    When i imported the strobe media playback in flash builder
    the ADDITIONAL COMPILER ARGUMENTS  in the projec>properties>actionscript compiler>
    was having value
    -swf-version=11 -define CONFIG::LOGGING true -define CONFIG::FLASH_10_1 true
    please help me out

  • [svn:fx-4.x] 14806: Fix the same mirroring bug in both mx: WindowedApplication and s:WindowedApplication.

    Revision: 14806
    Revision: 14806
    Author:   [email protected]
    Date:     2010-03-17 06:50:37 -0700 (Wed, 17 Mar 2010)
    Log Message:
    Fix the same mirroring bug in both mx:WindowedApplication and s:WindowedApplication.  When using air,  setActualSize is called before commitProperties/invalidateLayoutDirection so invalidateLayoutDirection needs preserve the width as well as mirror in _layoutFeatures.
    QE notes:
    Doc notes: None
    Bugs: SDK-25735, SDK-25880
    Reviewed By: Jason, Kevin
    Tests run: checkintests
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-25735
        http://bugs.adobe.com/jira/browse/SDK-25880
    Modified Paths:
        flex/sdk/branches/4.x/frameworks/projects/airframework/src/mx/core/WindowedApplication.as
        flex/sdk/branches/4.x/frameworks/projects/airspark/src/spark/components/WindowedApplicati on.as
        flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/core/UIComponent.as

  • Why is it takes Apple forever to fix the appleeventsd bug?

    There are hundreds of posts around the net about killing appleeventsd to fix the issue that prevents "open in finder" and it's been like that for months now... Why is it takes Apple forever to release a fix?
    Everybody's laughing at Microsoft's updates amount, but at least they are fixing the issues...
    Do you think Apple not aware of the issue? they don't think it's important enough? or they just don't care about technical issues in general?
    Should we contact them directly about stuff like that or is it just a waste of time?
    What's your experience\impression of OSX support?
    Thanks!

    http://www.apple.com/feedback/

  • [svn:fx-4.x] 15123: Fix for ASDoc bugs:

    Revision: 15123
    Revision: 15123
    Author:   [email protected]
    Date:     2010-03-29 17:46:28 -0700 (Mon, 29 Mar 2010)
    Log Message:
    Fix for ASDoc bugs:
    @see links are not working in the ASDoc of a style property
    @see links in a skinPart ASDoc are not visible
    Asdoc tool generates bad links for Vector. type, property detail section
    QE notes: None.
    Doc notes: None.
    Bugs: SDK-26034, SDK-26035, SDK-26036
    Reviewed By: Darrell
    Tests run: checkintests
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-26034
        http://bugs.adobe.com/jira/browse/SDK-26035
        http://bugs.adobe.com/jira/browse/SDK-26036
    Modified Paths:
        flex/sdk/branches/4.x/asdoc/templates/all-index.xslt
        flex/sdk/branches/4.x/asdoc/templates/class-files.xslt
        flex/sdk/branches/4.x/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGener ator.java

    Stope
    Mailing me ***
    Sent from my I phone

  • Fixing the Msvcr80 bug ?

    Along with hundreds (?) of other users, I too met a huge problem when I innocently allowed Apple to update my iTunes with the latest version (11.1.4).  But checking the Apple discussion forums, I found a recommendation by TuringtestII FIXED THE BUG COMPLETELY, per the procedure below:
    Go to Control Panel > Add or Remove Programs (Win XP) or Programs and Features (later)
    Remove all of these items in the following order:
    o                                               iTunes
    o                                               Apple Software Update
    o                                               Apple Mobile Device Support (if this won't uninstall move on to the next item)
    o                                               Bonjour
    o                                               Apple Application Support
    Reboot, download iTunes, then reinstall, either using an account with administrative rights, or right-clicking the downloaded installer and selecting Run as Administrator.
    The uninstall and reinstall process will preserve your iTunes library and settings, but ideally you would back up the library and your other important personal documents and data on a regular basis. See this user tip for a suggested technique.
    Please note:
    Some users may need to follow all the steps in whichever of the following support documents applies to their system. These include some additional manual file and folder deletions not mentioned above.
    HT1925: Removing and Reinstalling iTunes for Windows XP
    HT1923: Removing and reinstalling iTunes for Windows Vista, Windows 7, or Windows 8
    APPLE itself was completely unhelpful, but am indebted to TT2 for their excellent fix.  Time consuming, but worth the hassle once it's all done.

    I have to make an explanatory note:
    on my MAC the problem with screensharing occurs when scaling (Sreensharing / Preferences / Viewing) is off. So where is no need to delete the above mentioned file but to set scaling to "on".

  • How long till you slackers fix the clipboard bug in firefox?

    seriously im ditching firefox as of now for opera cuz no one seems to be interested in fixing the virtual private clipboard bug in firefox.
    It is nothing short of infuriating & frustrating!!!!!!!! CMON U SLACKERS!!!!

    Delete a possible user.js file and numbered prefs-##.js files and rename (or delete) the prefs.js file to reset all prefs to the default value including prefs set via user.js and prefs that are no longer supported in the current Firefox release.
    *http://kb.mozillazine.org/Preferences_not_saved
    *Help > Troubleshooting Information > Profile Directory: Show Folder (Linux: Open Directory; Mac: Show in Finder)

  • Why does Mozilla not fix the XULRunner bug?

    I'm loosing the will to use FF as this rate. It seems that XULRunner version conflicts have been around for a long time. Isn't it time to fix this once and for all.
    == This happened ==
    Every time Firefox opened
    == After update of Zone Alarm and re-boot ==
    == User Agent ==
    Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E)

    Assuming you mean something along the lines of:
    '''XULrunner Error: Platform version '1.9.x.x' is not compatible'''
    There are two possibilities, neither of which originate from Mozilla:
    1. "You have some security software that was locking files in the Firefox program folder or have some kind of file protection active and thus prevented the updater from replacing them." quoted from another thread. The solution is to just download the full installer from http://getfirefox.com and run it, you will not lose any user data like bookmarks or settings.
    2. You have '''Malware''' locking files in the same way. The solution is to battle it out for weeks with said malware until you give up and run http://wubi-installer.org

  • Frustrated with iCal 3--please fix the obvious bugs!

    I read that Apple actually looks at these posts, otherwise I would suffer in silence. So here goes...
    After adopting iCal for all of my calendar needs and being able to rely on version 2 to work, I upgraded to Leopard and iCal 3. Now, I am frustrated with obvious bugs and very worried about the integrity of my calendar data (which is EXTREMELY important).
    Some things that do not work or seem to work sporadically in iCal 3:
    1. Delete events/to-do's after n days. Nothing. And why is this option applied globally rather than to specific calendars?
    2. Publish calendars upon modification. Usually works; sometimes quits for no apparent reason.
    3. Reliable syncing (OK, maybe this is an iSync problem).
    Other frustrations:
    1. Very slow operation. Slow to create event, slow to edit event, slow to even change from month to month.
    2. Very slow or even crashes when I double-click on an event.
    3. I seem to need to double-click after I enter an event to fill in all the info I want.
    4. No easy way to archive (and restore) old events.
    Please, Apple, do not lose your focus on software excellence, as you pursue lucrative new markets! Your recent software releases (like iCal, iSync, AirDisk, TimeMachine, etc.) are beginning to remind me of, gasp, Microsoft. They almost work.
    Excuse me for venting on this forum.

    I have all of the same issues Jeff. What gives?? This needs immediate fix.

  • Fixing the screensharing bug

    Hello everybody,
    if there are problems with screensharing after installing SL, the following workaround may help:
    Look für the file "com.apple.ScreenSharing.plist" (in your Library/Preference-Folder) and delete it.
    Start Screensharing via Finder and click "Share Screen" - the other MACs Screen will appear immediately (without the black-or white screen failure). Configure the display options to your liking.
    Screensharing still doesn't work using the screensharing.app (within the utilites folder).
    Let's hope Apple will provide an update / bug fix soon.
    Heinz
    Message was edited by: Heinz-Th

    I have to make an explanatory note:
    on my MAC the problem with screensharing occurs when scaling (Sreensharing / Preferences / Viewing) is off. So where is no need to delete the above mentioned file but to set scaling to "on".

  • Apple - PLEASE fix the graphical bug with Dock and Stacks! PLEASE!

    Using popular Mac games such as Diablo II, Freeverse's Wingnuts, Ambrosia's Aperion, and Blitwise's Super DX-Ball (as well as a LOT more) results in a common graphical glitch with the Dock and stacks, making fan stacks totally useless until I restart my iMac. Killing and relaunching the Dock doesn't fix it. Only restarting my Mac temporarily sorts it out. This is a highly annoying bug most often set off by games that Apple STILL hasn't fixed as of 10.5.3. So I let every developer (who I do not blame, BTW) know whose product results in this bug, in the hope they will apply pressure to Apple. Leopard has been the buggiest release since 10.1 IME and Apple is taking there sweet time about crushing such crippling bugs. Suffice to say it's really ******* me off.
    Here is a screenshot from another 24" iMac afflicted by this bug after running a game:
    <http://img231.imageshack.us/img231/5324/corrupteddockandmenuletpk1.png>
    Notice the open stack is just grey bars. The icons and names are not
    showing.
    Regards,
    Jamie Kahn Genet

    Hi Wizardling
    These forums are User to User technical forums Apple employees do not often read these forums. You can do 1 of two things.
    1. Send feedback to Apple via http://www.apple.com/feedback or
    2. Sign up for a free developer account and open a bug report with Apple through http://bugreporter.apple.com
    Hope this helps
    J.C

Maybe you are looking for