[svn:fx-trunk] 8265: fix the textlLayout swf to contain the version number as well as the build number

Revision: 8265
Author:   [email protected]
Date:     2009-06-25 15:30:56 -0700 (Thu, 25 Jun 2009)
Log Message:
fix the textlLayout swf to contain the version number as well as the build number
Modified Paths:
    flex/sdk/trunk/build.xml

Thats good news.

Similar Messages

[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] 7868: Fixed bug in flex4test testWheel app; it needed to be updated to the latest effects API after motionPaths changed from an Array to a Vector . MotionPath

Revision: 7868
Author:   [email protected]
Date:     2009-06-15 16:37:33 -0700 (Mon, 15 Jun 2009)
Log Message:
Fixed bug in flex4test testWheel app; it needed to be updated to the latest effects API after motionPaths changed from an Array to a Vector.
Modified Paths:
    flex/sdk/trunk/development/eclipse/flex/flex4test/src/testWheel.mxml

Walter Laan wrote:
almightywiz wrote:
Walter Laan wrote:
The security popup really messes with the focus in Firefox (3.6.16) though.Not saying you're wrong, but I'm using FireFox 3.6.16, as well, and I have none of the focus troubles you've described.Cannot reproduce it now either. Weird.I got the impression you were referring to keyboard focus, so I did some further tests on focus behavior. The test results are listed in the Accumulated Results table on the 1st post.
The only browser so far that works as I'd expect, or at least as I'd like, is IE.
Applets and keyboard navigation have always been a PITA. Some time ago I vaguely recall seeing an update involving a new parameter to regulate initial focus (applet or page, ..or another applet), but for the life of me I cannot locate it now. Given that it was a parameter for initial focus, I doubt it would help in this case.
Edited by: Andrew Thompson on Mar 26, 2011 6:18 PM
Removed table which has now been expanded & added to 1st post.

[svn] 4669: Fix for - compiled SWF varies depending on version of java pointed

Revision: 4669
Author: [email protected]
Date: 2009-01-26 11:00:48 -0800 (Mon, 26 Jan 2009)
Log Message:
Fix for - compiled SWF varies depending on version of java pointed
QE Notes: Some mustella tests may need to be updated, as includes will be processed as per the order specified during compilation.
Doc Notes: None
Bugs: SDK-18168
Reviewed By: Paul
tests: checkintests, mxmlcunit
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18168
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerAPI.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerSwcContext.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/common/Configuration.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/swc/SwcMovie.java
flex/sdk/trunk/modules/compiler/src/java/flex2/linker/FlexMovie.java

Revision: 4669
Author: [email protected]
Date: 2009-01-26 11:00:48 -0800 (Mon, 26 Jan 2009)
Log Message:
Fix for - compiled SWF varies depending on version of java pointed
QE Notes: Some mustella tests may need to be updated, as includes will be processed as per the order specified during compilation.
Doc Notes: None
Bugs: SDK-18168
Reviewed By: Paul
tests: checkintests, mxmlcunit
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18168
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerAPI.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerSwcContext.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/common/Configuration.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/swc/SwcMovie.java
flex/sdk/trunk/modules/compiler/src/java/flex2/linker/FlexMovie.java

Initially I had downloaded Document 2 (Free) application to view my doc, ppt and xls files. I was not able to edit the files so there was an option for upgrade the Document-2 free to paid version. I have upgraded the Document 2 application.

Initially I had downloaded Document 2 (Free) application to view my doc, ppt and xls files. I was not able to edit the files so there was an option for upgrade the Document-2 free to paid version. I have upgraded the Document 2 application. But on my iPad now there are to application present Docemnt-2 (Free) and Document-2. I am not able to open any existing document using the upgraded version of application. How do I connect all the existing txt,PPT,XLS doccument to the new upgraded Document-2 application and then to edit it on my iPad.

As suggested I had deleted the free application and did a hard restart the iPad. I have again copied the document using iTunes. But I am not able to edit any document using this app. Document 2 (paid version) supports editing features of the txt/ xls /ppt files. Is there any problem while loading the Document 2 app. If I reload then do I need to purchase again?

Im having trouble activating my CS2 with my original serial number as well as the new serial number privided by Adobe

im having trouble activating my CS2 with my original serial number as well as the new serial number privided by Adobe

You must download and install the CS2 version provided by Adobe and you must use the new serial number provided by Adobe.
https://www.adobe.com/cfusion/entitlement/index.cfm?e=cs2_downloads

I am a very brand new Mac user. So anyway, when I point to the apple and click on "About This Mac", it says the operating system is, "OS X Version 10.8.2. The question, is this "Mountain Lion", or is that additional software I need to download?

I am a very brand new Mac user. So anyway, when I point to the apple and click on "About This Mac", it says the operating system is, "OS X Version 10.8.2. The question, is this "Mountain Lion", or is that additional software I need to download?

Jon Kevin wrote:
I am a very brand new Mac user. So anyway, when I point to the apple and click on "About This Mac", it says the operating system is, "OS X Version 10.8.2. The question, is this "Mountain Lion", or is that additional software I need to download?
Yes 10.8.2 is the latest version of Mountain Lion. 10.7 was Lion and 10.6 was Snow Leopard.
Cheers
Pete

[svn:fx-trunk] 11211: Fixing a fall-out from the DefaultItemRenderer change .

Revision: 11211
Author:   [email protected]
Date:     2009-10-27 17:07:30 -0700 (Tue, 27 Oct 2009)
Log Message:
Fixing a fall-out from the DefaultItemRenderer change. When labelDisplay comes on-board, we should check to see if the label property has been set, and push it down in there if it has. We need this because the labelDisplay isn't created until createChildren() time, which happens when the component is first validated, but for some scenarios, the component may not be on-screen at the time we set the label property. Also, itemIndex needs to be "cloned" in the drag'n drop scenario.
QE notes: -
Doc notes: -
Bugs: SDK-23867
Reviewer: Evtim
Tests run: checkintests, mustella List, DataGroup, DropDownList, ListDragDrop
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23867
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/DataGroup.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/ListItemDrag Proxy.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/DefaultItemRenderer.as

[svn:fx-trunk] 11541: Fix the textLayout build number that is set in the main build. xml to match what will be set when the build machine does NOT do the build

Revision: 11541
Author:   [email protected]
Date:     2009-11-06 14:29:41 -0800 (Fri, 06 Nov 2009)
Log Message:
Fix the textLayout build number that is set in the main build.xml to match what will be set when the build machine does NOT do the build
QE notes: no
Doc notes: no
Bugs: no
Reviewer:
Tests run: checkintests
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/trunk/frameworks/air-config.xml
    flex/sdk/trunk/frameworks/flex-config.xml

Thats good news.

[svn:bz-trunk] 5137: Fix failing security tests on BlazeDS/ trunk by using a remote object to invalidate the FlexSession at the end of each test method which should cause each test method to run with a new /clean session.

Revision: 5137
Author: [email protected]
Date: 2009-03-02 10:28:59 -0800 (Mon, 02 Mar 2009)
Log Message:
Fix failing security tests on BlazeDS/trunk by using a remote object to invalidate the FlexSession at the end of each test method which should cause each test method to run with a new/clean session. It looks like some test methods were leaving some things in a bad state which was causing the next test that ran to fail. These may be legitimate bugs/issues so we should investigate further to see what sequence of events gets things into a bad state but for these tests we want all of the test methods to run in isolation.
Modified Paths:
blazeds/trunk/qa/apps/qa-manual/WEB-INF/flex/services-config.mods.xml
blazeds/trunk/qa/apps/qa-regress/WEB-INF/flex/remoting-config.mods.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/security/stream ing-amf/JMSAuthSendSubscribeConstraintTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/security/stream ing-amf/MessagingAuthProSendTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/security/stream ing-http/JMSAuthSendSubscribeConstraintTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/security/stream ing-http/MessagingAuthProSendTest.mxml
Added Paths:
blazeds/trunk/qa/apps/qa-regress/WEB-INF/src/qa/messaging/SessionManager.java

In general theory, one now has the Edit button for their posts, until someone/anyone Replies to it. I've had Edit available for weeks, as opposed to the old forum's ~ 30 mins.
That, however, is in theory. I've posted, and immediately seen something that needed editing, only to find NO Replies, yet the Edit button is no longer available, only seconds later. Still, in that same thread, I'd have the Edit button from older posts, to which there had also been no Replies even after several days/weeks. Found one that had to be over a month old, and Edit was still there.
Do not know the why/how of this behavior. At first, I thought that maybe there WAS a Reply, that "ate" my Edit button, but had not Refreshed on my screen. Refresh still showed no Replies, just no Edit either. In those cases, I just Reply and mention the [Edit].
Also, it seems that the buttons get very scrambled at times, and Refresh does not always clear that up. I end up clicking where I "think" the right button should be and hope for the best. Seems that when the buttons do bunch up they can appear at random around the page, often three atop one another, and maybe one way the heck out in left-field.
While I'm on a role, it would be nice to be able to switch between Flattened and Threaded Views on the fly. Each has a use, and having to go to Options and then come back down to the thread is a very slow process. Jive is probably incapable of this, but I can dream.
Hunt

[svn:bz-trunk] 14778: fix the tests by checking all possible return text.

Revision: 14778
Revision: 14778
Author:   [email protected]
Date:     2010-03-16 09:14:53 -0700 (Tue, 16 Mar 2010)
Log Message:
fix the tests by checking all possible return text.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/proxyService/httpservice/amfchan nel/hs_resultformat.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/proxyService/httpservice/httpcha nnel/hs_resultformat.mxml

I believe that plugins rely on the libraries being located in a specific location. The installer can place these libraries in the specific location or some other installer can do that. You can create code that scans the library directly to "learn" what packages/libraries are available. Then you would build the path to that VI and open the reference to it.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

[svn:bz-trunk] 8964: Fix LCDS-953 - Add a last ditch catch block to the service() function to avoid any possibility or leaking exception info.

Revision: 8964
Author:   [email protected]
Date:     2009-07-31 12:07:09 -0700 (Fri, 31 Jul 2009)
Log Message:
Fix LCDS-953 - Add a last ditch catch block to the service() function to avoid any possibility or leaking exception info.
Ticket Links:
    http://bugs.adobe.com/jira/browse/LCDS-953
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/MessageBrokerServlet.java

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: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] 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] 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] 8265: fix the textlLayout swf to contain the version number as well as the build number

Similar Messages

Maybe you are looking for