[svn:fx-trunk] 11329: Fix a rather bad typo in AsyncListView/itemUpdated().

Revision: 11329
Author:   [email protected]
Date:     2009-10-30 14:23:59 -0700 (Fri, 30 Oct 2009)
Log Message:
Fix a rather bad typo in AsyncListView/itemUpdated().
QE notes: none
Doc notes: none
Bugs: sdk-23909
Reviewer: Alex
Tests run:
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-23909
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/collections/AsyncListView.as

Similar Messages

[svn:fx-trunk] 11250: Fixing proxy pattern bug in VideoPlayer.

Revision: 11250
Author:   [email protected]
Date:     2009-10-28 17:07:19 -0700 (Wed, 28 Oct 2009)
Log Message:
Fixing proxy pattern bug in VideoPlayer. I tried to save a few extra bytes by not keeping around an extra object, but I made a mistake with this code. It seems better just to follow the typical pattern and not worry about this extra savings, which probably cost more in code-size anyways.
Also changing VideoPlayer.thumbnailSource to mx_internal, rather than public. In VideoElement it's mx_internal, and that's what it should be here too.
QE notes: -
Doc notes: -
Bugs: SDK-23665
Reviewer: Deepa
Tests run: checkintests, mustella VideoPlayer
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23665
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/VideoPlayer.as

[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] 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] 5351: Fix for @ copy tag causing first method arg to appear as the last arg in the destination method

Revision: 5351
Author: [email protected]
Date: 2009-03-17 12:51:44 -0700 (Tue, 17 Mar 2009)
Log Message:
Fix for @copy tag causing first method arg to appear as the last arg in the destination method
QE Notes: Some baseline will require updates.
Doc Notes: None.
Bugs: SDK-19974
tests: checkintests, asdoc
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-19974
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/AsDocUtil.java

Well, putting all that Java code into a JSP was a bad idea in the first place, just on general design principles. But you've done it in such a way that the result of compiling the JSP is malformed Java code. Frankly I would just throw it away and put the Java code into a servlet or some other Java class, where it belongs.
But if you're really working in a place where nobody has learned anything since 2003, and you're forced to support that old junk, then I would point out that the error occurs before the place which generates this line:
import java.util.*;You only need to look at two of the thousand lines of code you posted.

[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: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: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] 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] 10635: * Fixed FB issue with FXG in library projects.

Revision: 10635
Author:   [email protected]
Date:     2009-09-28 06:49:45 -0700 (Mon, 28 Sep 2009)
Log Message:
Fixed FB issue with FXG in library projects.
QE notes:
Doc notes:
Bugs: FB-22197
Reviewer: pfarland
Cycloner: gcomnino
Tests run: checkintests
Is noteworthy for integration: Yes, fixes FB issue
Code-level description of changes:
Modified getSourceListMimeTypes() to include FXG mime type.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FB-22197
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/tools/WebTierAPI.java

[svn:fx-trunk] 11999: Fixed: ASC-3889 - Using setting in a for loop causes Verify error

Revision: 11999
Revision: 11999
Author:   [email protected]
Date:     2009-11-19 11:37:09 -0800 (Thu, 19 Nov 2009)
Log Message:
Fixed: ASC-3889 - Using setting in a for loop causes Verify error
Notes: emit pop after callstatic to a void function to balance the stack.
Reviewer: jodyer+
Testing: asc,tamarin,flex checkin tests
Ticket Links:
    http://bugs.adobe.com/jira/browse/ASC-3889
Modified Paths:
    flex/sdk/trunk/modules/asc/src/java/macromedia/asc/semantics/CodeGenerator.java

Blacklisting the ahci module does indeed get rid of the error. Would be nice to figure out why it was conflicting with the ahci module though.
I have not yet tried the 173xx drivers, but the latest drivers for the Quadro FX 580 are the 256.53 drivers according to nvidia.
Posted at the nV forums (http://www.nvnews.net/vbulletin/showthread.php?t=155282), so we'll see what they suggest.

[svn:fx-trunk] 11530: Fix ASC-3790 ( conditional expression in for loop causes verifier error) r=jodyer

Revision: 11530
Author:   [email protected]
Date:     2009-11-06 13:23:05 -0800 (Fri, 06 Nov 2009)
Log Message:
Fix ASC-3790 (conditional expression in for loop causes verifier error) r=jodyer
Ticket Links:
    http://bugs.adobe.com/jira/browse/ASC-3790
Modified Paths:
    flex/sdk/trunk/modules/asc/src/java/macromedia/asc/parser/ConditionalExpressionNode.java

[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] 11329: Fix a rather bad typo in AsyncListView/itemUpdated().

Similar Messages

Maybe you are looking for