Vector shape- independ on pixel grig snapping

Hi Guys I am wondering. I wanna use to shapee tool or whatever- ractangle tool- Generally said I need to create some shape. But at photoshop is everything snap my new shape to pixels. Like in the backroground is some invisible pixel grids and everything is snaping to whole pixels. I dont want this. I Want to use whole space without automatic pixels adapting to my shapes. I want to be independent in creating my shapes without snaping to pixels grid.
And also want to ask you. If you would like create new guide lines it is non dependable on pixel grid. But after it when I want to snap my nex objects to it- it not possible. And when I tick in preferences/ general: ,,snap vector tool to pixel grid" everything become dependable to pixels and everything is snapping to pixels. I don t wanna this…
please advise.
thank you so much

Untick "Align Edges" in Options bar to prevent shapes being rendered with grid alignment.

Similar Messages

Snap vector shape points to pixels

I'm trying to write a JS script in Photoshop CS5 which will snap all the points in a selected vector layer to the nearest whole pixel. This is extremely useful when producing artwork for web pages, mobile phone apps etc.
I've figured out how to obtain the list of vector points (via doc.pathItems[].subPathItems[].pathPoints[]) and it's easy to quantize these values to the nearest integer. The bit I can't figure out is how to apply the quantized values back to the document. I've tried simply writing the value into the obtained pathPoints[] object but this seems to be read only and any changes made are not picked up by the document.
Would anyone have any advice on the last piece of this puzzle?
The scripting guide has example script for creating a new path (rather than modifying an existing one), so another idea would be to construct a brand new (snapped) path and layer based upon a complete copy of the original, and then delete the original layer. This seems a bit of a long way round though.

For the sake of completeness, but at the expense of some readability, here's a version which deals with multiple selected layers.
The only final issue I have is that my script adds many operations to the history list. Does anyone know how I can make my whole script a single atomic history step?
#target photoshop
// Constants
var QUANTIZE_PIXELS = 1;    // The number of whole pixels we wish the path points to be quantized to
// Some helpers
function cTID(s) { return charIDToTypeID(s); };
function sTID(s) { return stringIDToTypeID(s); };
app.bringToFront();
main();
// Quantizes all points in the active layers' vector masks to the value specified by QUANTIZE_PIXELS.
function main()
    // Work in pixels
    var OrigRulerUnits = app.preferences.rulerUnits;
    var OrigTypeUnits = app.preferences.typeUnits;
    app.preferences.rulerUnits = Units.PIXELS;
    app.preferences.typeUnits = TypeUnits.PIXELS;
    // Obtain the action manager indices of all the selected layers
    var SelIndices = GetSelectedLayersIdx();
    if (SelIndices.length == 1)
        // Only a single layer is selected
        QuantizeVectorMaskForActiveLayer(QUANTIZE_PIXELS);
    else
        // More than one layer is selected
        for (var i = 0; i < SelIndices.length; ++i)
            if (MakeActiveByIndex(SelIndices[i], false) != -1)
                QuantizeVectorMaskForActiveLayer(QUANTIZE_PIXELS);
    // Restore original ruler units
    app.preferences.rulerUnits = OrigRulerUnits;
    app.preferences.typeUnits = OrigTypeUnits;
function QuantizeVectorMaskForActiveLayer(zQuantizeUnits)
    var doc = app.activeDocument;
    var PathItems = doc.pathItems;
    // Nothing to do if the active layer has no path
    if (PathItems.length == 0)
        return;
    var QuantizedPathInfo = null;
    for (var i = 0; i < PathItems.length; ++i)
        var Path = PathItems[i];
        // It would appear that the path for the selected layer is of kind VECTORMASK. If so, when does WORKPATH come into play?
        if (Path.kind == PathKind.VECTORMASK)
            // Build a path info structure by copying the properties of this path, quantizing all anchor and left/right points
            var QuantizedPathInfo = BuildPathInfoFromPath(Path, zQuantizeUnits);
            if (QuantizedPathInfo.length > 0)
                // We've now finished with the original path so it can go
                Path.remove();
                // Add our new path to the doc
                var TempQuantizedPath = doc.pathItems.add("TempQuantizedPath", QuantizedPathInfo);
                // Convert the new path to a vector mask on the active layer
                PathtoVectorMask();
                // Finished with the path
                TempQuantizedPath.remove();
// Copies the specified path to a new path info structure, which is then returned. The function will
// optionally quantize all points to the specified number of whole units. Specify zQuantizeUnits = 0
// if you do not wish to quantize the points.
function BuildPathInfoFromPath(zInputPath, zQuantizeUnits)
    // The output path will be an array of SubPathInfo objects
    var OutputPathInfo = [];
    // For each subpath in the input path
    for (var SubPathIndex = 0; SubPathIndex < zInputPath.subPathItems.length; ++SubPathIndex)
        var InputSubPath = zInputPath.subPathItems[SubPathIndex];
        var OutputPointInfo = [];
        // For each point in the input subpath
        var NumPoints = InputSubPath.pathPoints.length;
        for (var PointIndex = 0; PointIndex < NumPoints; ++PointIndex)
            var InputPoint = InputSubPath.pathPoints[PointIndex];
            var InputAnchor = InputPoint.anchor;
            var InputAnchorQ = QuantizePoint(InputAnchor, zQuantizeUnits);
            // Copy all the input point's properties to the output point info
            OutputPointInfo[PointIndex] = new PathPointInfo();
            OutputPointInfo[PointIndex].kind = InputPoint.kind;
            OutputPointInfo[PointIndex].anchor = QuantizePoint(InputPoint.anchor, zQuantizeUnits);
            OutputPointInfo[PointIndex].leftDirection = QuantizePoint(InputPoint.leftDirection, zQuantizeUnits);
            OutputPointInfo[PointIndex].rightDirection = QuantizePoint(InputPoint.rightDirection, zQuantizeUnits);
        // Create the SubPathInfo for our output path, and copy properties from the input sub path
        OutputPathInfo[SubPathIndex] = new SubPathInfo();
        OutputPathInfo[SubPathIndex].closed = InputSubPath.closed;
        OutputPathInfo[SubPathIndex].operation = InputSubPath.operation;
        OutputPathInfo[SubPathIndex].entireSubPath = OutputPointInfo;
    return OutputPathInfo;
// Quantizes the specified point to the specified number of whole units
function QuantizePoint(zPoint, zQuantizeUnits)
    // Check for divide by zero (if zQuantizeUnits == 0 we don't quantize)
    if (zQuantizeUnits == 0)
        return [ zPoint[0], zPoint[1] ];
    else
        return [ Math.round(zPoint[0] / zQuantizeUnits) * zQuantizeUnits, Math.round(zPoint[1] / zQuantizeUnits) * zQuantizeUnits ];
// Converts the current working path to a vector mask on the active layer. This function will fail
// if the active layer already has a vector mask, so you should remove it beforehand.
function PathtoVectorMask()
    var desc11 = new ActionDescriptor();
    var ref8 = new ActionReference();
    ref8.putClass( cTID("Path") );
    desc11.putReference( cTID("null"), ref8);
    var ref9 = new ActionReference();
    ref9.putEnumerated(cTID("Path"), cTID("Path"), sTID("vectorMask"));
    desc11.putReference(cTID("At "), ref9);
    var ref10 = new ActionReference();
    ref10.putEnumerated(cTID("Path"), cTID("Ordn"), cTID("Trgt"));
    desc11.putReference(cTID("Usng"), ref10);
    executeAction(cTID("Mk "), desc11, DialogModes.NO );
// Make a layer active by its action manager index
function MakeActiveByIndex(zIndex, zVisible)
    var desc = new ActionDescriptor();
    var ref = new ActionReference();
    ref.putIndex(cTID("Lyr "), zIndex)
    desc.putReference(cTID( "null"), ref );
    desc.putBoolean(cTID( "MkVs"), zVisible );
    executeAction(cTID( "slct"), desc, DialogModes.NO );
// Returns the AM index of the selected layers
function GetSelectedLayersIdx()
    var selectedLayers = new Array;
    var ref = new ActionReference();
    ref.putEnumerated(cTID('Dcmn'), cTID('Ordn'), cTID('Trgt') );
    var desc = executeActionGet(ref);
    if (desc.hasKey(sTID('targetLayers')))
        desc = desc.getList(sTID('targetLayers'));
        var c = desc.count
        var selectedLayers = new Array();
        for(var i = 0; i < c; ++i)
            selectedLayers.push(desc.getReference(i).getIndex());
    else
        var ref = new ActionReference();
        ref.putProperty(cTID('Prpr'), cTID('ItmI'));
        ref.putEnumerated(cTID('Lyr '), cTID('Ordn'), cTID('Trgt'));
        selectedLayers.push(executeActionGet(ref).getInteger(cTID('ItmI')));
    return selectedLayers;

Moving selection points in vector shapes

I am trying to align vector shapes in the pixel grid. In CS5 if I needed to adjust my vector shape to lay on the grid, I could nudge vector points in a shape in much smaller increments. I can't move the vector points in CSS that way now.

What is your Photoshop > Preferences > General > Snap Vector Tools … setting?

Vector shapes suddenly looks jagged when exported from InDesign to pdf

I've read several discussions on pdf export topics but none of them seem to solve this issue. I have an indesign document with multiple pages, its both vector shapes, text and pixel graphics. I worked on this for weeks and I exported this document to pdf numerous times and it all looked good every time I did it. All of a sudden I started to get a very bad looking export, just out of the blue the shapes, logos etc got this jagged look and it looks aweful - see my enclosed examples.
I have done nothing to my pdf export setup, InDesign setup or any screen preferances. It's just a mystery to me. It seems to be hurting all my sirculare shapes and not my text in general! Every pixel image / photography exports perfect to pdf. My page display is set to smooth text rendering in my pdf preferences. What's up? What puzzles me is this happened so sudden after numerous fine exports. I'm using InDesign CS6.
This is the O in a logo that's been placed on a page. The right one is what I get when I export to pdf now, the left one is what I used to get

John, your are very wrong about post #2. I personally had a rendering problem that was all solved by setting the opacity to 99.9% - it was exported horribly but fixed by this operation. You can read other user stories that confirms this too. But this is not the same issue so let's leave it at that. I just wanted to mention it in terms of having jagged exports.
There's been no updates thats been changing the Acrobat settings. Acrobat has a default setting in terms of page display that I haven't changed ever as a matter of fact. I shared that info in case someone asked. I'm not connected to any printer, the file is for screen view and third partie receivers can print if they need to (I'm not connected to any printer at work, there's a no print policy). Watching the corporate identity material look terrible on the screen is hardly something a marketing manager likes to do and I don't wanna be the designer responsible for that. So all I want is to solve this mystery and get things back to how it was just two days ago. As described nothing is changed in terms of technical things AND the same terrible results occur when opening a new indd file with a new vector file and exporting that. So the error is not connected to a spesific document or file.
I remember having export rendering problems of all kinds in CS3, CS4 and CS5, it was all sort of quirky operations I had to do to solve them. Once I actually sat on the phone talking to a technical advisor at Adobe in Ireland while he was trying to explain that this was one of those weak spots of InDesign vs Acrobat. I was emailed a script, if that's not a bugfix I don't know what is. He tried to explain how to embedd the file into the installation setup but the end of the story was a full CS4 MA Collection refund. I'm trying to avoid placing foreign calls this time around and nothing has helped so far. I've been reading endless forum threads different places that describes the problem I have but they never end up with a solution for InDesign CS6 and export routines. It's just a series of errors and questions. I've turned the stone a million times, but all I see is...stone

Holding Shift when creating Vector Shape - No snap to pixels!

Hi there,
Adobe Photoshop Version: 13.0.1 (13.0.1 20120808.r.519 2012/08/08:21:00:00) x64
Operating System: Windows 7 64-bit
Version: 6.1 Service Pack 1
I'm experiencing the following problem:
When creating vector shapes and holding shift the shape do not snap to pixel. Snap to pixels is turned on.
It is pretty strange.
Please check the video below:
http://screencast.com/t/1iys3tDJHpJt
Initially when do not hold shift shapes is pixel perfect. As you can see in the image first 2 shapes are made free hand.
SK

Instead of holding the shift key try pressing the + key to change the path operations to Add to Shape Area and the - key to subtract from shape area.
That is strange behaviour compared to cs5 where having snap to pixels checked for the rectangle tool does align the edges when holding down shift
where as cs6 13.01 doesn't align the edges when holding shift either with the snap vector preferences of align edges checked.
It only seems to align the pixels when snap vectors in the preferences is checked and using add to shape area is actually selected in the drop down.
That's what the plus key does.
I guess i was under the impression that align edges was supposed to be the same as the snap to pixels was in cs5.
Message was edited by: R_Kelly

CS4 Vector shapes look pixelated

I'm new here. In fact I just signed up to get help with this issue.
Anyway. In school last semester, I took a computer art class in which we made things in Photoshop CS4. Now that the semester is over, I took my work home with me (I also have PS CS4). Anyway, one of the exercises we did was creating vector art. In school, the vectors that I made turned out fine. The edges were clearly defined and there where no real issues to be see. However, when I took it home to look at it, I noticed that all of the vector shapes and lines look pixilated... as if I drew them with a brush or something.
Here is a screenshot of what it looks like in CS4:
Also, for clarification, here is another example:
First, the new image settings:
Red elipse:
Zoomed in:
Anyway, I admit to not being 100% knowledgeable in the program... so it might just be a silly simple mistake or setting that I don't have checked or something. Any help would be appreciated as this issue is really annoying me.
Also, if it matters, my computer is much better standing that the ones we used in school.

Two things:
First, if the Vector Mask path is active in the Paths panel, the path will be visible. This can cause the edges of shapes to look raggedy.
The main culprit, though, is that you need to view the image at 100% (Control+Alt+ZERO, 'Actual Pixels' in the Zoom tool Option Bar) for the shapes to look smooth. Very often, viewing at other than 100% can cause visible artifacts to appear on the screen that aren't actually in the image.

Pixel perfect vector shapes

Hi There,
How do you get Fireworks to display/output sharp edges? I'm using a 10px x 10px grid which I'm snapping to and all my shapes are exact pixel dimensions but still don't get sharp edges.
Is there a trick to achieving this?
Cheers

You should try setting stroke alignment to outside or inside of shape to get pixel perfect strokes and set stroke itself to full pixels. As per CSS box model borders are outside of box dimensions, but I prefer setting them to inside in Illustrator so that I can control visual dimensions of blocks.
I'm using Illustrator for most of my web designs and the hardest part is to get new objects to be in precise pixel dimensions. Snapping is not pixel perfect unless you turn on pixel preview and snap to pixel options. Drawback of enabling 'pixel preview' and 'snap to pixel' is that smart guides are then turned off.
Currently I am looking for a solution to make existing designs pixel perfect. That could be some kind of script which iterates over all selected objects and rounds position and dimensions to full pixels.
It's tiresome to correct hundreds of imperfectly placed and sized objects in designs created by web-unaware designers.

How do I change the units for the vector shape stroke in the option bar?

I work with vector shapes very often in Photoshop. In CS6, they have added the stroke and fill tools in the option bar.
If I open a file with vector shapes that was created in CS5, the stroke defaults to 3pt. I would prefer it to default to pixels instead of points. I have found that if I change the settings prior to creating a new shape, it retains those attributes for all future shapes. However, if I am working on an older file, and would like to use this tool, it is frustrating to have to change this unit every time.
Any assistance would be helpful. Thanks!

Every time I move the volume, it moves back!
Check, if you have a volume automation set on the software instrument track.
If the track volume automation curve is enabled, the volume slider for the track will move with the automation curve.
Click the automation curves disclosure triangle in the track header and disable the volume automation.

Why do vector shapes in scaled smart objects blur?

This remains a point of frustration.
Why does converting a vector shape to a smart object in Photoshop mean that it's then treated as a bitmap and blurs when scaled up?
If i paste the same vector shape into Illustrator and then back into Photoshop as a smart object it then behaves correctly, and remains sharp.
See the image for example of what i mean. Left is the master shape, centre is it converted into a smart object in Photoshop, right pasted to and from Illustrator. These were then scaled 300% resulting in the centre one blurring.
I don't really want to have to invovle Illustrator in this way and keep all my vector work in Photoshop now it has the tools to do so, but this issue creates me a lot of extra work.
Or am i doing something wrong?
Rob

Smart Object layers are transform to other sizes through interpolating the pixels rendered for the embedded object not be using vector graphics on the embedded object.. If your resize resizes the pixel count way un the image will become soft. Yoy can try seting your Photoshop Default interpolation setting to other setting then Adobe default Bicubic Automatic to something like plain bicubic which IMO is a better general purpose option then Bicubic Automatic.
You can also open the embedded object by double clicking the smart layers smart object icon in the layers palette. Once opened in Photoshop resize the vector graphic using Image size and save the embedded vector object larger. Photoshop will update the smart object layers content then.

"Controlled" Rounding of Vector Shape Corners

I know how to drag the corner box to vary the amount of curve in a rounded corner rectangle, but is there a way to set the value, similar to numeric transform?
If you are making lots of rounded corner shapes... like for buttons throughout the site, and containers, say for content areas, it would be handy to be able to set the amount of roundness exactly, so all are pixel perfect the same.

Starting from the rectangle "primitive" vector shape there is a box that appears at the bottom of the property inspector in the stroke section under texture labeled roundness that controls the radius of the curve as described by Pete-1967 above.
Starting from the auto vector shape. rounded rectangle, that roundness selector in the property inspector disappears. It would seem only natural to include that control in that location for that shape. It may have something to do with the difference between primitive shapes, those three that appear first in menu under the vector shapes tool and auto shapes. As noted above, the auto shapes are controlled in the auto shape properties panel, which is not opened automatically in the expanded mode, but can be found unded Window --> Auto Shape Properties.
My initial confision over this stems from a couple of user interface issues inherant in Fireworks CS4. Firstly, and Jim Babbage warns about this either in his greatClassroom In A Book, or his equally excellent videos located on Lynda.com.... I could just here his voice chiding me when realized my mistake after posting this thread... ( I can't remeber everthything!! ) the properties inspector has three states controlled by the little arrows next to " Properties". The properties inspector can be completely rolled up with only the tab showing, halfway rolled up with only the top half of the properties inspector showing and all the way unfurled completely showing all the available controls. There is NO indication to the user that there is more information hiding when it is half way open. I had it in that state, and therefor could not find the controls pointed out in this thread by Pete. Adobe should put a visual que, like one uses on a nested menu, for example, to que the user that there is more information hiding, and a click on the control is required to reveal it.
Thanks to Dave, I found the auto shapes properties panel.... should have looked harder I guess, but wouldn't it make more sense from a UI ease of use standpoint to put auto shape PROPERTIES in the PROPERTIES inspector? Oh well, now I know where it is
These Adobe programs are great... they are also vast, so when I forget where something is, or can't find something, it's a pleasure to be able to come here get pointed in the right direction. This post is intended clearify this thread to help others who may arrive here in the future.
The Properties Inspector Halfway Open:
The Properties Inspector All the way Open:
The Auto Shapes Properties Panel: Window --> Auto Shape Properties:

Vector shape to smart object, is blurry when scaled

I've recently been upgraded to Photoshop CS5.5 and am having issues with smart objects.
Quite often I would:
make a shape layer, say a circle
apply a layer style, say a stroke and drop-shadow
Convert this to a smart-object
Resize this object to whatever I needed and it would scale perfectly, the layer styles and crisp edge would scale.
Now, when I use this same workflow, the whole object becomes blurry - like it's become one giant bitmap instead of retaining its original nature.
The blurred smart object loses it's vector nature and looks horrible, this is surely an error.

It depends on how you scale the smart object layer. If you just use Ctrl+T free transform Photoshop will matieilize the pixels for the layer then resize the materilazed pixel layer like normal raster layer not text not a shape layer. If on the otherhand you double click on the smart object icon in the layer in the layers palette Photoshop will open the smart object in photoshop. If it a RAW file it wil open in ACR. If is is a Photoshop Document like a PSD, Tif, Jpeg etc it will open in Photosgop. If it is some Photoshop object like a layer group a collection of layers an vector shape layer it will open in Phpotoshop. You can then scale the smart object with Photoshop tools like ACR or Image size set resample constrain scale layer style etc to scale the smart object when you use save the change Photoshop will update the smaer object layer in the document. You can do the save by clicking the Close icon and respond yes to save. Scaling the smart object layr this way will scale text and vectors the way you want them to be scaled.
http://forums.adobe.com/message/3498406#3498406

BUG? - Vector shapes move after when resizing PSDs with layer comps.

I use layer comps to show different interaction steps through my designs.
Designing mostly for mobile, i create at @1x (72 Pixels/Inch) resolution, and then scale up to @2x (144 PPI) and @3x (216 PPI) to get my assets for higher resolution devices.
However when i scale the PSD, all vector shapes within it offset themselves by one pixel up and to the left for @2x resolution and two pixels for @3x resolution, meaning all my careful alignments go out the window. Raster elements and text fields behave as they should and do not shift.
All my vectors shapes are bang on the the pixel to begin with so that's not a factor, and the scaling is a multiple so again that isn't the cause either.
You can see the issue in the image attached.
The obvious white edges along the right and bottom edges are revealed after the scale and layer comp change as the shapes shift.
The bitmap layers equivalent on the right are fine.
You can try it for yourself by downloading this PSD...
http://neonstate.com/scale-layer-comps-test.psd
1. Open the file
2. Change the resolution by going to Image / Image Size and entering 144 or 216 as the resolution.
3. Step through the layer comps, you'll see after the first layer comp is changed that the vector shapes shift, affecting all layer comps.
I'm sure this didn't used to happen, but what it means is I can no longer use this technique.
I'm using Photoshop CC 2014.2.2 / 20141204.r.310 x64
Any help much appreciated.
Rob

Hi again,
The purpose of this checkbox in the Layer Comp settings is to remember the positions of items, if you turn it off then you can save the positions which defeats the point a bit.
I've created another example to better explain - http://neonstate.com/scale-layer-comps-test-reposition.psd
If you step through the layer comps you'll see the shapes move from one position to the next, i've set these positions specifically.
Now change the resolution to 144 or 216.
Everything looks fine until you step through the layer comps - the boxes change position as they should, but the vector ones are incorrectly offset to the top left.
Rob

CS6 : How to convert a path stroke in a vector shape ?

Hello,
When you use the Photoshop CS6 new function stroke on the path of a vector shape, how can you convert the result in a vector shape ?
Merging multiple vector shapes doesn't work. The strokes outlines are not vectorized in the new vector shape.
It's possible to convert in pixel and keep the stroke drawing, but no way to convert in vector.
Illustrator has a similar function in order to vectorize the stroke.
Thanks for your help

Yes, I misunderstood.
Photoshop has no command to directly create a new vector path from the outline of a stroke.
You could try making Path from Selection. With the Shape on a white background, click on the pink with the Magic Wand Tool with options as shown below:

Tweening dynamic vector shapes

So I am wanting to blend/morph/tween a sequence that gives a
rectangle the appearance that it is "snapping" in place by bowing
and pinching the shape. Hopefully this image helps explain it.
http://members.optusnet.com.au/expansiondesign/Picture%201.png
Just imagine that the blend is happening in the one spot;
that the 4 shapes are sitting on top of each other.
Ignore the colour.
The only way I know how to do this is with frame by frame
animation and exporting/importing each image step from illustrator.
But I've done that before and it is too tedious.
I thought maybe there was someway to edit the points of a
vector shape at different keyframes?
Thanks

vertexList is the property you that you can control for a
vector member.
A quick demo at:
http://www.directoratnight.com/2006/08/22/vertexlists-go-morphing/
and here is a quick behavior that will tweak a rectangle
property pSprite
property pMem
property pW, pH, pD, pTheta
property pCounter
on beginSprite me
pSprite = sprite(me.spriteNum)
pMem = pSprite.member
pW = 200.
pH = 100.
pD = 20.
pCounter = 0
end
on exitFrame me
pTheta = pCounter * pi() / 180.
me.setToShape()
pCounter = pCounter + 5
if pCounter > 180 then
pCounter = -180
end if
end
on setToShape me
p1 = point(-pW, -pH)/2
h11 = pD * point(cos(pTheta), -sin(pTheta))
h12 = pD * point(-cos(pTheta), sin(pTheta))
p2 = point(pW, -pH)/2
h21 = pD * point(cos(pTheta), sin(pTheta))
h22 = pD * point(-cos(pTheta), -sin(pTheta))
p3 = point(pW, pH)/2
h31 = pD * point(-cos(pTheta), sin(pTheta))
h32 = pD * point(cos(pTheta), -sin(pTheta))
p4 = point(-pW, pH)/2
h41 = pD * point(-cos(pTheta), -sin(pTheta))
h42 = pD * point(cos(pTheta), sin(pTheta))
aL1 = [#vertex:p1, #handle1:h11, #handle2:h12]
aL2 = [#vertex:p2, #handle1:h21, #handle2:h22]
aL3 = [#vertex:p3, #handle1:h31, #handle2:h32]
aL4 = [#vertex:p4, #handle1:h41, #handle2:h42]
myVertexList = [ aL1, aL2, aL3, aL4]
pMem.vertexList = myVertexList
end

Scaling layer styles on a vector shape

How do you get the Layer styles to scale as you transform, on a vector shape, to a larger scale, so that the larger shape has the same look at the smaller version?
Thanks

Not possible. Layer styles are applied to rasterized pixels even for vector layers and have no knowledge of your intentions. Duplicate the image, resize it using the image size dialog with the option to scale layer styles, copy&paste the resized result back to your source document. To my knowledge the only reliable way. You may still need to adjust the layer style, though, as several of them do not use sub-pixel precision and may be rounded of to the wrong next value, making it look goofy.
Mylenium

Vector shape- independ on pixel grig snapping

Similar Messages

Maybe you are looking for