[svn] 4950: * Fixed some junit test failures caused by revision 4939.

Revision: 4950
Author: [email protected]
Date: 2009-02-13 08:31:33 -0800 (Fri, 13 Feb 2009)
Log Message:
* Fixed some junit test failures caused by revision 4939.
tests Passed: checkintests
Needs QA: YES
Needs DOC: NO
Bug fixes: SDK-19299
API Change: NO
Reviewer: Darrell
Code-level description of changes:
Modified compile() by moving check for no inputs above the call to
recompile().
Modified link() to only call FileUtil.getCanonicalPath() if the
output is not null.
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-19299
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/tools/oem/Library.java

Similar Messages

[svn] 2263: Fixed WiseUI performance app and some mustella test failures.

Revision: 2263
Author: [email protected]
Date: 2008-06-26 13:19:12 -0700 (Thu, 26 Jun 2008)
Log Message:
Fixed WiseUI performance app and some mustella test failures.
tests Passed: checkintests
Needs QA: YES
Needs DOC: NO
Bug fixes:
API Change: NO
Reviewer: pfarland
Code-level description of changes:
OffsetInputBuffer.java
Added getLineText() override to take the offset into
consideration.
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/OffsetInputBuffer.java

[svn:osmf:] 15899: Attempted fix for unit tests failure.

Revision: 15899
Revision: 15899
Author:   [email protected]
Date:     2010-05-04 17:21:06 -0700 (Tue, 04 May 2010)
Log Message:
Attempted fix for unit tests failure.
Modified Paths:
    osmf/trunk/framework/OSMFTest/org/osmf/OSMFTests.as

[svn] 1378: Fixed some recently introduced mxunit databinding failures when

Revision: 1378
Author: [email protected]
Date: 2008-04-24 07:15:10 -0700 (Thu, 24 Apr 2008)
Log Message:
Fixed some recently introduced mxunit databinding failures when
-generate-abstract-syntax-tree is turned on.
checkintests Passed: YES
Needs QA: No
Needs DOC: NO
API Change: NO
Code-level description of changes:
AbstractSyntaxTreeUtil.java
Added some asserts to parse() to help catch ASC changes early.
binding/DataBindingExtension.java
Modified both generateAccessorFunction()'s to no longer skip the
first two nodes as AbstractSyntaxTreeUtil.parse() handles this.
Modified generateInitFunctionCommon() to set the
FunctionSignatureNode's void_anno to true.
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/AbstractSyntaxTreeUtil.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/DataBindingExtension. java

[svn] 4203: * Fixed some failing invalidation tests.

Revision: 4203
Author: [email protected]
Date: 2008-12-01 10:25:12 -0800 (Mon, 01 Dec 2008)
Log Message:
* Fixed some failing invalidation tests.
tests Passed: checkintests
Needs QA: YES
Needs DOC: NO
Bug fixes: SDK-18180
API Change: NO
Reviewer: Pete F.
Code-level description of changes:
Modified validateCompilationUnits() to restrict
DependencyNeedsRecompilation to dependents not in
updatedWithStableSignature and to restrict DependencyNotCached to
compilation units with type information.
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18180
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerAPI.java

[svn] 4068: fix some negative config tests - updates to the error message text

Revision: 4068
Author: [email protected]
Date: 2008-11-11 08:37:37 -0800 (Tue, 11 Nov 2008)
Log Message:
fix some negative config tests - updates to the error message text
additional negative test to validate we throw when advanced messaging property access is attempted
Modified Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/InvalidBufferPolicyTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/InvalidConflatePolicyTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/frequencies/McfGreaterthanMfTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leOutbound/InvalidBufferPolicyTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leOutbound/InvalidConflatePolicyTest/error.txt
Added Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/AdaptiveFrequencyTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/AdaptiveFrequencyTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/AdaptiveFrequencyTest/messaging-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/AdaptiveFrequencyTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/FrequencyStepSizeTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/FrequencyStepSizeTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/FrequencyStepSizeTest/messaging-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/FrequencyStepSizeTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/MaxQueueSizeTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/MaxQueueSizeTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/MaxQueueSizeTest/messaging-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/MaxQueueSizeTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/readme.txt

Revision: 4068
Author: [email protected]
Date: 2008-11-11 08:37:37 -0800 (Tue, 11 Nov 2008)
Log Message:
fix some negative config tests - updates to the error message text
additional negative test to validate we throw when advanced messaging property access is attempted
Modified Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/InvalidBufferPolicyTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/InvalidConflatePolicyTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/frequencies/McfGreaterthanMfTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leOutbound/InvalidBufferPolicyTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leOutbound/InvalidConflatePolicyTest/error.txt
Added Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/AdaptiveFrequencyTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/AdaptiveFrequencyTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/AdaptiveFrequencyTest/messaging-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/AdaptiveFrequencyTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/FrequencyStepSizeTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/FrequencyStepSizeTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/FrequencyStepSizeTest/messaging-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/FrequencyStepSizeTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/MaxQueueSizeTest/
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/MaxQueueSizeTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/MaxQueueSizeTest/messaging-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/MaxQueueSizeTest/services-config.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/readme.txt

[svn] 4598: Fixed some approval FlexUnit tests.

Revision: 4598
Author: [email protected]
Date: 2009-01-20 10:45:04 -0800 (Tue, 20 Jan 2009)
Log Message:
Fixed some approval FlexUnit tests.
tests Passed: checkintests
Needs QA: YES
Needs DOC: NO
API Change: NO
Reviewer: Carol
Code-level description of changes:
Modified watchXML() and unwatchXML() to work with XMLList's of
length greater than 1.
Modified Paths:
flex/sdk/trunk/frameworks/projects/framework/src/mx/utils/XMLNotifier.as

JUNIT test failure-Configuration file bc4j.xcfg not found in the classpath

Hi All,
As part of an ESS project,Im having a model project containing a VO(parameters VO).This VO is configured to have Read-only access through SQL query and have only one transient attribute each.For the model projects containing the VO for pre merge checker compliance I had to create JUNIT Test projects containing new AMs for testing the parametersVO. While running the JUNIT tests I got an exception like
“oracle.jbo.JboException: JBO-29000: Unexpected exception caught: oracle.jbo.ConfigException, msg=JBO-33001: Configuration file /oracle/apps/hcm/goals/core/dataMigration/publicEssModel/test/applicationModule/common/bc4j.xcfg is not found in the classpath.”.—even though this file is contained in both the src/classes folder of the project.
When i try to run the TestAM I'm getting an exception like 'configuration tester.xcfg not found in the calsspath.
While debugging this error, we found that we are able to successfully run the JUNIT tests if we make some changes in the adf-config.xml file of the Application. The change required is to comment out the mdsC:adf-mds-config tag in the xml file.
After doing this change Im also able to run my AM without any exception.
Is this a known issue?.
Since modifying the adf-config.xml is not a recommended practice is there any workaround that we can get rid of this exception.
Regards,
Ajin.

Just checked but could only find this thread Unable to run ADFBC JUNIT Test Classes with JDEV11G 11.1.1.6
As it's also dealing with junit and 11.1.1.6.0 you might want to read it.
Timo

[svn] 3687: Add some messaging tests for scenarios that involve subscribing to a destination , disconnecting from the channel currently being used and resubscribing to the destination .

Revision: 3687
Author: [email protected]
Date: 2008-10-16 11:23:39 -0700 (Thu, 16 Oct 2008)
Log Message:
Add some messaging tests for scenarios that involve subscribing to a destination, disconnecting from the channel currently being used and resubscribing to the destination. There is an issue that is causing the streaming/multipleDisconnectsResubscribesTest.mxml test to fail that I will log a bug for.
Added Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/disconnectResubscribeJMSTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/disconnectResubscribeTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/multipleDisconnectsResubscribesTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/disconnectResubscribeJMSTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/disconnectResubscribeTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/multipleDisconnectsResubscribesTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/disconnectResubscribeJMSTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/disconnectResubscribeTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/multipleDisconnectsResubscribesTest.mxml

Revision: 3687
Author: [email protected]
Date: 2008-10-16 11:23:39 -0700 (Thu, 16 Oct 2008)
Log Message:
Add some messaging tests for scenarios that involve subscribing to a destination, disconnecting from the channel currently being used and resubscribing to the destination. There is an issue that is causing the streaming/multipleDisconnectsResubscribesTest.mxml test to fail that I will log a bug for.
Added Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/disconnectResubscribeJMSTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/disconnectResubscribeTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/multipleDisconnectsResubscribesTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/disconnectResubscribeJMSTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/disconnectResubscribeTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/multipleDisconnectsResubscribesTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/disconnectResubscribeJMSTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/disconnectResubscribeTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/multipleDisconnectsResubscribesTest.mxml

[svn] 2788: fix asc commandline tests, use wildcards for build number is usage baselines

Revision: 2788
Author: [email protected]
Date: 2008-08-08 10:47:32 -0700 (Fri, 08 Aug 2008)
Log Message:
fix asc commandline tests, use wildcards for build number is usage baselines
Modified Paths:
flex/sdk/trunk/modules/asc/test/compiler/cmdline/avmtarget.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/avmtargetn.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/config.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/help1.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/help2.err

[mi] EQ overflowing. The server is probably stuck in an infinite loop.
Seems a little suspicious, though its kind of a generic error message. Lots and lots of google hits on that one.
Are you sure none of the libs or executables for xorg-* got damaged before the system called for an fsck? The power went out on me once and my hard drive "forgot" about 75% of my kernel modules, although it was a conventional hard drive and not an SSD.
try re-installing some packages:
pacman -S xorg xf86-video-ati ati-dri libgl
(any more anyone can think of?)
[edit]
Is your copy of that bootchart that blurry or is flicker messing with it? It looks like its been resized even at largest setting. I can hardly read it.
Last edited by wriggary (2010-01-29 04:43:02)

[svn] 834: Fix failing MBean tests.

Revision: 834
Author: [email protected]
Date: 2008-03-17 10:15:31 -0700 (Mon, 17 Mar 2008)
Log Message:
Fix failing MBean tests. The name of the qa-regress webapp changed in web.xml so the MBean name used in the tests needed to get updated.
Modified Paths:
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/MBeanS erver/StreamingAMFEndpointMBean.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/MBeanS erver/StreamingHTTPEndpointMBean.mxml

[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] 7728: Reverting change 7716 after it caused a bunch of test failures.

Revision: 7728
Author:   [email protected]
Date:     2009-06-10 14:58:37 -0700 (Wed, 10 Jun 2009)
Log Message:
Reverting change 7716 after it caused a bunch of test failures.
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/common/MxmlConfiguration.java

Did I understand you right that you said that even using a PCI NIC in those systems gave the same errors? That would likely mean that any corruption is in the hardware... the nForce4 chipset or Hypertransport or maybe even mbrd traces? I think there are enough systems out there running satisfactorily that that is not a viable explanation: Hypertransport errors would cause all kinds of hard disk problems as well as with other I/O devices. Are you sure that nothing is (unintentionally) overclocked and have you checked the memory with Orthos http://sp2004.fre3.com/beta/beta2.htm?
There are a couple of things about the nForce NI though: most important is that the TCP offloading is broken and I've had to disable Checksum Offloading and Segmentation Offloading in the Advanced Properties of the nForce Network Controller in Device Manager. This also means that the Active Armor is broken and consequently the nVidia Firewall and NAM (Network Access Manager) are useless. IOW if NAM is installed get rid of it - I've no idea what it might do with other NIs installed in the system... hopefully nothing but then.......
A couple of points to clear up: 1) are you only getting the errors on an internet connection and LAN connections work OK? 2) What are those nForce systems connected to... a hub or switch and through to a router? 3) I'm not sure what "outbound packet errors" means - is it due to the OS seeing that the packets are malformed before they go to the NI, or is it due to the NI getting error responses from the device on the other end of the "wire"?

[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-4.x] 14337: Revert this file from mirroring PARB change 14431 until I can figure out why it is causing a graphic test failure .

Revision: 14337
Revision: 14337
Author:   [email protected]
Date:     2010-02-22 12:31:24 -0800 (Mon, 22 Feb 2010)
Log Message:
Revert this file from mirroring PARB change 14431 until I can figure out why it is causing a graphic test failure.
QE notes:
Doc notes: None
Bugs:
Reviewed By:
Tests run: checkintests
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/branches/4.x/frameworks/projects/spark/src/spark/primitives/supportClasses/Graph icElement.as

Revision: 14337
Revision: 14337
Author:   [email protected]
Date:     2010-02-22 12:31:24 -0800 (Mon, 22 Feb 2010)
Log Message:
Revert this file from mirroring PARB change 14431 until I can figure out why it is causing a graphic test failure.
QE notes:
Doc notes: None
Bugs:
Reviewed By:
Tests run: checkintests
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/branches/4.x/frameworks/projects/spark/src/spark/primitives/supportClasses/Graph icElement.as

[svn] 4950: * Fixed some junit test failures caused by revision 4939.

Similar Messages

Maybe you are looking for