Snapping bug in Illustrator CC?
Hello. I've an issue with Illustrator CC. When moving more than one point of an object, the points snap to some predefined pixel grid... You'll notice from the attached images - the second image shows the first scaled down to about half the size - the 'slits' on the side elements have either been widened, or reduced to nothing (as shown by the last image)...
I've used illustrator since version 9, so am used to using the application. Snap to grid and pixel are both off (as is pixel preview or anything else that defines how the image is viewed), so believe this to be a bug - a very annoying bug that effectively renders the application useless for precision illustration.
Any thoughts? Many thanks!
Paul,
In the Transform panel, select everything and untick Align to Pixel grid, this frees the present objects, then in the Options untick for New Objects.
You may avoid using (RGB) document types made for web and similar uses. or change their default to have Align to Pixel Grid unticked.
Edit: Hi Monika.
Similar Messages
-
Bug Found: Illustrator CC *always* merges layers when opening a DXF file - CS6 works properly
Bug Found: Illustrator CC *always* merges layers when opening a DXF file - CS6 works properly. When opening a DXF, CC merges multiple layers into one, even if you have the "Merge Layers" unchecked. Can a forum admin employee get this submitted as a bug report? Thanks.
Thank you Larry. I just submitted this bug report pasted below at the link you provided.
******BUG******
Illustrator CC 17.0.0 *always* merges layers when opening a DXF file, even if you have the "Merge Layers" unchecked.
1. Open a DXF file that contain multiple layers in Illustrator CC 17.0.0
2. Uncheck the "Merge Layers" button.
3. Click OK.
Results: It has merge all the layers into one layer.
Expected results: It should open with multiple layers preserved. Illustrator CS6 works properly. -
Mitering Bug in Illustrator CS4?
I finally bit the bullet and moved from Illustrator 10 to CS4 this winter. So far, it's been great! I don't regret it at all. On my very first project, though, I noticed that CS4 seems not to miter certain small paths correctly. At first I thought my geometry might not have been exact, but I opened the same file up in version 10 and the mitering is perfect. Has anyone else noticed this? I'm attaching two images of the same file, one opened in version 10 (with the mitering I had expected) and one in CS4 (with the incorrect mitering, circled in red).
I will add this to Wade's list too, but wanted to see if anyone else had had this problem. If not, where is the appropriate place to report a bug?How were you able to get the coordinates of the direction handles?
The dialog shown in the screenshots is a Script Alert. It's one of a handful of very simple "get info" Javascripts I use to obtain specific info about selections when working on more elaborate scripts.
//--start script
var docRef=app.activeDocument;
var pathRef=docRef.selection[0];
var pointsRef=pathRef.pathPoints;
var pointsCount=pointsRef.length;
for(i=0;i<pointsCount;i++){
var pointRef=pointsRef[i];
var myReturn="\r";
if(pointRef.selected==PathPointSelection.ANCHORPOINT){
alert("Anchor "+i+" X: "+pointRef.anchor[0]+myReturn+
"Anchor "+i+" Y: "+pointRef.anchor[1]+myReturn+
"LeftDirection X: "+pointRef.leftDirection[0]+myReturn+
"LeftDirection Y: "+pointRef.leftDirection[1]+myReturn+
"RightDirection X: "+pointRef.leftDirection[0]+myReturn+
"RightDirection Y: "+pointRef.rightDirection[1]);
//--end script
And how were you able to numerically adjust them?
I didn't. See the guides in the second screenshot? I just snapped a horizontal ruler guide to the bottom of the extended handle and a vertical ruler giude to the anchorPoint. Then I snapped the handle to the intersection of the two guides.
What a cool feature that would be.
Javascripts can be used to set coordinates of anchorPoint anchors and handles. Some of my scripts do. But you would have to be carefully specific about what exactly you want the behavior of the script to be. For example:
FreeHand has for decades provided retract and extend buttons for incoming and outgoing handles. Those buttons would fix your specific problem with a mere couple of clicks. Illustrator only just very recently got around to providing point kind (corner or smooth) conversion buttons in its Control Panel--and those fall far short of the functionality and utility of FreeHand's treatment. The FreeHand functionality could be constructed in Javascript without too much difficulty (the auto-extend portion of it would be the trickiest), so I would think it should be a piece of cake to build it into the program.
But don't hold your breath. The program still can't join more than two open paths at a time, either.
By the way, five out of the twelve innermost points of your path are Smooth Points. Unfortunately, Illustrator's convert buttons retracts the handles when you convert to cornerPoints, and doesn't give you any option to specify otherwise. See that little Automatic checkbox in FreeHand's Object inspector? Also, note how easy it is to differentiate between selected corner (round) and curve (square) points in FreeHand:
If I had but one pathpoint selected, its position would be shown above, too. In fact, in this one tidy palette I can see and set important things about a selected path or pathpoint for which in Illustrator you have to visit the Appearance, Attributes, and (of all things) Document Info palettes.
JET -
Major font substitution bug in Illustrator CS5
Hi all,
This took me a good long time to track down, and since I didn't find any information here and Adobe technical support was no help, I figured I'd post the result. Happy new year.
Here was the problem. Working in CS5, intermittently we would get font reflow issues. In addition, when going to edit the type boxes with font reflow, we would get the message, "This text was created in a different version of Illustrator. Editing the text may cause some changes to your text layout. Basic formatting will not be affected. Do you want to continue?" Please note it says "different version" rather than "previous version". These files originated and stayed in Ilustrator CS5! If we hit OK, the type would snap back to the original state!!! Worse, if the type was copied and pasted, or anything in character or paragraph styles was edited, it would snap back without ANY warning. Now you see it... now you don't. Major problem in any print environment.
So here is what I found, and this is a CS5 exclusive. If you are working on a file and have a font set open which includes a font from one foundry, and then opened another document and activated a font set with an identical font from a different foundry (the original font closing), the kerning for the original document (in the background now) would be set to zero (rather than auto) and the font would reflow. If you didn't notice the reflow, and saved the file, well it would create the condition as described above. Of course it isn't ideal to have the font foundry change like that, but bottom line usually you could get away with it... maybe with one or two characters moving slightly. In the new CS5 world, Illustrator decides you really don't need ANY kerning pair information and then helpfully tells you it was a "different" version of Illustrator that caused this. Heh.
What a mess. Bottom line, make sure your font management application is set to throw warnings when conflicting fonts are opened, and most importantly, leave the original font open! Do not allow the new font to be opened until the conflict is resolved.
If your font management application does not have this option (Universal Type Server 1 did not), you better upgrade or forget about using Illustrator CS5 in a heavy production environment.
Adobe, this was a major change and a major headache. You have some explaining to do...Confirmed this is being generated entirely in CS5. I opened the font Sabon. I created a text box. I pasted in some generic type I had just made in text edit. I changed the font to Sabon and the paragraph to justify. I saved and closed the document and closed Illustrator. I closed Sabon and opened Sabon from another foundry. I opened Illustrator and opened the document. All looked good. I duplicated the text box over and outlined the type. I went into the font manager and closed Sabon. I opened the original Sabon. DING! Type reflow. I saved as a second document. I copied the outlined type and closed the document. I opened the original document (note the original font is open). No problems. I paste the outlined type (type outlined with the wrong version of the font active) and it lands exactly in place. I open the second document. The type that reflowed now gives me the stupid message about another version of Illustrator screwing it up. I hit OK and the type reflows back to the way it is supposed to be.
This proves that the kerning changes weren't due to differences between the fonts. This proves that Illustrator CS5 has a MAJOR type engine bug that could easily spell disaster in production. -
How to snap guides in illustrator?
hello
id like to know as in ps we can snap our guide lines to the middle of the canvas and they snap making a nice intersection so we know where the middle of the canvas is,so we can place our object,how can it be done in illustrator?the guide lines do not snap,although snap to point is checked.do i have to make the canvas a perfect symmetric and then use the grid in order for the guides to snap?
any suggestions?
thank you.seems reasonalbe,but im trying to align the guide lines i make 2 of em in the centre of the canvas,then i select them both and in the align pallet i click on horizontal align centre and then vertical align centre,BUT and the guides dont align in the middle of the canvas but outside on the boundareis on the white canvas.
i do have also the aligh to art board checked as well.
whats going wrong? -
Possible bug in Illustrator CS4 text anti-aliasing in Save for Web and Devices
Hello all,
This could be a bug... if so, I'd be happy to add it to Wade's bug list a few messages down the stream.
Here's what's happening: when I create small text using a very thin font (in this case, Helvetica Neue Light), the Pixel Preview gives a noticeably different anti-aliasing solution to the actual output from Save for Web & Devices. I'm attaching an original .AI file as well as a screenshots of what I'm getting in both situations.
I'd really prefer the Save for Web and Devices output to look exactly like the Pixel Preview. The font looks great in Illustrator but loses a lot of its punch when I Save for Web.
---PeterIn the Svae for Web and Device under the image tab where it says art Optimize that is a drop down menu select Type Optimize as such
htis is what it lloks like in AI and a browser when you choose Type Optimize
This the difference between Art Optimized and Type Optimize
That is what is happening to you you are selcting Art Optimize and that is the reason when you choose art optimize aqnd you rraster the image it looks right to you. -
Color manager bug in illustrator cs5
i try to change objects colors via the color manager with a cmyk code for the new color. the color of layers i changed already changes while i'm changing the other layers. It takes 5-6 time before the right color stay. why? is it a bug? i would like to set the same color for all layers ...thanks
Confirmed this is being generated entirely in CS5. I opened the font Sabon. I created a text box. I pasted in some generic type I had just made in text edit. I changed the font to Sabon and the paragraph to justify. I saved and closed the document and closed Illustrator. I closed Sabon and opened Sabon from another foundry. I opened Illustrator and opened the document. All looked good. I duplicated the text box over and outlined the type. I went into the font manager and closed Sabon. I opened the original Sabon. DING! Type reflow. I saved as a second document. I copied the outlined type and closed the document. I opened the original document (note the original font is open). No problems. I paste the outlined type (type outlined with the wrong version of the font active) and it lands exactly in place. I open the second document. The type that reflowed now gives me the stupid message about another version of Illustrator screwing it up. I hit OK and the type reflows back to the way it is supposed to be.
This proves that the kerning changes weren't due to differences between the fonts. This proves that Illustrator CS5 has a MAJOR type engine bug that could easily spell disaster in production. -
Bug in Illustrator CS2-CS5.1 beim SVG Speichern
Mittlerweile ist klar, das ist ein Fehler im Programm, getestet mit Illustrator CS2, CS4 und CS5.1 .
Was muss man wo tun um ein Hotfix zu erhalten?
Wohin muss ich mich da wenden und was kostet's ggf.?
Eine Kollegin hat herausgefunden, dass Illustrator bei eingestellter Codierung UTF-8 nicht in UTF-8 exportiert, sondern in ANSI.
Wenn UTF-8 drauf steht, aber ANSI drin ist, passt das natürlich nicht zusammen
D.h. im XML Quelltext steht UTF-8 drin, aber es ist eigentlich ANSI, das führt dann zu Interpretationsfehlern.
Witzigerweise kann AI sein gerade gespeichertes SVG noch nicht mal selbst öffnen.
Beispiel:
Öffnet das Pseudo-UTF SVG mal mit den normalen Windows Editor, anschließend geht ihr auf "Speichern unter", der Editor schlägt vor, in ANSI zu speichern, heißt die Datei ist eigentlich ANSI kodiert. Speichert man das SVG mit dem Editor dann nicht unter ANSI, sondern als UTF-8 ab, gibt es plötzlich keine Anzeigefehler mehr, weder im IE noch im Firefox.
Habe mittlerweile die Möglichkeit gehabt es in CS5.1 zu versuchen, selber Fehler.
Gibts dafür vielleicht schon ein Fix?
Wir steigen nun von CorelDraw auf Illustrator um, zu Testzwecken habe ich im Mom zwar nur CS2 drauf, aber CS5.1 wird folgen.
Es geht darum maussensitive SVG's zu erstellen, d.h. bei einigen Objekten werden Grafikattribute hinterlegt um das SVG hinterher interaktiv machen zu können.
Problem:
Das Grafikattribut ist als "Imagemap: Polygon" gesetzt und sieht in etwa so aus: "Þg;8314;S005Þ"
Problem:
Leider werden Objekte die mit diesem Attribut im SVG später nicht angezeigt(siehe "Link mit Zeichen"). Wenn ich das Thorn "Þ" weglasse, werden die SVG's richtig angezeigt (siehe "Link ohne Zeichen").
Im IE8 werden Objekte im SVG mit diesem Thorn einfach weggelassen, der Rest wird angezeigt.
Im Firefox wird das SVG gar nichtt angezeigt und er gibt einen XML-Verarbeitungsfehler in der entsprechenden Code Zeile aus.Confirmed this is being generated entirely in CS5. I opened the font Sabon. I created a text box. I pasted in some generic type I had just made in text edit. I changed the font to Sabon and the paragraph to justify. I saved and closed the document and closed Illustrator. I closed Sabon and opened Sabon from another foundry. I opened Illustrator and opened the document. All looked good. I duplicated the text box over and outlined the type. I went into the font manager and closed Sabon. I opened the original Sabon. DING! Type reflow. I saved as a second document. I copied the outlined type and closed the document. I opened the original document (note the original font is open). No problems. I paste the outlined type (type outlined with the wrong version of the font active) and it lands exactly in place. I open the second document. The type that reflowed now gives me the stupid message about another version of Illustrator screwing it up. I hit OK and the type reflows back to the way it is supposed to be.
This proves that the kerning changes weren't due to differences between the fonts. This proves that Illustrator CS5 has a MAJOR type engine bug that could easily spell disaster in production. -
"Verdana missing" bug in illustrator CC on Mac
Hi Adobe,
I just called your outsourced phone support at the request of the tier 1 support/chat and they were unable or unwilling to address this issue and I was told to start a new thread here to try to get the attention of the programmers. For some reason, Illustrator CC stops working randomly, and asks for the font Verdana. It's installed, and active, in all 4 flavors but Illustrator can't or won't see it. In my experience a restart fixes the issue, but it will return again within a week and this has been happening since about mid-December 2013, or about 2 months. I am up to date on all cc files, and am running OSX v10.9.1 and I find it a vexing problem that this verdana font, which I *never* use is crashing your software and I see it as a threat to my livelyhood and sanity! What is being done to fix the dependancy that Illustrator has on this font? Why don't the tech people know about the issue when it is clearly a known issue on the discussion boards? Why are your previous threads about the issue closed without a clear resolution? What changed in the most recent version to create this dependacy on a system font that has *no business* being used for design work? I await your response...Yes Monika, they are there as I previously stated....
**please do not post to this thread without reading the issue first, what we are talking about here is a program bug which has been reported to adobe and unless you are an adobe programmer you can't solve the issue***
Message was edited by: PrePress1 -
Modal dialog bug in Illustrator CS3, CS4 (Mac)
Using the latest point version of Illustrator CS3 and a newly installed copy of Illustrator CS4, I have noticed a consistent bug on at least two different Macs (10.5.5). This bug pops up when you have a text item with optical kerning, and you try to manually adjust the kerning between characters. The value in the kerning field of the Character Panel has parenthesis around the numbers to show that it is a calculated value. If you change the numbers, but accidentally leave the parentheses, a modal dialog pops up saying, "Invalid numeric value." It is not possible to dismiss this dialog, and it is necessary to force quit the program.
When the text is Auto-kerned, and one makes the same mistake, the parentheses are automatically removed for you.
Using Illustrator CS3 in Windows, the "Invalid numeric value" dialog pops up under the above scenario; however, one is able to dismiss this dialog and resume working.I wasn't quite sure where to submit bug reports, which is why I posted here. However, I finally did find the bug report form on the Feedback tab of Adobe's Contact page. So I just reported this bug.
-
Bug in Illustrator on MacBook Retina with external monitor
I noticed that in Illustrator CS6 - after the Retina update
when I am working on a document on my MacBook Pro Retina - it look fine
but when I connect to external Thunderbolt display - and start moving around objects on layer
I get a bunch of white lines through my graphic where the object rectangle boundries were (in old position and when moved to new position)
this is a display only issue as it does not get exported into final imgae, and it can be cleared by refreshing the screen (drag a window on top of it for example to force a redraw)
however it makes editing very annoying as I'm workign with precision elements and they are getting sliced up with 1 pixel white lines everywhere and I have to go manually clear them every minute or two which is distracting.
Anyone else having this issue? I suppose I'll open a bug report but wanted to see if anyone else noticed it as well.Yes, you can. I have the Bluetooth wireless keyboard and mouse and a Dell widescreen display, but if you have a USB keyboard and mouse, it works essentially the same way. Just power everything up, then close the lid on the MBP to put it to sleep. Then, leaving the lid on the MBP closed, press a key or move the mouse, and your MBP will wake using the external display as the primary.
Should be no problem ;)) -
Eyedropper bug / annoyance Illustrator CC
Hi everyone,
I believe this is something which seems to have happened in the last couple of weeks.
I've recorded a video of my issue to try and show you guys what my problem is.
Basically, I have my shield on the left which is a shape with a fill and stroke. I'd like to select the wifi signal's style, by selecting the eyedropper. The wifi signal is a group made up of three shapes.
For whatever reason, my styling completely gets removed, as you can see here:
http://monosnap.com/file/hQayYPlpaj4c7zh6mBEIfCknlZ13xn#
In my eyedropper settings, I have all the boxes checked.
This is frustrating me like you wouldn't believe. Any ideas?Thank you Larry. I just submitted this bug report pasted below at the link you provided.
******BUG******
Illustrator CC 17.0.0 *always* merges layers when opening a DXF file, even if you have the "Merge Layers" unchecked.
1. Open a DXF file that contain multiple layers in Illustrator CC 17.0.0
2. Uncheck the "Merge Layers" button.
3. Click OK.
Results: It has merge all the layers into one layer.
Expected results: It should open with multiple layers preserved. Illustrator CS6 works properly. -
BUG & Frage: Illustrator CC 2014: Zeichenflächenlineale nicht als Standardeinstellung
Anders als in der offiziellen Help-Dokumentation von Adobe sind in Illustrator CC 2014 "globale Lineale" die Standardeinstellung und nicht "Zeichenflächenlineale". In Illustrator CS6 war dies genau anders herum und so ist es auch in der Hilfe beschrieben.
Wie kann ich Zeichenflächenlineale zur Standardeinstellung machen?
> In den "Voreinstellungen" habe ich nichts gefunden
> Über "Arbeitsbereich" geht's auch nicht.Danke für die Antwort, leider hilft mir das nicht weiter. Der Reihe nach:
1) Pfad: OK, Du bist auf dem Mac. Wo und wie soll ich beim Programm-Icon mit der rechten Maustaste auf "Paketinhalt" zeigen?
2) Aber natürlich weiß ich, wo sich Illustrator auf meinem PC bzw. Festplatte befindet. Also, der Pfad könnte lauten:
c:\Program Files\Adobe\Adobe Illustrator CC 2014\Support Files\Required\New Document Profiles\de_DE
Das erscheint mir als ob das der Pfad wäre, den Du meinst.
3) Bei mir ist nur de_DE installiert.
4) Das hat mit dem Problem überhaupt nichts zu tun. Es geht um die Einstellung für "In Zeichenflächenlineale ändern" bzw. "In globale Lineale" ändern. Dazu muss nur ein Dokument offen sein.
5) OK, reden wir über die Templates. In dem oben genannten Profil-Ordner befinden sich:
> Druck.ai
> EinfachesRGB.ai
> Geräte.ai
> Video und Film.ai
> Web.ai
Welches Profil wird herangezogen, wenn man im Dateimenü ganz einfach sagt: "Datei -> NEU..."?
Das was ich suchen würde, ist beispielsweise Microsoft Word die "normal.dot". Ein absolutes Basis-Profil für neue Dokumente. Keines der obig genannten Profile scheint das tatsächlich zu sein, denn jedes Profil dient ja bereits einem spezifischen Zweck.
6) Andere, gleichnamige Templates: Habe ich nachgesehen, keine gefunden. Der Programmordner ist ja auch für Illustrator CS6, für Illustrator CC und für Illustrator CC 2014 unterschiedlich. Da ich aktiv keine Basis-Profile irgendwo hin gespeichert habe, war auch nicht anzunehmen, dass hier mehrere gleichnamige Profile liegen würden. Davon abgesehen kann es in ein und demselben Windows Ordner nicht 2 Dateien mit exakt gleicher Bezeichnung und Typ geben.
Wenn ich hier weitere zweckdienliche Hinweise erhalten würde, wäre ich dankbar.
Das alles ändert nichts an der Grundproblematik, dass eine Funktion, wie sie in der Hilfe beschrieben ist nach einem Update auf eine neuere Version nicht mehr so verhält. Und das ist ein BUG. Kann man drehen und wenden wie man will und ich habe schon wieder zwei Stunden mit einem Problem verbracht, das mich eigentlich überhaupt nichts angeht. -
Help with Mavericks crashes Photoshop CC & bugs with Illustrator CC?
Have I missed an update specifically for CC users who have upgraded to Mavericks? Really wishing I had held off on the upgrade to the OS - luckily my CS4 is still compatible with the java update, however had just purchased the CC license, and wanted to use the new apps - now Photoshop CC crashes on launch (havent successfully opened one file in it without having to force quit it) and Illustrator CC bounced for a while then stopped. Randomly five minutes later the app launched. I quit it then re-opened to check for lag again, seemed fine - but then switched between that app and another, then returned to Illustrator CC and took ages for it to open. I am on a 3.4GHz intel core i7 iMac with 16GB memory 1600mhz ddr3, it shouldn't be having any lag problems, and is only a couple months old.
OK I found a file in Library/Logs/DiagnosticReports called a .hang file which is really long:
[ unecessary bits removed by admin ]
Date/Time: 2013-10-25 16:20:17 +1300
OS Version: 10.9 (Build 13A603)
Architecture: x86_64
Report Version: 18
Command: Photoshop
Path: /Applications/Adobe Photoshop CC/Adobe Photoshop CC.app/Contents/MacOS/Adobe Photoshop CC
Version: 14.1.2 (14.1.2.427)
Parent: launchd [181]
PID: 1324
Event: hang
Duration: 0.96s
Steps: 10 (100ms sampling interval)
Hardware model: iMac13,2
Active cpus: 8
Fan speed: 1194 rpm
Free pages: 1738166 pages (-1631)
Pageins: 0 pages
Pageouts: 0 pages
Swapins: 0 pages
Swapouts: 0 pages
Process: Adobe Photoshop CC [1324]
Path: /Applications/Adobe Photoshop CC/Adobe Photoshop CC.app/Contents/MacOS/Adobe Photoshop CC
Architecture: x86_64
Parent: launchd [181]
UID: 501
Task size: 78587 pages (-2)
CPU Time: 0.216s
Thread 0x11153 DispatchQueue 1 priority 46 cpu time 0.210s
10 ??? (Adobe Photoshop CC + 10804) [0x100002a34]
10 ??? (Adobe Photoshop CC + 2967993) [0x1002d49b9]
10 ??? (Adobe Photoshop CC + 2967772) [0x1002d48dc]
10 ??? (Adobe Photoshop CC + 556898) [0x100087f62]
10 ??? (Adobe Photoshop CC + 23843020) [0x1016bd0cc]
10 ??? (Adobe Photoshop CC + 23838178) [0x1016bbde2]
10 -[NSApplication run] + 646 (AppKit) [0x7fff97c09a29]
10 ??? (Adobe Photoshop CC + 23836436) [0x1016bb714]
10 ??? (Adobe Photoshop CC + 554787) [0x100087723]
10 ??? (Adobe Photoshop CC + 555164) [0x10008789c]
10 ??? (Adobe Photoshop CC + 582218) [0x10008e24a]
10 ??? (Adobe Photoshop CC + 528382) [0x100080ffe]
10 ??? (Adobe Photoshop CC + 531567) [0x100081c6f]
10 ??? (Adobe Photoshop CC + 651011) [0x10009ef03]
10 ??? (Adobe Photoshop CC + 16970549) [0x10102f335]
10 ??? (Adobe Photoshop CC + 653865) [0x10009fa29]
10 ??? (Adobe Photoshop CC + 6331860) [0x100609dd4]
10 ??? (Adobe Photoshop CC + 6757398) [0x100671c16]
10 ??? (Adobe Photoshop CC + 9980396) [0x1009849ec]
10 ??? (Adobe Photoshop CC + 9983358) [0x10098557e]
10 ??? (Adobe Photoshop CC + 9983806) [0x10098573e]
10 ??? (Adobe Photoshop CC + 6705418) [0x10066510a]
10 ??? (Adobe Photoshop CC + 6694335) [0x1006625bf]
10 ??? (Adobe Photoshop CC + 6688868) [0x100661064]
10 ??? (Adobe Photoshop CC + 6679135) [0x10065ea5f]
10 ??? (Adobe Photoshop CC + 6668898) [0x10065c262]
10 ??? (Adobe Photoshop CC + 11952401) [0x100b66111]
10 ??? (Adobe Photoshop CC + 13033929) [0x100c6e1c9]
10 ??? (Adobe Photoshop CC + 12891317) [0x100c4b4b5]
10 ??? (Adobe Photoshop CC + 12946238) [0x100c58b3e]
10 ??? (Adobe Photoshop CC + 12826595) [0x100c3b7e3]
10 ??? (Adobe Photoshop CC + 12828601) [0x100c3bfb9]
10 ??? (Adobe Photoshop CC + 12160436) [0x100b98db4]
10 ??? (Adobe Photoshop CC + 12160764) [0x100b98efc]
10 ??? (Adobe Photoshop CC + 12166326) [0x100b9a4b6]
10 ??? (Adobe Photoshop CC + 12255652) [0x100bb01a4]
10 ??? (AdobeCoolType + 353207) [0x104fb93b7]
10 CTCleanup + 724119 (AdobeCoolType) [0x105072605]
10 CTCleanup + 388882 (AdobeCoolType) [0x105020880]
10 CTCleanup + 389039 (AdobeCoolType) [0x10502091d]
6 CTCleanup + 724408 (AdobeCoolType) [0x105072726]
6 ??? (AdobeCoolType + 73737) [0x104f75009]
6 CTCleanup + 325486 (AdobeCoolType) [0x1050110dc]
6 CTCleanup + 324222 (AdobeCoolType) [0x105010bec]
5 CTCleanup + 1026803 (AdobeCoolType) [0x1050bc461]
5 CTCleanup + 1025680 (AdobeCoolType) [0x1050bbffe]
5 CTCleanup + 1005119 (AdobeCoolType) [0x1050b6fad]
5 CTCleanup + 1005217 (AdobeCoolType) [0x1050b700f]
5 CTFontManagerCreateFontDescriptorsFromURL + 54 (CoreText) [0x7fff917dc7ee]
5 CreateFontsWithURL(__CFURL const*, bool) + 22 (CoreText) [0x7fff917dd1bc]
5 CGFontCreateFontsWithURL + 383 (CoreGraphics) [0x7fff930e117e]
5 CGFontCreateFontsWithPath + 40 (CoreGraphics) [0x7fff930e1569]
5 create_private_data_with_path + 19 (libCGXType.A.dylib) [0x7fff8f0991f4]
5 FPFontCreateFontsWithPath + 253 (libFontParser.dylib) [0x7fff9159fe1f]
2 TFont::CreateFontEntitiesForFile(char const*, bool, TSimpleArray<TFont*>&, bool, short, char const*) + 1225 (libFontParser.dylib) [0x7fff915a07cd]
2 TResourceForkSurrogate::TResourceForkSurrogate(char const*, bool) + 116 (libFontParser.dylib) [0x7fff915a68ae]
2 TResourceForkFileReference::TResourceForkFileReference(char const*, bool) + 29 (libFontParser.dylib) [0x7fff915a6955]
2 TFileDataReference::TFileDataReference(char const*, bool) + 319 (libFontParser.dylib) [0x7fff915a6bb3]
2 __open + 10 (libsystem_kernel.dylib) [0x7fff8f3855da]
*2 hndl_unix_scall64 + 22 (mach_kernel) [0xffffff80002f3e06]
*2 unix_syscall64 + 499 (mach_kernel) [0xffffff800063de23]
*2 open + 274 (mach_kernel) [0xffffff80003e67d2]
*2 open1 + 309 (mach_kernel) [0xffffff80003e5f15]
*2 vn_open_auth + 1648 (mach_kernel) [0xffffff80003f4360]
*2 vn_authorize_open_existing + 445 (mach_kernel) [0xffffff80003df80d]
*2 kauth_authorize_action + 193 (mach_kernel) [0xffffff80005b3671]
*2 KLKauthVnodeInterceptorCommand::KLKauthVnodeInterceptorCommand() + 278 (klif) [0xffffff7f810bdc66]
*2 KLInterceptor010::getMetaClass() const + 148 (klif) [0xffffff7f810bc234]
*2 KLFileMonitor::getMetaClass() const + 2540 (klif) [0xffffff7f810c322c]
*2 KLFileMonitor::getMetaClass() const + 577 (klif) [0xffffff7f810c2a81]
*2 lck_mtx_sleep_deadline + 87 (mach_kernel) [0xffffff800022d217]
*2 thread_block_reason + 204 (mach_kernel) [0xffffff8000235d4c]
*2 ??? (mach_kernel + 223563) [0xffffff800023694b]
*2 machine_switch_context + 354 (mach_kernel) [0xffffff80002d81d2]
2 TFont::CreateFontEntitiesForFile(char const*, bool, TSimpleArray<TFont*>&, bool, short, char const*) + 1306 (libFontParser.dylib) [0x7fff915a081e]
2 TLWFNType1Font::TLWFNType1Font(TResourceForkSurrogate const&, TResourceFileDataSurrogate const&, TResourceFileDataSurrogate const&) + 452 (libFontParser.dylib) [0x7fff915b3c86]
2 TType1ParsingContext::ParseType1Font() + 14 (libFontParser.dylib) [0x7fff915b4610]
2 TParsingContext::ParseType1Font() + 486 (libFontParser.dylib) [0x7fff915b48b4]
2 TParsingContext::DoParse(TParserDictionary const*) + 857 (libFontParser.dylib) [0x7fff915b54db]
2 TParsingContext::DoCharStrings() + 378 (libFontParser.dylib) [0x7fff915ba550]
1 TType1LWFNParsingContext::CharString(unsigned int, unsigned int, unsigned int, char const*, char const*, unsigned int) + 112 (libFontParser.dylib) [0x7fff915ba984]
1 TParsingContext::DoFontInfoString(char const*, int&) + 227 (libFontParser.dylib) [0x7fff915b1313]
1 <executing in user space>
1 TType1LWFNParsingContext::CharString(unsigned int, unsigned int, unsigned int, char const*, char const*, unsigned int) + 44 (libFontParser.dylib) [0x7fff915ba940]
1 TParsingContext::CharString(unsigned int, unsigned int, unsigned int, char const*, char const*, unsigned int) + 187 (libFontParser.dylib) [0x7fff915c44b7]
1 TType1LWFNParsingContext::CharStringIndex(int, int, short, char const*) + 180 (libFontParser.dylib) [0x7fff915dac6a]
1 _platform_memmove$VARIANT$Nehalem + 299 (libsystem_platform.dylib) [0x7fff95ef810b]
1 <executing in user space>
1 TFont::CreateFontEntitiesForFile(char const*, bool, TSimpleArray<TFont*>&, bool, short, char const*) + 518 (libFontParser.dylib) [0x7fff915a050a]
1 TResourceForkSurrogate::TResourceForkSurrogate(char const*, bool) + 116 (libFontParser.dylib) [0x7fff915a68ae]
1 TResourceForkFileReference::TResourceForkFileReference(char const*, bool) + 29 (libFontParser.dylib) [0x7fff915a6955]
1 TFileDataReference::TFileDataReference(char const*, bool) + 319 (libFontParser.dylib) [0x7fff915a6bb3]
1 __open + 10 (libsystem_kernel.dylib) [0x7fff8f3855da]
*1 hndl_unix_scall64 + 22 (mach_kernel) [0xffffff80002f3e06]
*1 unix_syscall64 + 499 (mach_kernel) [0xffffff800063de23]
*1 open + 274 (mach_kernel) [0xffffff80003e67d2]
*1 open1 + 309 (mach_kernel) [0xffffff80003e5f15]
*1 vn_open_auth + 1648 (mach_kernel) [0xffffff80003f4360]
*1 vn_authorize_open_existing + 445 (mach_kernel) [0xffffff80003df80d]
*1 kauth_authorize_action + 193 (mach_kernel) [0xffffff80005b3671]
*1 KLKauthVnodeInterceptorCommand::KLKauthVnodeInterceptorCommand() + 278 (klif) [0xffffff7f810bdc66]
*1 KLInterceptor010::getMetaClass() const + 148 (klif) [0xffffff7f810bc234]
*1 KLFileMonitor::getMetaClass() const + 2540 (klif) [0xffffff7f810c322c]
*1 KLFileMonitor::getMetaClass() const + 577 (klif) [0xffffff7f810c2a81]
*1 lck_mtx_sleep_deadline + 87 (mach_kernel) [0xffffff800022d217]
*1 thread_block_reason + 204 (mach_kernel) [0xffffff8000235d4c]
*1 ??? (mach_kernel + 223563) [0xffffff800023694b]
*1 machine_switch_context + 354 (mach_kernel) [0xffffff80002d81d2]
1 CTCleanup + 1026901 (AdobeCoolType) [0x1050bc4c3]
1 CTCleanup + 1014804 (AdobeCoolType) [0x1050b9582]
1 CTCleanup + 552748 (AdobeCoolType) [0x10504889a]
1 CTCleanup + 203 (AdobeCoolType) [0x104fc1a39]
1 __open + 10 (libsystem_kernel.dylib) [0x7fff8f3855da]
*1 hndl_unix_scall64 + 22 (mach_kernel) [0xffffff80002f3e06]
*1 unix_syscall64 + 499 (mach_kernel) [0xffffff800063de23]
*1 open + 274 (mach_kernel) [0xffffff80003e67d2]
*1 open1 + 309 (mach_kernel) [0xffffff80003e5f15]
*1 vn_open_auth + 1648 (mach_kernel) [0xffffff80003f4360]
*1 vn_authorize_open_existing + 445 (mach_kernel) [0xffffff80003df80d]
*1 kauth_authorize_action + 193 (mach_kernel) [0xffffff80005b3671]
*1 KLKauthVnodeInterceptorCommand::KLKauthVnodeInterceptorCommand() + 278 (klif) [0xffffff7f810bdc66]
*1 KLInterceptor010::getMetaClass() const + 148 (klif) [0xffffff7f810bc234]
*1 KLFileMonitor::getMetaClass() const + 2540 (klif) [0xffffff7f810c322c]
*1 KLFileMonitor::getMetaClass() const + 577 (klif) [0xffffff7f810c2a81]
*1 lck_mtx_sleep_deadline + 87 (mach_kernel) [0xffffff800022d217]
*1 thread_block_reason + 204 (mach_kernel) [0xffffff8000235d4c]
*1 ??? (mach_kernel + 223563) [0xffffff800023694b]
*1 machine_switch_context + 354 (mach_kernel) [0xffffff80002d81d2]
4 CTCleanup + 724448 (AdobeCoolType) [0x10507274e]
4 CTCleanup + 848573 (AdobeCoolType) [0x105090c2b]
4 CTCleanup + 833672 (AdobeCoolType) [0x10508d1f6]
4 ??? (AdobeCoolType + 40488) [0x104f6ce28]
4 ??? (AdobeCoolType + 30415) [0x104f6a6cf]
4 CTCleanup + 1024055 (AdobeCoolType) [0x1050bb9a5]
4 CTCleanup + 1018593 (AdobeCoolType) [0x1050ba44f]
4 CTCleanup + 1005217 (AdobeCoolType) [0x1050b700f]
4 CTFontManagerCreateFontDescriptorsFromURL + 54 (CoreText) [0x7fff917dc7ee]
4 CreateFontsWithURL(__CFURL const*, bool) + 22 (CoreText) [0x7fff917dd1bc]
4 CGFontCreateFontsWithURL + 383 (CoreGraphics) [0x7fff930e117e]
4 CGFontCreateFontsWithPath + 40 (CoreGraphics) [0x7fff930e1569]
4 create_private_data_with_path + 19 (libCGXType.A.dylib) [0x7fff8f0991f4]
4 FPFontCreateFontsWithPath + 253 (libFontParser.dylib) [0x7fff9159fe1f]
2 TFont::CreateFontEntitiesForFile(char const*, bool, TSimpleArray<TFont*>&, bool, short, char const*) + 1225 (libFontParser.dylib) [0x7fff915a07cd]
2 TResourceForkSurrogate::TResourceForkSurrogate(char const*, bool) + 116 (libFontParser.dylib) [0x7fff915a68ae]
2 TResourceForkFileReference::TResourceForkFileReference(char const*, bool) + 29 (libFontParser.dylib) [0x7fff915a6955]
2 TFileDataReference::TFileDataReference(char const*, bool) + 319 (libFontParser.dylib) [0x7fff915a6bb3]
2 __open + 10 (libsystem_kernel.dylib) [0x7fff8f3855da]
*2 hndl_unix_scall64 + 22 (mach_kernel) [0xffffff80002f3e06]
*2 unix_syscall64 + 499 (mach_kernel) [0xffffff800063de23]
*2 open + 274 (mach_kernel) [0xffffff80003e67d2]
*2 open1 + 309 (mach_kernel) [0xffffff80003e5f15]
*2 vn_open_auth + 1648 (mach_kernel) [0xffffff80003f4360]
*2 vn_authorize_open_existing + 445 (mach_kernel) [0xffffff80003df80d]
*2 kauth_authorize_action + 193 (mach_kernel) [0xffffff80005b3671]
*2 KLKauthVnodeInterceptorCommand::KLKauthVnodeInterceptorCommand() + 278 (klif) [0xffffff7f810bdc66]
*2 KLInterceptor010::getMetaClass() const + 148 (klif) [0xffffff7f810bc234]
*2 KLFileMonitor::getMetaClass() const + 2540 (klif) [0xffffff7f810c322c]
*2 KLFileMonitor::getMetaClass() const + 577 (klif) [0xffffff7f810c2a81]
*2 lck_mtx_sleep_deadline + 87 (mach_kernel) [0xffffff800022d217]
*2 thread_block_reason + 204 (mach_kernel) [0xffffff8000235d4c]
*2 ??? (mach_kernel + 223563) [0xffffff800023694b]
*2 machine_switch_context + 354 (mach_kernel) [0xffffff80002d81d2]
1 TFont::CreateFontEntitiesForFile(char const*, bool, TSimpleArray<TFont*>&, bool, short, char const*) + 518 (libFontParser.dylib) [0x7fff915a050a]
1 TResourceForkSurrogate::TResourceForkSurrogate(char const*, bool) + 116 (libFontParser.dylib) [0x7fff915a68ae]
1 TResourceForkFileReference::TResourceForkFileReference(char const*, bool) + 29 (libFontParser.dylib) [0x7fff915a6955]
1 TFileDataReference::TFileDataReference(char const*, bool) + 319 (libFontParser.dylib) [0x7fff915a6bb3]
1 __open + 10 (libsystem_kernel.dylib) [0x7fff8f3855da]
*1 hndl_unix_scall64 + 22 (mach_kernel) [0xffffff80002f3e06]
*1 unix_syscall64 + 499 (mach_kernel) [0xffffff800063de23]
*1 open + 274 (mach_kernel) [0xffffff80003e67d2]
*1 open1 + 309 (mach_kernel) [0xffffff80003e5f15]
*1 vn_open_auth + 1648 (mach_kernel) [0xffffff80003f4360]
*1 vn_authorize_open_existing + 445 (mach_kernel) [0xffffff80003df80d]
*1 kauth_authorize_action + 193 (mach_kernel) [0xffffff80005b3671]
*1 KLKauthVnodeInterceptorCommand::KLKauthVnodeInterceptorCommand() + 278 (klif) [0xffffff7f810bdc66]
*1 KLInterceptor010::getMetaClass() const + 148 (klif) [0xffffff7f810bc234]
*1 KLFileMonitor::getMetaClass() const + 2540 (klif) [0xffffff7f810c322c]
*1 KLFileMonitor::getMetaClass() const + 577 (klif) [0xffffff7f810c2a81]
*1 lck_mtx_sleep_deadline + 87 (mach_kernel) [0xffffff800022d217]
*1 thread_block_reason + 204 (mach_kernel) [0xffffff8000235d4c]
*1 ??? (mach_kernel + 223563) [0xffffff800023694b]
*1 machine_switch_context + 354 (mach_kernel) [0xffffff80002d81d2]
1 TFont::CreateFontEntitiesForFile(char const*, bool, TSimpleArray<TFont*>&, bool, short, char const*) + 1306 (libFontParser.dylib) [0x7fff915a081e]
1 TLWFNType1Font::TLWFNType1Font(TResourceForkSurrogate const&, TResourceFileDataSurrogate const&, TResourceFileDataSurrogate const&) + 452 (libFontParser.dylib) [0x7fff915b3c86]
1 TType1ParsingContext::ParseType1Font() + 14 (libFontParser.dylib) [0x7fff915b4610]
1 TParsingContext::ParseType1Font() + 486 (libFontParser.dylib) [0x7fff915b48b4]
1 TParsingContext::DoParse(TParserDictionary const*) + 857 (libFontParser.dylib) [0x7fff915b54db]
1 TParsingContext::DoCharStrings() + 334 (libFontParser.dylib) [0x7fff915ba524]
1 TParsingContext::GetBinaryString(unsigned int&, unsigned int&, unsigned int&) + 37 (libFontParser.dylib) [0x7fff915b9e97]
1 TParsingContext::InterpretInteger(char*) + 82 (libFontParser.dylib) [0x7fff915b870c]
1 strtol_l + 100 (libsystem_c.dylib) [0x7fff96e103bd]
1 <executing in user space>
Thread 0x11161 DispatchQueue 2 priority 48
10 _dispatch_mgr_thread + 52 (libdispatch.dylib) [0x7fff98dde152]
10 kevent64 + 10 (libsystem_kernel.dylib) [0x7fff8f386662]
*10 ??? (mach_kernel + 3948480) [0xffffff80005c3fc0]
Thread 0x11160 priority 46
10 start_wqthread + 13 (libsystem_pthread.dylib) [0x7fff989e1fb9]
10 __workq_kernreturn + 10 (libsystem_kernel.dylib) [0x7fff8f385e6a]
*10 wq_unpark_continue + 0 (pthread) [0xffffff7f80be66ae]
Thread 0x11332 priority 46
10 thread_start + 13 (libsystem_pthread.dylib) [0x7fff989e1fc9]
10 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff989dd72a]
10 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff989dd899]
10 ??? (MultiProcessor Support + 417508) [0x113981ee4]
10 ??? (MultiProcessor Support + 286291) [0x113961e53]
10 ??? (MultiProcessor Support + 286619) [0x113961f9b]
10 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f385716]
*10 psynch_cvcontinue + 0 (pthread) [0xffffff7f80be8940]
Thread 0x11333 priority 46
10 thread_start + 13 (libsystem_pthread.dylib) [0x7fff989e1fc9]
10 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff989dd72a]
10 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff989dd899]
10 ??? (MultiProcessor Support + 417508) [0x113981ee4]
10 ??? (MultiProcessor Support + 286291) [0x113961e53]
10 ??? (MultiProcessor Support + 286619) [0x113961f9b]
10 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f385716]
*10 psynch_cvcontinue + 0 (pthread) [0xffffff7f80be8940]
Thread 0x11334 priority 46
10 thread_start + 13 (libsystem_pthread.dylib) [0x7fff989e1fc9]
10 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff989dd72a]
10 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff989dd899]
10 ??? (MultiProcessor Support + 417508) [0x113981ee4]
10 ??? (MultiProcessor Support + 286291) [0x113961e53]
10 ??? (MultiProcessor Support + 286619) [0x113961f9b]
10 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f385716]
*10 psynch_cvcontinue + 0 (pthread) [0xffffff7f80be8940]
Thread 0x11335 priority 46
10 thread_start + 13 (libsystem_pthread.dylib) [0x7fff989e1fc9]
10 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff989dd72a]
10 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff989dd899]
10 ??? (MultiProcessor Support + 417508) [0x113981ee4]
10 ??? (MultiProcessor Support + 286291) [0x113961e53]
10 ??? (MultiProcessor Support + 286619) [0x113961f9b]
10 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f385716]
*10 psynch_cvcontinue + 0 (pthread) [0xffffff7f80be8940]
Thread 0x11336 priority 46
10 thread_start + 13 (libsystem_pthread.dylib) [0x7fff989e1fc9]
10 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff989dd72a]
10 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff989dd899]
10 ??? (MultiProcessor Support + 417508) [0x113981ee4]
10 ??? (MultiProcessor Support + 286291) [0x113961e53]
10 ??? (MultiProcessor Support + 286619) [0x113961f9b]
10 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f385716]
*10 psynch_cvcontinue + 0 (pthread) [0xffffff7f80be8940]
Thread 0x11337 priority 46
10 thread_start + 13 (libsystem_pthread.dylib) [0x7fff989e1fc9]
10 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff989dd72a]
10 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff989dd899]
10 ??? (MultiProcessor Support + 417508) [0x113981ee4]
10 ??? (MultiProcessor Support + 286291) [0x113961e53]
10 ??? (MultiProcessor Support + 286619) [0x113961f9b]
10 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f385716]
*10 psynch_cvcontinue + 0 (pthread) [0xffffff7f80be8940]
Thread 0x11338 priority 46
10 thread_start + 13 (libsystem_pthread.dylib) [0x7fff989e1fc9]
10 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff989dd72a]
10 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff989dd899]
10 ??? (MultiProcessor Support + 417508) [0x113981ee4]
10 ??? (MultiProcessor Support + 286291) [0x113961e53]
10 ??? (MultiProcessor Support + 286619) [0x113961f9b]
10 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f385716]
*10 psynch_cvcontinue + 0 (pthread) [0xffffff7f80be8940]
Thread 0x11342 priority 46
10 thread_start + 13 (libsystem_pthread.dylib) [0x7fff989e1fc9]
10 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff989dd72a]
10 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff989dd899]
10 ??? (ScriptingSupport + 1319093) [0x1170b40b5]
10 ??? (ScriptingSupport + 1212366) [0x117099fce]
10 ??? (ScriptingSupport + 1320216) [0x1170b4518]
10 __semwait_signal + 10 (libsystem_kernel.dylib) [0x7fff8f385a3a]
*10 semaphore_wait_continue + 0 (mach_kernel) [0xffffff800023b550]
Thread 0x11358 priority 46
10 thread_start + 13 (libsystem_pthread.dylib) [0x7fff989e1fc9]
10 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff989dd72a]
10 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff989dd899]
10 ??? (Adobe Photoshop CC + 24013556) [0x1016e6af4]
10 ??? (Adobe Photoshop CC + 26858074) [0x10199d25a]
10 ??? (Adobe Photoshop CC + 26851948) [0x10199ba6c]
10 ??? (Adobe Photoshop CC + 26855800) [0x10199c978]
10 ??? (Adobe Photoshop CC + 2771725) [0x1002a4b0d]
10 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f385716]
*10 psynch_cvcontinue + 0 (pthread) [0xffffff7f80be8940]
Thread 0x1135a priority 46
10 thread_start + 13 (libsystem_pthread.dylib) [0x7fff989e1fc9]
10 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff989dd72a]
10 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff989dd899]
10 ??? (libclh.dylib + 6360105) [0x7fff96c1bc29]
10 ??? (libclh.dyli -
Bug with Illustrator Line Tool
Hi
I am trying to draw a shape using the illustrator line tool, and it always seems to revert to 1pt when I am using it within a shape, even when I manually change it to 0.5pt in the top bar, it does not change. I will go larger than 1pt but not smaller for some reason. It works when the line is by itself. As in not attached to a shape but as soon as you move it to connect with the rest of the shape it reverts to that large size. please help
Thanks
RebeccaOh thanks! I didn't realise this could effect specific tools as well as the placement of objects, Im having another problem which I thought would be solved by turning off the 'Align to Pixel Grid' but it didn't work
Maybe you are looking for
-
My computor had been overly slow which was not normal when looking at processes running in task manager I found plugin-container.exe to be using alot of memory. I looked online and found that this was an update of firefox which was not essential, I t
-
I am in the UK. Can I use the iPad Mini when on holiday in Sri Lanka?
I am in the UK. Can I use the iPad Mini when on holiday in Sri Lanka?
-
I was wondering i havent bought a mac yet and i am a college student. i am looking to buy just the hardrive will it be able to hook up to a Dell monitor and key board
-
How to embed more than 393 chars in form fields
how to embed more than 1000 character in the field. I have written a xsl template which is about 2 pages in length. How do I embed it in the word template fields.
-
Hi Everyone! I would like to know, how can I hide the context menu ( righ clck menu ) in 3D pdf? Is it possible? Thank You for some help!