[svn:bz-trunk] 14636: Fix misspelling of occurred.
Revision: 14636
Revision: 14636
Author: [email protected]
Date: 2010-03-09 06:16:33 -0800 (Tue, 09 Mar 2010)
Log Message:
Fix misspelling of occurred. No functional change.
Modified Paths:
blazeds/trunk/modules/core/src/flex/messaging/MessageBrokerServlet.java
Similar Messages
-
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. asI 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: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.mxmlonearm 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] 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 .aserror 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.asould 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) -
Revision: 9287
Author: [email protected]
Date: 2009-08-13 15:53:43 -0700 (Thu, 13 Aug 2009)
Log Message:
Fixes bug with shader-transition effects (AnimateTransitionShader, Wipe, and CrossFade) when acting on targets that either have filters or are inside a hierarchy with filters. Fix was to capture the bitmap snapshot of the target without any of its own filters applied and to then use the ShaderFilter in conjunction with the target's filters during the animation.
QE notes: Probably need more tests in this area, now that we handle it
Doc notes: none
Bugs: sdk-20250
Reviewer: Jason
Tests run: Checkintests, Mustella (spark/effects/[AnimateTransitionShader|Wipe|CrossFade])
Is noteworthy for integration: No
Ticket Links:
http://bugs.adobe.com/jira/browse/sdk-20250
Modified Paths:
flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/AnimateTransitionShader.as
flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/AnimateTransiti onShaderInstance.asLots to be excited about. BUT...Just updated to 8.1 on one of my computers to test it out...
Sadly, the following issue is NOT fixed for me. Is it with new projects only? I haven't started a new project on 8.1 I've only opened an old project but the issue that I'm referring to which involves also a delay/freeze of anywhere from a few seconds to a MINUTE while the render bar goes from yellow to red and then back to yellow is still there. Boo.
On the list above...
Switching between sequences can turn the render bar red.
This issue is incredibly easy to replicate. I really do hope it gets fixed. Here are the steps:
1) Create two sequences with multiple short clips (the more clips the better)
2) Make sure GPU acceleration is enabled.
3) Add warp stabilizer to the clips in both sequences. Again, the more clips the longer the delay/freeze will be as the render bar goes from YELLOW to RED and then eventually back to YELLOW again.
4) Hit SAVE.
5) Now, toggle between sequences. You'll hit a short delay with a few clips stabilized and a LONG delay with lots stabilized. In my case this delay is around a full minute. The render bar will go from YELLOW to RED and then back to yellow...eventually.
6) Toggle back to the original sequence and the delay occurs again.
7) Once you've toggled between sequences and have gone through this delay, that's it, there is no longer a delay...UNTIL...(and here's the big kicker)...until the project is SAVED again. After that the issue returns when you toggle between sequences. Both saving manually and AUTOSAVING cause this issue. No way around it except not editing with GPU acceleration.
Not sure what the issue is...caching issue when saving maybe? Either way, it stinks and it's still there in 8.1. Big bummer.
Again, lots to be excited about with this release but I really was hopefully this specific issue was resolved.
Sigh. -
[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 vaaplay -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. -
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.javaWell, 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] 12978: Fix for possible null deref in Effect. captureMoreStartValues().
Revision: 12978
Revision: 12978
Author: [email protected]
Date: 2009-12-15 17:12:29 -0800 (Tue, 15 Dec 2009)
Log Message:
Fix for possible null deref in Effect.captureMoreStartValues(). Seems unlikely to ever occur since the function is not really there for random calling outside of data effects, but the fix was simple.
QE notes: none
Doc notes: none
Bugs: sdk-16451
Reviewer: Jason
Tests run: checkintests, Mustella mx/effects, mx/ListDataEffects
Is noteworthy for integration: no
Ticket Links:
http://bugs.adobe.com/jira/browse/sdk-16451
Modified Paths:
flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Effect.as -
Revision: 7891
Author: [email protected]
Date: 2009-06-16 13:38:37 -0700 (Tue, 16 Jun 2009)
Log Message:
Fixed bug in effects that was fallout from renaming offsets property to postLayoutTransformOffsets.
QE Notes: none
Doc Notes: None
Bugs: SDK-21839
Reviewer: Evtim
Tests: checkintests
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-21839
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/AnimateTransfor mInstance.asLots to be excited about. BUT...Just updated to 8.1 on one of my computers to test it out...
Sadly, the following issue is NOT fixed for me. Is it with new projects only? I haven't started a new project on 8.1 I've only opened an old project but the issue that I'm referring to which involves also a delay/freeze of anywhere from a few seconds to a MINUTE while the render bar goes from yellow to red and then back to yellow is still there. Boo.
On the list above...
Switching between sequences can turn the render bar red.
This issue is incredibly easy to replicate. I really do hope it gets fixed. Here are the steps:
1) Create two sequences with multiple short clips (the more clips the better)
2) Make sure GPU acceleration is enabled.
3) Add warp stabilizer to the clips in both sequences. Again, the more clips the longer the delay/freeze will be as the render bar goes from YELLOW to RED and then eventually back to YELLOW again.
4) Hit SAVE.
5) Now, toggle between sequences. You'll hit a short delay with a few clips stabilized and a LONG delay with lots stabilized. In my case this delay is around a full minute. The render bar will go from YELLOW to RED and then back to yellow...eventually.
6) Toggle back to the original sequence and the delay occurs again.
7) Once you've toggled between sequences and have gone through this delay, that's it, there is no longer a delay...UNTIL...(and here's the big kicker)...until the project is SAVED again. After that the issue returns when you toggle between sequences. Both saving manually and AUTOSAVING cause this issue. No way around it except not editing with GPU acceleration.
Not sure what the issue is...caching issue when saving maybe? Either way, it stinks and it's still there in 8.1. Big bummer.
Again, lots to be excited about with this release but I really was hopefully this specific issue was resolved.
Sigh. -
[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] 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.javaI 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:bz-trunk] 23085: Fix test to explicitly remove an event listener after the test is finished .
Revision: 23085
Revision: 23085
Author: [email protected]
Date: 2011-10-21 07:49:33 -0700 (Fri, 21 Oct 2011)
Log Message:
Fix test to explicitly remove an event listener after the test is finished. Not doing this was causing the test to throw an RTE.
Modified Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/security/stream ing-amf/MessagingAuthProSendTest.mxmlThanks for the ideas regarding beforeInvoke, Ben. I will try to check that out. In my situation, here's essentially how my script is working...
BeforeSave is invoked.
Script makes a change to the document, which should be captured in the saved file.
Document saves.
Document appears saved for a moment, and then appears unsaved (asterisk in the document title).
My biggest problem is that this behavior isn't consistent. I have dozens of users, all running the same script, and the problem only occurs with certain users and at random times. I can move a problematic document from a user's machine to a different machine, and the problem doesn't occur there. It's very difficult to troubleshoot because I can't reproduce it consistently. -
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
Maybe you are looking for
-
I just purchased the I5, and use the same itunes as my wife. All my wifes contacts showed up on my phone. Is there a way to avoid this?
-
A very good friend of mine dropped her iphone into water and now it is not working.Her husband recently passed away and text messages from him and from well wishers after his decease are feared lost. Is there any way to retrieve them? I suggested con
-
Photoshop CS5 won't work with the raw files from my new Canon D60 camera. Do I need CS6?
-
Hi SAP FI/CO GURUS ... please tell me what are the activities
Hai SAP FI/CO gurus Good day to you all. i know the activities of a fi/co consultant in implementation project. i would like to know the responsibilities or activities of a sap fi/co consultant in a development support project. As per my knowledge t
-
Deserialization error of exception information
Hello, In my client when an exception from the server is caught I get the following exception info: Runtime exception; nested exception is: deserialization error: unexpected XML reader state. expected: END but found: START: messageSearching for