[svn] 1941: Fix bug with writing out a MorphShape2 line style when it has a fill

Revision: 1941
Author: [email protected]
Date: 2008-06-04 12:13:17 -0700 (Wed, 04 Jun 2008)
Log Message:
Fix bug with writing out a MorphShape2 line style when it has a fill
connected to it. Had been calling encodeMorphFillstyles() directly
with an array of one element, but that adds a count byte (of value 1)
which should not be there. So I decomposed new method
encodeMorphFillstyle() out of encodeMorphFillstyles(). So not a big
change, but lots of indentation changes.
Other than that all changes were replacing the use of constant numbers
with static constants from FillStyle and also adding an equals()
implementation for FocalGradient.
reviewed by Pete Farland, passed flex checkin tests
Modified Paths:
flex/sdk/trunk/modules/swfutils/src/java/flash/swf/TagDecoder.java
flex/sdk/trunk/modules/swfutils/src/java/flash/swf/TagEncoder.java
flex/sdk/trunk/modules/swfutils/src/java/flash/swf/types/FocalGradient.java

Hello,
We also have this problem ...
We are concluded, (??) When there is a note on the first or second line that starts in the block, justification and rebuilt and the problem happens! even made to change color of text on the blank page occurs ... our solution to an extra line at the beginning of the block without note or make it past the note on the previous page ...
when in a true solution?
Translation from French
Bonjour,
Nous avons aussi ce problème …
Nous somme arrivé à la conclusion, (???) quand il y a une note sur la première ou la deuxième ligne qui commence dans le bloc, justification et refaite et le problème arrive !!! même le faite de changé de couleur sur du texte les page blanche survient … notre solution mettre une ligne supplémentaire en début du bloc sans note ou faire passé le note sur la page précédente …
à quand une vrai solution?
Philippe

Similar Messages

[svn:fx-trunk] 9287: 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 .

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.as

Lots 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] 12786: Fixed bug with state property value assignments.

Revision: 12786
Revision: 12786
Author:   [email protected]
Date:     2009-12-10 07:35:43 -0800 (Thu, 10 Dec 2009)
Log Message:
Fixed bug with state property value assignments. SetProperty pseudonym values (width/explicitWidth, height/explicitHeight) were not getting set correctly, causing values to be incorrectly assigned to 0 in some cases.
QE notes: -
Doc notes: -
Bugs: sdk-24446
Reviewer: Corey
Tests run: checkintests, Mustella tests/States, tests/mx/states
Is noteworthy for integration: Yes (fix requested by tools)
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-24446
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/states/SetProperty.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:osmf:] 15068: Fix bug FM-603: Need to signal complete event when live stream is unpublished.

Revision: 15068
Revision: 15068
Author:   [email protected]
Date:     2010-03-26 10:10:58 -0700 (Fri, 26 Mar 2010)
Log Message:
Fix bug FM-603: Need to signal complete event when live stream is unpublished.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FM-603
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/net/NetStreamCodes.as
    osmf/trunk/framework/OSMF/org/osmf/net/NetStreamTimeTrait.as

I have at least now managed to narrow down the problem.
I took a guess at the packages that were causing problems, and seems I guessed right.
By following this guide: http://wiki.archlinux.org/index.php/Downgrade_packages
I downgraded both libgl to version 7.7-1 and ati-dri to 7.7-1, and now I can X starts correctly.
I guess I'll need to figure out how to file a bug on those packages.

How can you get the schedule of a single reoccurring job with Restart ability in Redwood to pause when it has failed...?

We need the Request Restart ability when scheduling a single reoccurring job in Redwood. Most of our jobs are scheduled in CHAINs which offers the Final Status Handler on Step level, and the schedule is "paused" when a job in the CHAIN has failed ( the next instance does not populate until the OP MSG has been Replied to) , and once the OPERATOR message is replied to, the CHAIN can resume running again ( desired ) . But we need this same ability when scheduling a single job not in a CHAIN. In our testing, we set up a job with Request Restart chosen on the Error , Killed and Unknown selections on the Restart Behavior Tab. But we found when a job is scheduled say once a day at 8AM, and when it fails, an OPERATOR msg appears allowing a Restart choice ( desired), but the next day's schedule also populates ( undesired) and we do NOT want the schedule to continue on yet because we need a chance to fix the error before the next insance runs for business reasons. So how can you get the schedule of a single reoccurring job with Restart ability in Redwood to pause when it has failed...?

Hello Fran,
You can wrap the job chain in a master job chain in the first step and set the final status handler there.
You can also set the Restart Behavior to 'Stop Submit Frame', in that case you will have to resubmit the job once you are finished troubleshooting.
Regards Gerben

[svn] 4793: Fix bug SDK-17734 Path with width and height set different than path data has incorrect bounds

Revision: 4793
Author: [email protected]
Date: 2009-02-02 11:20:06 -0800 (Mon, 02 Feb 2009)
Log Message:
Fix bug SDK-17734 Path with width and height set different than path data has incorrect bounds
Fix: When calculating the bounds position we should take into account the implicit scaling factor actualSize/naturalSize. Also did some refactoring, getting rid of the protected method calculateTopLeft.
QE Notes: None
Doc Notes: None
Bugs: SDK-17734
Reviewer: Ryan
tests: mustella gumbo/layout/GraphicElement
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-17734
http://bugs.adobe.com/jira/browse/SDK-17734
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/Ellipse.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/Path.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/graphicsClasses/GraphicElement.a s

Thank you so much for replying.
Yes I have removed and reinstalled WMP.
I had good results with the PD6 application installed on the default path onto the C: drive with the one exception that if the application was launched by accident and the user data path was not available, the PD6 application would blow away my custom user path registry settings. Now that I know what they are I have made a .reg file to repair my registry to my desired user data paths.
Installing the application on the removable drive appeared to help prevent me from launching the application by accident and overwriting my registry with default user paths.
So which is the less of the two evils?
If the application directory is not available, windows media player still tries to launch the .msi for installing PD6.
If I install the application to the C: drive but the user data to the removable drive, launching the PD6 application without the user data drive will still corrupt my registry settings for a user data path.
Both these issues seem like a logical (if not easy) fix that should be done in the PD6 application and installation package. I mean really, cannot anyone tell me why windows media player is checking the PD6 application directory? Why in PD4 did we have an option control for setting the user data path from the PD4 application? Why is this option not in the PD6 application, just the installer?
I am given a choice during installation to move the user data to another non default location. Why else would this be provided if not to accommodate my kind of request to store the user data into an alternate location other than “My Document”. Certainly Palm is not trying to force the users on how to protect and store their personal data?
Post relates to: Centro (Verizon)

[svn] 4932: Fixed RTE with FxAnimate3DInstance, where a check in a superclass on whether the property was a style didn' t succeed because the effect was using properties that weren' t actually styles or properties on the object.

Revision: 4932
Author: [email protected]
Date: 2009-02-11 15:29:32 -0800 (Wed, 11 Feb 2009)
Log Message:
Fixed RTE with FxAnimate3DInstance, where a check in a superclass on whether the property was a style didn't succeed because the effect was using properties that weren't actually styles or properties on the object. Fine for the effect, but not for the superclass. Fix was to simply stub out the style check.
QE Notes:
Doc Notes: None
Bugs: SDK-19256
Reviewer: Ely
tests: checkintests, Mustella mx/effects/FxRotate3D
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-19256
Modified Paths:
flex/sdk/branches/i10/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimate3DI nstance.as

Revision: 4932
Author: [email protected]
Date: 2009-02-11 15:29:32 -0800 (Wed, 11 Feb 2009)
Log Message:
Fixed RTE with FxAnimate3DInstance, where a check in a superclass on whether the property was a style didn't succeed because the effect was using properties that weren't actually styles or properties on the object. Fine for the effect, but not for the superclass. Fix was to simply stub out the style check.
QE Notes:
Doc Notes: None
Bugs: SDK-19256
Reviewer: Ely
tests: checkintests, Mustella mx/effects/FxRotate3D
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-19256
Modified Paths:
flex/sdk/branches/i10/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimate3DI nstance.as

[svn] 3610: Fixing bug SDK-17173: Setting rotate to a large number doesn' t work anymore.

Revision: 3610
Author: [email protected]
Date: 2008-10-13 17:33:25 -0700 (Mon, 13 Oct 2008)
Log Message:
Fixing bug SDK-17173: Setting rotate to a large number doesn't work anymore.
The Flash Player clamps rotate between -180 and 180. We should do the same now that we're doing some of the calculations ourselves. This clamping logic was added to CompoundTransform.as. Also, clamping logic was added to UIComponent. This is because FP10 doesn't handle values greater than 2^15-1; FP 9 used to handle these values fine. I filed a FP bug for this (FP-749).
QE: Yes - Please look out for any rotation failures
Doc: No
Bugs: SDK-17173
Reviewer: Ely
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-17173
http://bugs.adobe.com/jira/browse/FP-749
http://bugs.adobe.com/jira/browse/SDK-17173
Modified Paths:
flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/geom/CompoundTransform.as

Can we now assume that the touch SDK has been abandonned by Adobe? It's now a year after "should be updated soon", and currently if you try to download the touch SDK from this page you get the Photoshop 3 SDK instead!!!
I ask as I'm about to remove Touch support from my app; the very few people that use touch are now having problems e.g., timeouts, with the latest version of Photoshop.
Sandy

[svn] 3493: Fix bug setting focus into an A. 2 application that is in a dialog.

Revision: 3493
Author: [email protected]
Date: 2008-10-06 13:40:22 -0700 (Mon, 06 Oct 2008)
Log Message:
Fix bug setting focus into an A.2 application that is in a dialog.
QE: YES
Doc:
Checkintests: Marshall Plan mustella tests
Reviewer: Carol
Bugs: SDK-17177
SystemManager.as
On mouse down, change the test from "the click was in a bridged application", to "the click is in a bridged application and it has the same focus manager as the document". A bridged application that is in a dialog will have a different focus manager than the document.
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-17177
Modified Paths:
flex/sdk/branches/3.0.x/frameworks/projects/framework/src/mx/managers/SystemManager.as

Thanks Jutapa.
When I ran the DPC Latency Checker, there were no significant hiccups, and nothing abnormal at all when the skips occurred. The PCI Latency Tool had no effect on the issue, either (I tried many different latency options, between 0 and 248). But maybe they'll help other people with this or similar problems!
Besides that, I tried logging huge amounts of data with the performance monitor and there's no consistent abnormalities at the times the skips occur as far as CPU usage or any other measurable variables go.
I'll check out http://musicxp.net! I'd tried fresh installs and disabling all unnecessary system services and startup programs before and it also had absolutely no effect, but that's probably not what MusicXP.net advises, so I'll take a look. Thanks!

[svn] 4143: Fixed problem with metadata in SelectionFormatTextStyles. as so that named colors work for selectionColor, unfocusedSelectionColor, and inactiveSelectionColor attributes on Gumbo components.

Revision: 4143
Author: [email protected]
Date: 2008-11-19 14:53:40 -0800 (Wed, 19 Nov 2008)
Log Message:
Fixed problem with metadata in SelectionFormatTextStyles.as so that named colors work for selectionColor, unfocusedSelectionColor, and inactiveSelectionColor attributes on Gumbo components.
Thanks, Glenn!
QE Notes: None
Doc Notes: None
Bugs: SDK-18070
Reviewer: Glenn
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18070
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/styles/metadata/SelectionFormatTextStyles .as
flex/sdk/trunk/frameworks/projects/wireframe/bundles.properties

Revision: 4143
Author: [email protected]
Date: 2008-11-19 14:53:40 -0800 (Wed, 19 Nov 2008)
Log Message:
Fixed problem with metadata in SelectionFormatTextStyles.as so that named colors work for selectionColor, unfocusedSelectionColor, and inactiveSelectionColor attributes on Gumbo components.
Thanks, Glenn!
QE Notes: None
Doc Notes: None
Bugs: SDK-18070
Reviewer: Glenn
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18070
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/styles/metadata/SelectionFormatTextStyles .as
flex/sdk/trunk/frameworks/projects/wireframe/bundles.properties

[svn] 1571: Fix bugs ASC-3310, ASC-3337

Revision: 1571
Author: [email protected]
Date: 2008-05-06 10:58:32 -0700 (Tue, 06 May 2008)
Log Message:
Fix bugs ASC-3310, ASC-3337
ASC-3337:
ASC was emitting multinames for [] access with the wrong namespace set. It was using the def_namespaces, which is a list of open namespaces that conflicting definitions could be found in (public, private, protected, internal for a class). This set does not include any other open namespaces. This changes asc to use the set of all open namespaces, which includes namespaces open by default, and explicitly by the user.
ASC-3310:
LintEvaluator was returning ObjectValue.undefinedValue sometimes from a method that was supposed to be returning a TypeValue. This caused a ClaassCastException later as the return value was cast to a TypeValue. Change to return noType (*) instead of the undefinedValue.
smokes: asc tests, tamarin tests, flex checkintests
Ticket Links:
http://bugs.adobe.com/jira/browse/ASC-3310
http://bugs.adobe.com/jira/browse/ASC-3337
http://bugs.adobe.com/jira/browse/ASC-3337
http://bugs.adobe.com/jira/browse/ASC-3310
Modified Paths:
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/embedding/LintEvaluator.java
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/semantics/CodeGenerator.java

[svn] 3791: Fix bug when resetting stylesheet on FxApplication

Revision: 3791
Author: [email protected]
Date: 2008-10-21 13:23:09 -0700 (Tue, 21 Oct 2008)
Log Message:
Fix bug when resetting stylesheet on FxApplication
SDK-17691 RTE loading styles
When the FxApplication replaces its style sheet, it unloads the previous skin and loads in a new one. With the new skin, it creates a new instance of the contentGroup. However, when the content is added to the contentGroup, it has already been parented by the previous version of the contentGroup. This causes the RTE because the content is not in the correct state.
The solution is to set the old contentGroup's content property to null when we remove the skin. We also force the contentGroup to validate immediately because the new contentGroup was processing its content array before the oldGroup had removed the content as children.
QE Notes: Needs testing
Doc Notes: none
Bugs: SDK-17691
Reviewer: Glenn
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-17691
http://bugs.adobe.com/jira/browse/SDK-17691
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/FxContainer.as

The password history check is not honored in a password reset. It always been like that and it is documented:
"Password History Length Constraint: If all of the following conditions are true, the following constraints MUST be satisfied:
The requesting protocol message is a password change (as compared to a password set)."http://msdn.microsoft.com/en-us/library/cc245669.aspx
So changing it is not a correcting a bug but asking to change the design. From a pure support perspective, you switched from bug request to design change request. Which might still be arguable if you have a solid business case.
Password set is given through an extended right, so by default only administrators or operators have this right. So it comes down to trust those individual. If you cannot, then you don't give them the right and you implement other identity
management solution (Password Self Reset for example).
Other fancy and not useful information:
http://msdn.microsoft.com/en-us/library/cc245692.aspx
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

[svn] 4221: * Fixed issue with signature invalidation.

Revision: 4221
Author: [email protected]
Date: 2008-12-03 06:28:51 -0800 (Wed, 03 Dec 2008)
Log Message:
* Fixed issue with signature invalidation.
tests Passed: checkintests
Needs QA: YES
Needs DOC: NO
Bug fixes: SDK-18242
API Change: NO
Reviewer: Pete F.
Code-level description of changes:
Source.java
Modified isUpdated() to reset the fileTime if it's different from
the lastModified.
CompilerAPI.java
Added updateDependentLastModifiedTimes() and modified
validateCompilationUnits() to call it.
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18242
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerAPI.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/Source.java

Adding a pciture is fine in Mail 2.0.7, just tried
it, added a signature and just dragged and dropped
the .jpg image into the box where you add the text.
Created a new mail and there it was. Regards Jed
This works if you're sending the mail to a Mac user (or to yourself). However, PC users receive this image as an attachment. I have tried all kinds of formats for the image, including wmf, and it always goes as an attachment. Do you know how to send it to Windows users as an embedded signature that appears in the body of the e-mail??

[svn] 2392: Fix bug ASC-3460

Revision: 2392
Author: [email protected]
Date: 2008-07-08 10:55:02 -0700 (Tue, 08 Jul 2008)
Log Message:
Fix bug ASC-3460
Default to double math for constant folding when decimal feature is turned off. This fixes problems where the constant folding would compute certain values incorrectly. 1/30 would become 0 because it did integer math, now we just use Number math all the time.
tamarin tests, flex checkintests pass
Ticket Links:
http://bugs.adobe.com/jira/browse/ASC-3460
Modified Paths:
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/semantics/ConstantEvaluator.java

with me, i tried to run kde by typing kdm, that wouldnt work..
then, i read about some more stuuf you had to download, the names of those files you see when (after installing xorg with hwd: see the link in the main article)) you try to start up x.
just type:
startx
then it will start wining about some things that arent found, use pacman to get those files. if you cant remember them, just type startx again and see.
after doing that, the kdm command still didnt work.
then i just opened up rc.conf with nano:
nano /etc/rc.conf
and added kdm to the deamon line at the end.
DEAMONS=(syslog-ng !hotplug !pcmcia network netfs crond kdm)
then i rebooted and it worked!! kde started up!
hope this helps..

[svn] 4338: Fix bug in previous ClassDefLib.vm submission.

Revision: 4338
Author: [email protected]
Date: 2008-12-16 19:19:16 -0800 (Tue, 16 Dec 2008)
Log Message:
Fix bug in previous ClassDefLib.vm submission. Error shows when using the -keep option.
QE Notes: None
Doc Notes: None
Bugs: N/A
Reviewer:
tests: checkintests
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/gen/ClassDefLib.vm

Hi,
Although not exactly the same type of JVM crash, here is a situation the occurred when switching from JDBC Thin to OCI/Thick:
SQLDeveloper 3.2.20.09 crashes JVM using OCI/Thick driver on Linux 64bit
SQL Developer 3.2 crashes with java error when using OCI/Thick Driver
Did you recently switch your drive type, or client software so that the JDBC driver version changed? Just a guess. If true, read especially the final post of the second thread noted above.
Regards,
Gary
SQL Developer Team

[svn] 1941: Fix bug with writing out a MorphShape2 line style when it has a fill

Similar Messages

Maybe you are looking for