Currently using the CS6 trial. I have issues occasionaly when trying to make the stoke less than 1pt, it either immediatly flicks back to 1pt, or says 0.5pt and hasn't changed on my artboard. Is it a glitch with me or illustrator?
I agreee with Monika it is the align to pixel option and you must have it turned on.
If you are making a web document it is turned on my default
the transform panel reflects this unless you do not have the options of the transform panel opened.
here it shows it
Here it doesn't
Here witht the option I choose .5 pixels in the stroke panel
The result is 1 pixel
This is the only way this situation manifest itself.
On the web you cannot have less than a pixel.
Otherwise you must have something installed on your system that is drastically effecting AI CS 6.
But I am certain that Monika is correct.
Rodieck you are missing the point if you have align to pixel option turned on then it will not be possible to assign a weight of less than a pixel because of the nature of align to pixel.
So if youwant to assign less than pixel you hsave toturn thr option off before the weight field will allow it.
But according to her message 2 above, the align to pixel grid is off.
Unknown, however, is which "align to pixel grid" option is turned off. Turning off the option to create new objects aligned to the pixel grid does not retroactively undo the object-specific align to pixel grid option for objects which were created while the former was turned on.
So if the object being manipulated was created while the create new objects... option was on, it will still display the unwanted behavior of snapping Stroke Weight to integer values, unless the object-specific option is also turned off.
It's just another typically horrible interface for another typically ill-conceived and poorly-implemented feature. Another source of chronic Illustrator confusion.
This hideous feature should just be done away with. Other drawing programs are routinely used to rasterize graphics for use on the web without such a cumbersome interface feature. As implemented, I dare say this feature creates more headaches for far more users than those whose complaints (mostly about unwanted antialiasing of screen-res strokes) gave rise to it.
JET
You can also simply open the web rgb document turn it off and replace it then it will always be that way.
You find the document profiles here you need to right click or control click on the Illustrator Application and choose Show Packages.
You make the changes then resave the file by doing a save. I am not certain if it is possible to do a Save As to the packages so do a simple save.
They're are in the required folder.
If you ever wish to do a custom arrow head or 3D extrusion profile they are also located in thye Packages.
It actually feels more like a bug then a poor implemented feature to me...
I'm using CS6 for a week now, and I use it to create "technical drawings" (Illustrator just works for everything right) that can be cut using a laser cutter; something totally different then web design, which relies on pixels and rasterisation processes.
I found that even in a Print/CMYK document the strokes of the rectangles would not go below the 1 pt, and immediately jump back. According to my reasoning, this has nothing to do with any of the pixel grid align functions, since I am working in a document with millimeters as the standard measure and pt to define stroke size. In CS5 I did not have these problems and I could easily set the stroke to the desired size < 1pt.
So my thought is: maybe it's an actual bug, these pixel grid options should be ignord when working with print intention right?
pep_F wrote:
So my thought is: maybe it's an actual bug, these pixel grid options should be ignord when working with print intention right?
Depends on how you set up that document. The setting is defined in the document profile. If this is set up correctly, then, yes, Pixel grid is ignored.
pep,
There is another possible reason, namely a decimal mark mismatch: in English (with the exception of South Africa, I believe), the decimal mark is a stop (period), and in (some/most) other languages it is a comma (I believe).
Your OS and Illy may disagree about this and make a mess. Illy is right (and in any case you will have to indulge her).
You can see whether that is the issue if you try to create a 0.5pt stroke by typing it in the value box, first with a stop, then with a comma, and see whether either works.
If it works with he opposite decimal mark of the one used in the dropdown you have the mismatch; you may change the decimal mark in the OS Regional & Language settings.
If not, it is something else.
"It actually feels more like a bug then a poor implemented feature to me..."
I agree, I've noticed I can have two objects with "align to pixel" off and the appropriate global settting has been turned off; then, when I do a boolean operation suddenly the new object has "align to pixel" on and all the anchor points get skewed. Not helpful at all.
.... I agree, I've noticed I can have two objects with "align to pixel" off and the appropriate global settting has been turned off; then, when I do a boolean operation suddenly the new object has "align to pixel" on and all the anchor points get skewed. ...
This happens when you have the "Align New Objects To Pixel Grid" checked in the menu of the Transform panel accessible from the top right corner of the panel.
North America
Europe, Middle East and Africa
Asia Pacific