[svn:fx-trunk] 10828: FXG stroke and fill translation fix

Revision: 10828
Author:   [email protected]
Date:     2009-10-02 10:41:48 -0700 (Fri, 02 Oct 2009)
Log Message:
FXG stroke and fill translation fix
http://bugs.adobe.com/jira/browse/SDK-23257 - Gradient translation should occur from 0,0, not the upper left bounds
The current API only passes in the shape's bounds. I have added a new targetOrigin parameter to IFill.begin, IStroke.apply and IStroke.createGraphicsStroke of type Point. It is the origin (0,0) of the shape in the target graphic's coordinate space.
Changed the logic in the gradient stroke and fills. The x and y transform properties are now positioned relative to the origin instead of to the top left corner of the bounds. If no x and y are set, then the default behavior remains the same.
Removed the centering logic in LinearGradientStroke when scaleX was set.
This API change has been approved by PARB.
QE notes: Need to add tests that exercise this logic
Doc notes: Need to document additions to the API
Bugs: SDK-23257
Reviewer: Deepa
Tests run: spark/primitives, gumbo/components
Is noteworthy for integration: Yes, modifications to the API
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23257
    http://bugs.adobe.com/jira/browse/SDK-23257
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/BitmapFill.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/GradientStroke.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/IFill.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/IStroke.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/LinearGradient.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/LinearGradientStroke.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/RadialGradient.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/RadialGradientStroke.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/SolidColor.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/SolidColorStroke.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/Line.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/Path.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/FilledElemen t.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/StrokedEleme nt.as

Similar Messages

Document indesign in xml – stroke and fill the information content in a tag

I want stroke and fill the information contented in a tag. Inside this tag, could be several paragraphs with different styles in paragraph or character.

I want stroke and fill the information contented in a tag. Inside this tag, could be several paragraphs with different styles in paragraph or character.

Suggestion: preview of Stroke and Fill commands

Instead of having to click OK to see the result then, if not happy, having to backtrack and try a variation any number of times, could we see the document updating as we change parameters in the dialogues of Stroke and Fill commands, please? This could be an option that the user can disable, of course.
Ps is the leading app of its kind but in some ways it seems to be clinging onto the early 1990s.

I confused myself earlier regarding the different stroke commands. Yesterday, I had been using "Edit > Stroke" and becoming frustrated with not seeing the result until after clicking OK, then having to repeat the process several times until the result looked good by trial and error. (Yes, I know that Layer Styles give a real-time preview when adjusting stroke, but in this particular case, Edit > Stroke was what I wanted to use.) Then I was working on another image and using "Stroke Path..." to apply a brush. The result wasn't quite right, so I had to backtrack, tweak the brush, apply again, and iterate the process numerous times.
I realise that a real-time preview of "Stroke Path..." would not help when the brush needs adjusted. It would be wonderful if the brush or other tool could be adjusted while the "Stroke Path..." dialogue is open, and have a real-time preview. So, my wish is best generalised to one of real-time preview of most manipulations that the user can make in most dialogues, and for all dialogues which do not absolutely need to be modal to be become non-modal. Changing brush controls while the "Stroke Path..." dialogue is open and seeing the displayed image updating in real time is just one special case of the general principle.
Our modern hardware easily supports such aids to creativity.

Default Stroke and Fill

I would like to remove the keyboard shortcut for default stroke and fill
With object selected, if I type D it changes fill to none and stroke to black. I just want to get rid of this shortcut. I can't find it listed in the keyboard shortcuts

In the Keyboard Shortcuts it's under
Tools
Apply Default Fill and Stroke Colors

Cant use colours in AI free version.stroke and fill options are not active either

cant use colours in AI free version.stroke and fill options are not active either

In the Trial version of Illustrator try this:
In the top right of your screen, choose 'Essentials' from the workspace menu.
Then from the same menu, choose Reset Essentials.
Next, click the Selection tool in the Tools panel (strip on the left side of your screen, it is the black pointer at the top).
Click on the object you want to change the stroke and fill colour for. Does it display with little handles around it (this is called bounding box)? E.g. can you tell it is selected?
You should see the Stroke and Fill options in the Control panel (top horizontal strip above your document), if the object you've selected is a path. But if for instance you selected as a placed photo, you won't see the Stroke and Fill options.
If possible take a screenshot of what you are trying to do, and we can be of more help hopefully.

[svn:fx-trunk] 11885: Integrating Sujata and Min' s changes from the latest approved FXGUtils from CT changelist 633842.

Revision: 11885
Revision: 11885
Author:   [email protected]
Date:     2009-11-16 20:19:46 -0800 (Mon, 16 Nov 2009)
Log Message:
Integrating Sujata and Min's changes from the latest approved FXGUtils from CT changelist 633842.
CT Bugs Fixed:
- bug #2480280 (FXGUtils: pixelHinting setting to true for SolidColorStroke doesn't work.)
- bug #2479187(FXGUtils is drawing compiled FXG items is off by half a pixel)
- Fixed other instances of rounding errors from casting to int.
- Bug 2480289: Compiling richtext content markup in MXML with FlexSDK runtime option is throwing errors.
- LinkFormats cannot be child of tag has children, you do not get a compile error.
- Bug 2477649: FXGUtils needs to support setting justificationStyle to prioritizeLeastAdjustment for RichText.
- Bug 2477661: Incomplete error message when an invalid textAlign attribute value is provided.
- Bug 2444256: FXG compiler fails on percentage lineheight inside formatted text content.
QE notes: Please investigate 2 mustella failures for FXG stroke tests.
Doc notes: N/A
Bugs: N/A
Reviewer: Sujata, Min
Tests run: checkintests, mustella fxg
Is noteworthy for integration: Yes
Modified Paths:
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/fxg/FXGConstants.java
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/fxg/FXGException_en.properties
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/fxg/swf/FXG2SWFTranscoder.java
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/ContentPropertyNode.j ava
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/EllipseNode.java
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/RectNode.java
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/RichTextNode.java
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/AbstractRich BlockTextNode.java
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/TextHelper.j ava
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/TextProperty Node.java
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/types/LeadingModel.ja va
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/swf/ImageHelper.java

Reset Default Stroke and Fill on Path Tools

DUH! I've only done this task a million times before, and now I’m flummoxed. About the third weird thing in as many weeks . . .
Here's what is what: a file I've used before with no problems, suddenly will not let me reset the default settings of no fill and 1 pt black stroke on the path tools. I know how to do it - make sure nothing is selected and then reset the default. Easy peasy.
After I reset, it shows the default settings everywhere (tools panel, control panel, swatches panel) then after drawing the path, the object has no fill and no stroke. I've reset many times and finally understand the definition of insanity: doing the same thing over and over and getting the same result!
I've also tried creating a local defaul with a Cyan fill and a Red stroke, and everything looks good to go, until I draw the rectangle. Then it's no fill and no stroke again.
I'm almost embarrassed asking this question, but now I’d like to know if there is an answer. Is it possible the file is corrupted? If so, is there anything one can do to save the file? I tried doing a Save As and converting it to CS6 but that didn’t work. I’ve rebuilt the Preferences (again).
Thank you (she says, sheepishly)
P. Bell

Thanks, Michael.
You got me thinking about the Object Styles.
I went in and found the Basics Graphic Frame was messed up, so I Redefined the Style and now everything is working.
I needed some fresh perspective. Thanks to you and Bhatnagar for responding to my question.
P. Bell

Stroke and Fill help

I'm trying to set it so that I have a fill color and no stroke with the brush tool. But every time I set it like I want and draw a shape, it switches back to a color stroke with no fill.

Do not select use the brush tool instead use the pencil tool
First double click the pencil tool to show the option select to fill the pencil tool and the selct no stroke and a fill.
The brush tool is a brush and has to have a stroke.

Why when I switch between a centre-aligned stroke and fill do my anchor points move?

Hi there, I've been using Illustrator for many years and never noticed this happen before when I fill a shape - can anyone explain why this is happening?
I'm drawing a logo using a centre-aligned stroke, rounded rectangle and another stroked path merged together to make my logo outline....like this...
....and when I change my centre-aligned stroke from a stroke to a fill and back again (to make the shape solid black), the anchor points of my shape move.....after about 10 time so fswitching between fill and stroke, fill and stroke etc my paths look like this....
Why is this happening??? It doesn't do this when I use a stroke aligned to the outside or inside of the path - just when the storoke is aligned to the centre of the path? CAnanyone explain why this happens? what it going on here?
-thanks in advance!
-Pete Moore

No I don't mean 'outlining' a stroke - all I'm doing is changing a stroke'd box to a fill and back again using the 'Swap fill and stroke" button on the main pallet.
When my (rounded rectangle) path has a stroke applied to it, and it has the stroke aligned to the centre of the path, the anchor points of a rounded rectangle move slightly every time I swap from a filled shape to a stroked shape.
If I apply a stroke to a path (again - a rounded rectangle) that has the stroke aligned to the outside or inside of the path, then the anchor points do not move - however many times I swap between fill and stroke.
I've been wondering why when I re-apply a stroke to a filled object (and that stroke is alinged to the centre of the path) - I get slight movement with the anchor points (do it alot of times and it can really mess with rounded corners).
Draw a rounded square, apply a stroke to it (a center aligned stroke), click the 'swap fill and stroke' button (shift + x) a few times, watch the box move slightly every time you click.
-pete

Does PS CS6 now have 2 ways to add a stroke and fill to a shape?

Using CS6 for web mock ups - so lots of vector shapes.
And now there are 2 ways to do a stroke, 2 ways to do a fill - in the bar at the top or the old effects dialogue box, but gradients and shadows etc are still just in the old dialogue box, not in the top bar.
Is it me or is this incredibly bad app development? Bolt on some new functionality and don't bother about the old stuff so it just becomes one big mess.
Starting to use Sketch now, and really hoping they keep working on it so it makes PS redundant -
http://www.bohemiancoding.com/sketch/

Hello, Elio, there are indeed two different strokes. One is a characteristic of the vector path. Having two allows you to create multiple strokes easily.

Script to click on Stroke and Fill and Swap and Default and ...

Hey gang,
I have been playing with configurator 3.1.1 where you can make a button on a toolbar and supply it with a script. I am trying to make a custom toolbar for InDesign CS6. It already includes buttons for all the tools, except for (I am shocked to note) Stroke, Fill, Swap, Default, Apply Color, Apply Gradient, Apply None, and possibly Formatting Affects Container and Formatting Affects Type. I don't know how to command these missing 7-9 parts of the toolbox panel.
My workaround? Use the Configurator Script button, and supply the button with scripting that calls the functional button command. In reading and researching, I found one command: StrokeFillProxyOptions.FILL which presses the Fill Proxy button.
Alas, I don't have the complete picture. That expression alone does not make the whole clickable script button work. Can you help me write the whole line of script code that would make the button click?
Best to you,
Mike Witherell in Maryland

Hi Michael
app.selection[0].textFramePreferences.verticalJustification = VerticalJustification.JUSTIFY_ALIGN;
Is going to work provided you have the text frame selected. If it's not you'll get an ugly error message.
You can avoid this by
if (app.documents.length && app.selection.length && app.selection [ 0 ].constructor.name == "TextFrame")
app.selection[0].textFramePreferences.verticalJustification = VerticalJustification.JUSTIFY_ALIGN;
if (app.documents.length && app.selection.length && app.selection [ 0 ].hasOwnProperty ( 'baseline' ))
app.selection[0].parentTextFrames[0].textFramePreferences.verticalJustification = VerticalJustification.JUSTIFY_ALIGN;
This will work if the frame is selected (first if statement) or if text if selected or if the cursor is by text (second if statement and do nothing (without giving error messages) if the is no selection or document open etc.
Good Luck
Trevor

[svn:fx-trunk] 12027: Added selectionAnchorIndex and selectionActiveIndex getters to RichEditableTextAccImpl and SkinnableTextBaseAccImpl .

Revision: 12027
Revision: 12027
Author:   [email protected]
Date:     2009-11-19 21:43:31 -0800 (Thu, 19 Nov 2009)
Log Message:
Added selectionAnchorIndex and selectionActiveIndex getters to RichEditableTextAccImpl and SkinnableTextBaseAccImpl. The presence of these getters is supposed to make Player 10.1 and AIR 2.0 able to support text-selection-accessibility for TLF-based text; they are the ActionScript side of the GetSelection() method in Adobe's ISimpleTextSelection COM interface for screen readers like JAWS.
Although Player 10.1 and AIR 2.0 are adding a flash.accessibility.ISimpleTextSelection interface to formalize these getters, we want to be able to compile against the playerglobal.swc for Player 10.0 (or airglobal.swc for AIR 1.5). We could define our own copy of this interface in Flex, but it isn't necessary because the Player and AIR do not actually look at whether an AccessibilityImplementation class declares that it implements ISimpleTextSelection; they only look at whether an AccessibilityImplementation class has these getters.
This way of doing text-selection-accessibility replaces the ITextSupport interface that was in earlier versions of Player 10.1 and AIR 2.0, including the betas. So you try it you must have a very recent build of 10.1 and 2.0.
QE notes: None
Doc notes: None
Bugs: None
Reviewer: None
Tests run: None
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/accessibility/RichEditableTextAccImpl. as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/accessibility/SkinnableTextBaseAccImpl .as

[svn:fx-trunk] 15350: * More package and class level javadoc.

Revision: 15350
Revision: 15350
Author:   [email protected]
Date:     2010-04-12 13:22:21 -0700 (Mon, 12 Apr 2010)
Log Message:
More package and class level javadoc. A small amount of commented
out and dead code removal, too.
QE notes:
Doc notes:
Bugs: N/A
Reviewer: Corey
Tests run: checkintests
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/AbstractSyntaxTreeUtil.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/As3Compiler.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/As3Configuration.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/BytecodeEmitter.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/CodeFragmentLogAdapter.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/CodeFragmentsInputBuffer.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/EmbedEvaluator.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/EmbedExtension.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/EmbedUtil.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/HostComponentExtension.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/InheritanceEvaluator.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/MetaDataEvaluator.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/MetaDataParser.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/OffsetInputBuffer.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/SignatureExtension.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/SkinPartEvaluator.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/SkinPartExtension.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/StyleEvaluator.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/StyleExtension.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/SyntaxTreeEvaluator.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/ArrayElementWatcher.j ava
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/BindableExtension.jav a
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/BindableFirstPassEval uator.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/BindableInfo.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/BindableSecondPassEva luator.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/ChangeEvent.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/ClassInfo.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/DataBindingExtension. java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/DataBindingFirstPassE valuator.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/DataBindingInfo.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/EvaluationWatcher.jav a
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/FunctionReturnWatcher .java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/Info.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/InterfaceInfo.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/PrefixedPrettyPrinter .java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/PropertyWatcher.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/RepeaterComponentWatc her.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/RepeaterItemWatcher.j ava
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/TypeAnalyzer.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/Watcher.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/XMLWatcher.java
Added Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/package.html

Gordon, it looks like its been a while since you made this post. Not sure how valid it is now...   I am particularly interested in the LigatureLevel.NONE value. It seems that it is no longer supported.
How do I turn of ligatures in the font rendering?
My flex project involves trying to match the font rendering of Apache's Batik rendering of SVG and ligatures have been turned off in that codebase. Is there any way (even roundabout) to turn ligatures off in flash?
Thanks,
Om

[svn:fx-trunk] 8530: Change Slider and NumericStepper default value

Revision: 8530
Author:   [email protected]
Date:     2009-07-13 11:17:46 -0700 (Mon, 13 Jul 2009)
Log Message:
Change Slider and NumericStepper default value
http://bugs.adobe.com/jira/browse/SDK-18380 - FxHSlider and FxVSlider have default max of 100, should be 10
Changed the default value for Slider by setting the value to 10 in the constructor. I changed NumericStepper?\226?\128?\153s implementation to match Slider. The problem with NumericStepper?\226?\128?\153s previous implementation was that it wasn?\226?\128?\153t calling Range?\226?\128?\153s maximum setter. Thus there was some important logic in Range.commitProperties that wasn?\226?\128?\153t called.
QE Notes: Update tests with new default
Doc Notes: Update docs with new default
Bugs: SDK-18380
Reviewer: Hans
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-18380
    http://bugs.adobe.com/jira/browse/SDK-18380
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/NumericStepper.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/Slider.as

[svn:fx-trunk] 5554: Updating airframework and flex4 sample eclipse projects to more closely match the options set in the equivalent build .xml.

Revision: 5554
Author: [email protected]
Date: 2009-03-25 13:46:00 -0700 (Wed, 25 Mar 2009)
Log Message:
Updating airframework and flex4 sample eclipse projects to more closely match the options set in the equivalent build.xml.
Modified Paths:
flex/sdk/trunk/development/eclipse/flex/airframework/.actionScriptProperties
flex/sdk/trunk/development/eclipse/flex/airframework/.flexLibProperties
flex/sdk/trunk/development/eclipse/flex/flex4/.actionScriptProperties

If you're still using Buckminster 3.6, I strongly suggest switching to 3.7 - it has a number of bug fixes and improvements. This applies to both headless, and the IDE (assuming Eclipse 3.7 Indigo).
Matthew

[svn:fx-trunk] 10828: FXG stroke and fill translation fix

Similar Messages

Maybe you are looking for