[svn:fx-trunk] 11319: Allow for resizing of sub-apps after they initialize

Revision: 11319
Author:   [email protected]
Date:     2009-10-30 11:42:01 -0700 (Fri, 30 Oct 2009)
Log Message:
Allow for resizing of sub-apps after they initialize
QE Notes: Two Mustella Tests need updating:
MP_Controls_Tests2:MP_ComboBox_closeOnMouseDown_untrusted
MP_Controls_Tests2:MP_ComboBox_closeOnMouseDownOutside_untrusted
The new sub-app resize closes the dropdown. Probably have to wait a bit longer before opening the dropdown
Doc Notes: New API in ISystemManager
Bugs: SDK-23892
Reviewer: Darrell
API Change: yes
Is noteworthy for integration: No
tests: checkintests mustella/MarshallPlan
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23892
Modified Paths:
    flex/sdk/trunk/frameworks/projects/airframework/src/mx/managers/WindowedSystemManager.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/ISystemManager.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/SystemManager.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/systemClasses/MarshallingSup port.as

After commenting out nearly everything in the above autostart.sh, I also found that using . $GLOBALAUTOSTART will also cause the same issue. Once I commented that out, SLiM logged me into Openbox just fine.
Thanks alexandrite.

Similar Messages

[svn:fx-trunk] 10008: Fix for SDK-23005 performance regression after BlendMode changes

Revision: 10008
Author:   [email protected]
Date:     2009-09-04 00:10:00 -0700 (Fri, 04 Sep 2009)
Log Message:
Fix for SDK-23005 performance regression after BlendMode changes
Fix: make sure GE and Group DisplayObject sharing works in the blendMode="auto" case.
QE notes: None
Doc notes: None
Bugs: SDK-23005
Reviewer: Evtim
Tests run: checkintests, basictests
Is noteworthy for integration: Yes, blendMode behavior affects Catalyst
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23005
    http://bugs.adobe.com/jira/browse/SDK-23005
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Group.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/GraphicEleme nt.as

FYI - This regression has been filed here: http://bugs.adobe.com/jira/browse/SDK-31989

I changed my Apple ID email address yesterday and now my IPhone 4 and my Ipod 5 will not allow me to upload any apps as they both still show my old email address. How do I change the email address on the devices???

I changed my Apple ID email address yesterday and now my IPhone 4 and my IPod 5 will not allow me to upload any apps. When it asks for my Apple Password it still shows my old email address. How do I change the IPhone and IPod to recognize the new email address????

Hello there, emsariel.
The following Knowledge Base article offers up some great information in regards to the issue you are describing:
iOS 7: If you're asked for the password to your previous Apple ID when signing out of iCloud
http://support.apple.com/kb/ts5223
Thanks for reaching out to Apple Support Communities.
Cheers,
Pedro.

[svn:fx-trunk] 6642: Fix for bug when doing a Resize and a transform effect in a Parallel transition with autoCenterTransform =true.

Revision: 6642
Author:   [email protected]
Date:     2009-05-05 08:18:04 -0700 (Tue, 05 May 2009)
Log Message:

Revision: 6642
Author:   [email protected]
Date:     2009-05-05 08:18:04 -0700 (Tue, 05 May 2009)
Log Message:

[svn:fx-trunk] 12994: * Fixes for two issues that were showing up in FB.

Revision: 12994
Revision: 12994
Author:   [email protected]
Date:     2009-12-16 06:44:45 -0800 (Wed, 16 Dec 2009)
Log Message:
Fixes for two issues that were showing up in FB.
QE notes:
Doc notes:
Bugs: SDK-24669, SDK-24686
Reviewer: Corey
Cycloner: George
Tests run: checkintests
Is noteworthy for integration: yes, fixes two FB issues.
Code-level description of changes:
modules/compiler/src/java/flex2/tools/PreLink.java
    Modified postRun() to swap in the root CompilationUnit's Logger
    when validating it's StyleContainer. This allows the warnings
    from StylesContainer.validate() to be persisted across incremental
    compilations. This fixes SDK-24686.
modules/compiler/src/java/flex2/compiler/Source.java
    Made getLogger() public, so it could be called from PreLink.
modules/compiler/src/java/flex2/compiler/CompilerAPI.java
    Modified compile() to check forcedToStop() after each PreLink
    batch. This fixes SDK-24669.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24669
    http://bugs.adobe.com/jira/browse/SDK-24686
    http://bugs.adobe.com/jira/browse/SDK-24686
    http://bugs.adobe.com/jira/browse/SDK-24669
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerAPI.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/Source.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/linker/CULinkable.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/tools/PreLink.java

[svn:fx-trunk] 11602: Fix for Button tooltips.

Revision: 11602
Author:   [email protected]
Date:     2009-11-09 22:35:11 -0800 (Mon, 09 Nov 2009)
Log Message:
Fix for Button tooltips. TextBase dispatches an event when _isTruncated is set through the setIsTruncated() function. This allows ButtonBase to listen for the event and set the tooltip as necessary. If an explicit tooltip is set, then ButtonBase will not set a tooltip.
QE notes: No
Doc notes: No
Bugs: SDK-22260, SDK-23474, SDK-23657
Reviewer: Evtim
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-22260
    http://bugs.adobe.com/jira/browse/SDK-23474
    http://bugs.adobe.com/jira/browse/SDK-23657
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Label.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/RichText.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/ButtonBase.a s
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/TextBase.as

[svn:fx-trunk] 5386: * Fix for Flex Builder JUnit tests.

Revision: 5386 Author: [email protected] Date: 2009-03-18 08:03:11 -0700 (Wed, 18 Mar 2009) Log Message: ----------- * Fix for Flex Builder JUnit tests. tests Passed: checkintests, performance testsuite Needs QA: YES Needs DOC: NO API Change: NO Reviewer: Pete F. Code-level description of changes: compiler/CompilerAPI.java Changed the deleted Map used in validateCompilationUnits() and some of it's helper methods from <String, Source> to <QName, Source>. This allows us to track when a definition is deleted from one SWC in the library path and then added by another SWC in the library path. All the definitions dependant on the definition need to be recompiled and we were missing this before. Specifically, the Flex Builder JUnit tests were switching from airglobal.swc to playerglobal.swc midstream. As a result, we weren't recompiling classes that depended on flash.display.DisplayObjectContainer, because it looked like it hadn't been deleted. Modified Paths: -------------- flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerAPI.java flex/sdk/trunk/modules/compiler/src/java/flex2/tools/oem/Library.java

[svn:fx-trunk] 12962: Fix for ASDoc not saving event type for [Bindable] metadata tag

Revision: 12962
Revision: 12962
Author:   [email protected]
Date:     2009-12-15 10:32:23 -0800 (Tue, 15 Dec 2009)
Log Message:
Fix for ASDoc not saving event type for metadata tag
QE notes: None.
Doc notes: None
Bugs: SDK-24706
Reviewed By:Corey
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24706
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 3: NVIDIA HDMI [NVIDIA HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
Which correspondents fine with the
device "hw:0,3"
in my mpd.conf alsa section.
Also sound worked fine withh this config before I started installing ffmpeg-svn and alikes
hokasch:
I tried changing the mixer to "Master" but that did not change much.

[svn:fx-trunk] 7473: Fix for 'ant asdoc' does not work.

Revision: 7473
Author:   [email protected]
Date:     2009-06-01 12:09:26 -0700 (Mon, 01 Jun 2009)
Log Message:
Fix for 'ant asdoc' does not work.
It should now work from both svn and package zip.
Bugs: SDK-15306
QE Notes: None.
Doc Notes: None.
tests: checkintests
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-15306
Modified Paths:
    flex/sdk/trunk/asdoc/build.xml
    flex/sdk/trunk/build.xml

[svn:fx-trunk] 13136: Fix for FLEXENT-1196 ( Replay of click on NavigatorContent does not close the combobox)

Revision: 13136
Revision: 13136
Author:   [email protected]
Date:     2009-12-21 17:40:28 -0800 (Mon, 21 Dec 2009)
Log Message:
Fix for FLEXENT-1196 (Replay of click on NavigatorContent does not close the combobox)
We need not record OPEN event when it is triggered from a KeyBoard event that types a character. Replaying the type event would automatically open the drop down.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FLEXENT-1196
Modified Paths:
    flex/sdk/trunk/frameworks/projects/automation_spark/src/spark/automation/delegates/compon ents/SparkComboBoxAutomationImpl.as
    flex/sdk/trunk/frameworks/projects/automation_spark/src/spark/automation/delegates/compon ents/supportClasses/SparkDropDownListBaseAutomationImpl.as

[svn:fx-trunk] 10898: Fix for a bug: After playing a hide effect, a window wouldn't be visible again.

Revision: 10898
Author:   [email protected]
Date:     2009-10-06 13:54:04 -0700 (Tue, 06 Oct 2009)
Log Message:
Fix for a bug: After playing a hide effect, a window wouldn't be visible again.
The issue here is that all effects that occur because of HIDE end up calling setVisible() (see EffectManager.effectEndHandler). Window/WindowedApplication was basically left with two concepts of setVisible...the displayObject one and the native application one, and they were out of synch. So setting visible=true on the window wasn?\226?\128?\153t calling setVisible(true) which controls the display object visibility. Now instead of doing our work in the visible setter, we override setVisible() and do it in there.
QE notes: -
Doc notes: -
Bugs: SDK-23263
Reviewer: Darrell
Tests run: checkintests, Rob ran mustella window/windowedapplication
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23263
Modified Paths:
    flex/sdk/trunk/frameworks/projects/airframework/src/mx/core/Window.as
    flex/sdk/trunk/frameworks/projects/airframework/src/mx/core/WindowedApplication.as
    flex/sdk/trunk/frameworks/projects/airframework/src/spark/components/Window.as
    flex/sdk/trunk/frameworks/projects/airframework/src/spark/components/WindowedApplication. as

I run Suse 9.1 Linux, and Suse has a package called lmsensors which by default on my machine gives readings like this:
Code: [Select]
temp1: +27°C (high = +0°C, hyst = +22°C) sensor = thermistor
temp2: +41.0°C (high = +80°C, hyst = +75°C) sensor = PII/Celeron diode
Now that 41C is pretty high for an idle AMD643000+ running at 1000Mhz, 1.08V. Too high, I would say. temp 1 in this case is the SYS temp, temp2 is the CPU temp.
Now, using lmsensors I can duplicate your little trick and tell it that temp 2 is in fact a 3904 transistor. Having done this can I get readings like this:
Code: [Select]
temp1: +27°C (high = +0°C, hyst = +22°C) sensor = thermistor
temp2: +16.0°C (high = +80°C, hyst = +75°C) sensor = 3904 transistor
Problem is, I'm not sure that the sensor is actually a 3904 transistor! The number's lower, but I was pretty sure that the sensor in the AMD64 is in fact a diode. Also, surely the CPU temp can't actually be that much lower than the SYS temp.
So, I think your fix succeeds in giving lower temps and that's great in that it will tell your system software that the CPU is not overheating, but I don't think it's the solution to high temp reporting. Anyway, as you say, its a solution for people who can't run with system shutdowns due to bogus high temps.
I've been looking at these temp issues with the MSI K8T, and I was thinking the problem was simply a miscalibration. The Winbond sensor chip on my board (maybe the K8N is the same, maybe not) has a sensor temp offset that gets added to the temp coming from the sensor. On the K8T this number is +54C. Funny number I know, but I've "fixed" the problem while I wait for a real bios fix on the K8T by simply reducing this offset to give me a CPU temp that matches SYS temp when idle. This enables cool'n'quiet fan control to work properly on my system, which is my main practical concern.

[svn:fx-trunk] 12982: Fix for issue with exposing accessible names for combobox list items

Revision: 12982
Revision: 12982
Author:   [email protected]
Date:     2009-12-15 20:44:23 -0800 (Tue, 15 Dec 2009)
Log Message:
Fix for issue with exposing accessible names for combobox list items
QE notes: none
Doc notes: none
Bugs: n/a
Reviewer: Gordon
Tests run: checkintests
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/accessibility/ComboBoxAccImpl.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/accessibility/ListBaseAccImpl.as

Add this to the end of your nav p CSS selector at Line 209 of your HTML file, after 'background-repeat...':
margin-bottom: -2px;
Your nav p will then look like this:
nav p {
          font-size: 90%;
          font-weight: bold;
          color: #FFC;
          background-color: #090;
          text-align: right;
          padding-top: 5px;
          padding-right: 20px;
          padding-bottom: 5px;
          border-bottom-width: 2px;
          border-bottom-style: solid;
          border-bottom-color: #060;
          background-image: url(images/background.png);
          background-repeat: repeat-x;
          margin-bottom: -2px;

[svn:fx-trunk] 10229: Fixes for some transform effects problems.

Revision: 10229
Author:   [email protected]
Date:     2009-09-14 08:43:43 -0700 (Mon, 14 Sep 2009)
Log Message:
Fixes for some transform effects problems.
- We were not animating the postLayout properties in some cases where we should have, effectively pinning the object in place. We now animate those properties whenever applyChangesPostLayout is true.
- A copy/paste error meant that we did not animate the scaleZ property in cases where we should have.
- A problem in the transform code means that using a null transform center is not the same as a transform center which uses the transformX/Y/Z properties of the target object. We now force the creation/use of a transform center in all cases to avoid that problem.
QE notes: This breaks about a dozen tests in the transform effects area, but I believe the new results are correct and the tests/bitmaps should be changed.
Doc notes: None
Bugs: sdk-23177
Reviewer: Hans
Tests run: checkintests, Mustella transform effects
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-23177
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/AnimateTransform.as

[svn:fx-trunk] 11188: In 'for each (var in)' statements, defend against undefined entries in the AysncListView/ pendingResponders sparse array.

Revision: 11188
Author:   [email protected]
Date:     2009-10-27 12:16:37 -0700 (Tue, 27 Oct 2009)
Log Message:
In 'for each (var in)' statements, defend against undefined entries in the AysncListView/pendingResponders sparse array.
QE notes:
Doc notes: none
Bugs: sdk-23831, sdk-23832
Reviewer: Alex
Tests run:
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-23831
    http://bugs.adobe.com/jira/browse/sdk-23832
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/collections/AsyncListView.as

You are welcome. I'm glad you got it back up.
(1) You say you did the symbolic link. I will assume this is set correctly; it's very important that it is.
(2) I don't know what you mean by "Been feeding the [email protected] for several weeks now, 700 emails each day at least." After the initial training period, SpamAssassin doesn't learn from mail it has already processed correctly. At this point, you only need to teach SpamAssassin when it is wrong. [email protected] should only be getting spam that is being passed as clean. Likewise, [email protected] should only be getting legitimate mail that is being flagged as junk. You are redirecting mail to both [email protected] and [email protected] ... right? SpamAssassin needs both.
(3) Next, as I said before, you need to implement those "Frontline spam defense for Mac OS X Server." Once you have that done and issue "postfix reload" you can look at your SMTP log in Server Admin and watch as Postfix blocks one piece of junk mail after another. It's kind of cool.
(4) Add some SARE rules:
Visit http://www.rulesemporium.com/rules.htm and download the following rules:
70sareadult.cf
70saregenlsubj0.cf
70sareheader0.cf
70sarehtml0.cf
70sareobfu0.cf
70sareoem.cf
70sarespoof.cf
70sarestocks.cf
70sareunsub.cf
72sare_redirectpost
Visit http://www.rulesemporium.com/other-rules.htm and download the following rules:
backhair.cf
bogus-virus-warnings.cf
chickenpox.cf
weeds.cf
Copy these rules to /etc/mail/spamassassin/
Then stop and restart mail services.
There are other things you can do, and you'll find differing opinions about such things. In general, I think implementing the "Frontline spam defense for Mac OS X Server" and adding the SARE rules will help a lot. Good luck!

[svn:fx-trunk] 13257: Fix for @inheritDoc not working on a setter, but works on a getter

Revision: 13257
Revision: 13257
Author:   [email protected]
Date:     2010-01-04 10:49:13 -0800 (Mon, 04 Jan 2010)
Log Message:
Fix for @inheritDoc not working on a setter, but works on a getter
QE notes: None.
Doc notes: None
Bugs: SDK-24727
Reviewed By: Paul
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24727
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/ClassTable.java

steabert wrote:
Hi,
I had a similar problem with my Dell Latitude E4310, and apparently also the E6410, E6510.
The solution for me was to add the following line to /etc/modprobe.d/modprobe.conf:
options snd-hda-intel model=dell-s14
I tried that, unfortunately it does not work with this chipset. I do get a different set of channels though but it still cannot record anything. Maybe this chipset is too "new" for alsa. The latest release dates back from the end of January. Support for it is explicitly stated in the changelog to 1.0.24 but perhaps the recording part of it slipped through the cracks. ALSA bug tracking system seems quite closed.

[svn:fx-trunk] 11319: Allow for resizing of sub-apps after they initialize

Similar Messages

Maybe you are looking for