[svn:fx-trunk] 10817: Fix a deeplinking problem in IE7

Revision: 10817
Author:   [email protected]
Date:     2009-10-02 09:20:31 -0700 (Fri, 02 Oct 2009)
Log Message:
Fix a deeplinking problem in IE7
QE Notes: None
Doc Notes: None
Bugs: SDK-17197
Reviewer: Corey
API Change: No
Is noteworthy for integration: No
tests: checkintests
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-17197
Modified Paths:
    flex/sdk/trunk/templates/swfobject/history/history.js

Similar Messages

[svn:fx-trunk] 11707: Fix incremental compilation problem with styles.

Revision: 11707
Author:   [email protected]
Date:     2009-11-12 10:52:49 -0800 (Thu, 12 Nov 2009)
Log Message:
Fix incremental compilation problem with styles.
QE notes: None.
Doc notes: None.
Bugs: SDK-24173
Reviewer: Paul
Tests run: checkintests
Is noteworthy for integration: No.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24173
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/StylesContainer.java

You have used elements like header, footer, footer1 and nav without using the correct DOCTYPE declaration. Replace the first line of your code with
<!doctype html>
Also have a look here for other problems http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fhome.surewest.net%2Fstorytales%2F test%2Fforposting.html
After the above has been fixed, please come back here to fix the remaining problem(s)
Gramps

[svn:fx-trunk] 8452: - Fix flicker problem with constraint bound text that is being autoSized.

Revision: 8452
Author:   [email protected]
Date:     2009-07-08 08:38:32 -0700 (Wed, 08 Jul 2009)
Log Message:
- Fix flicker problem with constraint bound text that is being autoSized. If the remeasure is done in a 2nd pass you will see a flicker as all the objects are moved to accommodate the reflowed text.
- Fix data binding issue with text setter.
- Rework measure() to accommodate implicit autoSize.
If explicitWidth or widthInChars specified and explicitHeight or heightInLines specified, or for now, blockProgression != "tb", the text has fixed dimensions and is not auto-sized.
If no text and width specified, but no height, start at specified width and one line high and grow taller.
If no text and height specified, start at 1 char wide with the specified height and grow wider.
If neither width nor height specified, and toFit lineBreaks, start at explicitMaxWidth, or default maxWidth of 160, and grow taller.
If neither width nor height specified, and explicit lineBreaks width is unlimited and can grow taller.
These are further constrained by min/max Width and Height except in the case that explicitWidth or explicitHeight are specified.
- Change default maxWidth for RichText and SimpleText to 160 to match RET. Previously it was 10000. This is used for
text with toFit lineBreaks if a width isn't specified.
QA Notes: 12 or so TextGraphic tests fail because of the new default maxWidth.
Doc Notes:SDK-22014, SDK-21837
Reviewers: Gordon
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-22014
    http://bugs.adobe.com/jira/browse/SDK-21837
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/RichEditableText.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/GraphicEleme nt.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/RichEditable TextContainerManager.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/TextGraphicE lement.as
Added Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/RichEditable TextEditManager.as

You have used elements like header, footer, footer1 and nav without using the correct DOCTYPE declaration. Replace the first line of your code with
<!doctype html>
Also have a look here for other problems http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fhome.surewest.net%2Fstorytales%2F test%2Fforposting.html
After the above has been fixed, please come back here to fix the remaining problem(s)
Gramps

[svn:fx-gumbo_beta2] 10484: Fix for autoCenter problem when Move/ Resize effects are used.

Revision: 10484
Author:   [email protected]
Date:     2009-09-21 19:38:14 -0700 (Mon, 21 Sep 2009)
Log Message:
Fix for autoCenter problem when Move/Resize effects are used. autoCenterTransform calculates the center dynamically, using the current width/height of the target. This calculation can be one frame off if a Resize effect is running in parallel with the transform effect. Also, containers do their validation lazily, so they need to be forced to validate in order to have an up-to-date width/height. This fix addresses these problems by reordering the effects in a Parallel hierarchy to put the Resize effects (and composite effects containing Resize) at the front of the set of effects and by calling validateNow() on the target of a transform effect prior to calculating the transform center (if appropriate).
QE notes: None
Doc notes: None
Bugs: SDK-23306
Reviewer: Jason
Tests run: checkintests, Mustella spark/effects mx/effects, manual tests
Is noteworthy for integration: Yes
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23306
Modified Paths:
    flex/sdk/branches/gumbo_beta2/frameworks/projects/framework/src/mx/effects/effectClasses/ CompositeEffectInstance.as
    flex/sdk/branches/gumbo_beta2/frameworks/projects/framework/src/mx/effects/effectClasses/ ParallelInstance.as
    flex/sdk/branches/gumbo_beta2/frameworks/projects/spark/src/spark/effects/supportClasses/ AnimateTransformInstance.as

Dear Pallavi,
Very useful post!
I am looking for similar accelerators for
Software Inventory Accelerator
Hardware Inventory Accelerator
Interfaces Inventory
Customization Assessment Accelerator
Sizing Tool
Which helps us to come up with the relevant Bill of Matetials for every area mentioned above, and the ones which I dont know...
Request help on such accelerators... Any clues?
Any reply, help is highly appreciated.
Regards
Manish Madhav

[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] 6993: * Fixed a duplicate Bindable metadata bug that showed up with

Revision: 6993
Author:   [email protected]
Date:     2009-05-16 23:57:42 -0700 (Sat, 16 May 2009)
Log Message:
Fixed a duplicate Bindable metadata bug that showed up with
describeType().
tests Passed: checkintests
Needs QA: YES, just confirm the bug fix, please.
Needs DOC: NO
Bug fixes: SDK-21133
API Change: NO
Reviewer: Pete F.
Code-level description of changes:
BindableSecondPassEvaluator.java
    Modified moveMetaDataToNewDefinition() to no longer insert the new
    Bindable metadata into the definition's statement list, because
    prepMetaDataNode() already handles this.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21133
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/BindableSecondPassEva luator.java

I just noticed that for some reason the project is using an old path to my SVN repository. I recreated it and reimported the project but for some reason Xcode didn't realize that. I'm betting there's some little file somewhere that's causing my problem.

[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] 10866: Fix broken links in ASDoc comments for TLFTextInput. as and TextArea.as, and add OverrideBase.as to ASDoc output

Revision: 10866
Author:   [email protected]
Date:     2009-10-05 08:56:44 -0700 (Mon, 05 Oct 2009)
Log Message:
Fix broken links in ASDoc comments for TLFTextInput.as and TextArea.as, and add OverrideBase.as to ASDoc output
QE notes: -
Doc notes: -
Bugs: -
Reviewer: -
Tests run: - checkintests
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/states/OverrideBase.as
    flex/sdk/trunk/frameworks/projects/spark/src/mx/controls/TLFTextInput.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/TextArea.as

Sorry about that. I am not exactly sure where the problem is, but I know it takes place after I put the <nav> in (in the html portion). If I understand what I am learning, the CSS at the top will structure my html code so I would have thought the CSS tageting my nav would be the focus. Maybe it is a different section though.
CSS part:
nav p {
font-size: 90%;
color: #FFC;
text-align: right;
font-weight: bold;
background-color: #090;
padding-top: 5px;
padding-right: 20px;
padding-bottom: 5px;
border-top-width: 2px;
border-top-style: solid;
border-top-color: #060;
HTML part: (bold italic is the part I added)
<body>
<div class="container">
<div id="apDiv1"><img src="Lessons/images/butterfly-ovr.png" width="170" height="158" alt="GreenStart Logo"></div>
<header></header>
<nav>
    <p>Home | About Us | Contact Us</p>
</nav>
<div class="sidebar1">
    <ul class="nav">
      <li><a href="#">Green News</a></li>
      <li><a href="#">Green Products</a></li>
      <li><a href="#">Green Events</a></li>
      <li><a href="#">Green Travel</a></li>
      <li><a href="#">Green Tips</a></li>
    </ul>

[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:bz-trunk] 9665: Fix minor typo in errors.properties file.

Revision: 9665
Author:   [email protected]
Date:     2009-08-26 14:13:27 -0700 (Wed, 26 Aug 2009)
Log Message:
Fix minor typo in errors.properties file. Change "wilcard" to "wildcard" in the following error string.
10560=Attempt to subscribe to the subtopic, '''', on destination, '''', that does not allow wilcard subtopics failed.
Checkintests: passed
Modified Paths:
    blazeds/trunk/modules/common/src/flex/messaging/errors.properties
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/dynamicDestinat ions/subtopicsEnabledWildcardsNotAllowed.mxml

onearm wrote:
Svn revision 442 doesn't compile on Arch64:
[ 4%] [ 5%] Building CXX object src/CMakeFiles/guayadeque.dir/AlListBox.o
Building CXX object src/CMakeFiles/guayadeque.dir/ArListBox.o
In file included from /tmp/yaourt-tmp-gianluca/aur-guayadeque-svn/guayadeque-svn/src/guayadeque/Trunk/src/LastFMPanel.h:25,
from /tmp/yaourt-tmp-gianluca/aur-guayadeque-svn/guayadeque-svn/src/guayadeque/Trunk/src/MainFrame.h:27,
from /tmp/yaourt-tmp-gianluca/aur-guayadeque-svn/guayadeque-svn/src/guayadeque/Trunk/src/AlListBox.cpp:27:
/tmp/yaourt-tmp-gianluca/aur-guayadeque-svn/guayadeque-svn/src/guayadeque/Trunk/src/PlayerPanel.h:25:28: error: AutoScrollText.h: No such file or directory
[ 7%] Building CXX object src/CMakeFiles/guayadeque.dir/ArrayStringArray.o
[ 8%] Building CXX object src/CMakeFiles/guayadeque.dir/AudioScrobble.o
make[2]: *** [src/CMakeFiles/guayadeque.dir/AlListBox.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [src/CMakeFiles/guayadeque.dir/all] Error 2
make: *** [all] Error 2
Thanks for the bug report. It was a test i was doing but finally decided to not include it but left this line by error.
It have been fixed in svn 443.
Thanks again

[svn:fx-trunk] 12869: Fix FB-24801: Unable to run an application with AIR 3 .4 sdk

Revision: 12869
Revision: 12869
Author:   [email protected]
Date:     2009-12-11 14:50:26 -0800 (Fri, 11 Dec 2009)
Log Message:
Fix FB-24801: Unable to run an application with AIR 3.4 sdk
Ticket Links:
    http://bugs.adobe.com/jira/browse/FB-24801
Modified Paths:
    flex/sdk/trunk/modules/debugger/src/java/flash/tools/debugger/concrete/PlayerSessionManag er.java

I've fixed the problem!
I think the problem was in the way I was linking to the libraries. I ended up deleting all my hand made ANT settings and instead exporting the settings from my Flash Builder project, and just using those.
Full details in this article here, it saved my life: http://helpx.adobe.com/x-productkb/multi/compilation-results-flex-builder-flex.html

[svn:fx-trunk] 10578: Fix the SkinTest.mxml in the sparkTest project: use backgroundColor style as we don't have a property anymore.

Revision: 10578
Author:   [email protected]
Date:     2009-09-24 15:02:04 -0700 (Thu, 24 Sep 2009)
Log Message:
Fix the SkinTest.mxml in the sparkTest project: use backgroundColor style as we don't have a property anymore.
QE notes: None
Doc notes: None
Bugs: None
Reviewer: Evtim
Tests run: build
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/development/eclipse/flex/sparkTest/src/SkinTest.mxml

I finally found how to set a default skin to a custom component so that users of my component will not have to set again the skinClass value of my component.
You have to create a defaults.css file at the root of your library and tell the compiler to take it into account.
The remaining problem is about the compiler. There are some steps before success and they are a bit mysterious/unclear....
I found 2 or 3 blog articles explaining those steps but the compiler arguments to use are all differents in each article...
Here are the links I found:
http://www.unitedmindset.com/jonbcampos/2010/05/12/creating-custom-spark-components/
http://www.betadesigns.co.uk/Blog/2010/05/14/default-skin-for-custom-flashbuilder-componen ts/
http://flexdevtips.blogspot.com/2009/06/default-stylesheet-in-swc-flex-library.html
Following the first article guidelines has been successful for me but I'm not marking this topic as Resolved because I'd like some answers about this whole thing...

[svn:fx-trunk] 9328: Fixing SDK-22462: Event dispatched is not as expected in Tree

Revision: 9328
Author:   [email protected]
Date:     2009-08-14 17:02:35 -0700 (Fri, 14 Aug 2009)
Log Message:
Fixing SDK-22462: Event dispatched is not as expected in Tree
For this, the issue is really that TreeItemRenderers assume that no click event can occur on the disclosureIcon. This is because the discolsureIcon is added and removed each time it goes through invalidation in commitProperties(), so a new discolsureIcon gets created and replaces the old one after they mouseDown (meaning no click event actually occurs). Automation replays some mouse events on one disclosureIcon only (which is an automation bug because that?\226?\128?\153s not how it actually works in the real world) and when a ?\226?\128?\156click?\226?\128?\157 occurs, that causes an itemClick on the Tree, when it shouldn?\226?\128?\153t. For Flex 3, this wasn?\226?\128?\153t a problem because the IR was getting invalidated through a different codepath because openDuration did not default to 0. If you set it to 0, you?\226?\128?\153d see the same problem in Flex 3. Anyways, the fix is just to block all click events that occur on the disclosureIcon.
QE notes: -
Doc notes: -
Bugs: SDK-22462
Reviewer: Alex
Tests run: checkintests, mustella Tree
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-22462
    http://bugs.adobe.com/jira/browse/SDK-22462
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/treeClasses/TreeItemRenderer .as

error dateField not selecion date 27/11/2002 ?
This is bug flex 3 ?
thanks

[svn:fx-trunk] 9329: Fixing openDuration on Tree.

Revision: 9329
Author:   [email protected]
Date:     2009-08-14 17:07:31 -0700 (Fri, 14 Aug 2009)
Log Message:
Fixing openDuration on Tree. The issue was that a call to UIComponent.suspendBackgroundProcessing() wasn?\226?\128?\153t being respected by LayoutManager, now that it doesn?\226?\128?\153t use UIComponent.callLater(). The fix was for LayoutManager to look at UIComponentGlobals.callLaterSuspsendCount. There are probably other ways to fix this bug because all the tweening in Tree seems very hokey, but given that UIC.suspendBackgroundProcessing() should be respected by LayoutManager, this seemed like the right fix.
QE notes: We should add tests for openDuration
Doc notes: -
Bugs: SDK-21752
Reviewer: Alex
Tests run: checkintests, mustella Tree
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21752
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/LayoutManager.as

ould wrote:
I have done the hard work for you. My HTPC is pretty barebones so it was relatively easy to roll back all the packages that depend on libjpeg>7 with older versions. I then compiled the xbmc-svn package using that system. Slow downs are gone and I have uploaded the package to hotfile here:
http://hotfile.com/dl/13546051/021f9c9/ … ar.gz.html
This is for 32-bit. You will need the libjpeg6 package from AUR installed. I have tested it on two systems, my main system which has both libjpeg7 and the AUR libjpeg6 installed and on my htpc which has only the libjpeg6 along with the rolled back dependancies. Works good on both systems.
Hope that helps!
Kevin
Thanks ould!! You got it working with libjpeg6 again!
I had to upgrade libcdio again so now I lost dvd support. It's not easy to use the svn version.
If you could compile the build against libcdio 0.80 I'd be forever grateful... If you've got the time.
Last edited by Perre (2009-09-26 17:09:04)

[svn:fx-trunk] 10339: Fix BrowserManager for IE8.

Revision: 10339
Author:   [email protected]
Date:     2009-09-16 22:08:06 -0700 (Wed, 16 Sep 2009)
Log Message:
Fix BrowserManager for IE8. Also upgrade SWFObject with some changes from their code base
QE Notes: Last BrowserManagerTest test case fails in IE8. Updated version sent to Joann.
Doc Notes: None
Bugs: SDK-22941
Reviewer: Corey
API Change: No
Is noteworthy for integration: No
tests: checkintests mustella/browser/DeepLinking
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-22941
Modified Paths:
    flex/sdk/trunk/templates/swfobject/history/history.js
    flex/sdk/trunk/templates/swfobject/swfobject.js

[svn:fx-trunk] 10817: Fix a deeplinking problem in IE7

Similar Messages

Maybe you are looking for