Spinning rainbow when placing images

Within the past two weeks, something has happened to cause my computer to not want to place images in ANY program. When I try to place an image in Illustrator CS2, I get a spinning rainbow which lasts for about 3-5 minutes before placing the file. (not very helpful when I have to place 20 images on a page!) Same thing with Photoshop and Mail. It is also slow when opening a text file into AICS2.
I've trashed about every preference file I can find. I've trashed launch services cache files. I've repaired permissions. I don't know what else to try!
Any ideas? Could this be a hardware problem?

Tracey:
Take a look at Dr. Smoke's FAQ on The Spinning Beach Ball of Death.
Good luck.
cornelius

Similar Messages

Difference between CS3 and CS4 when placing images, percentage not kept

There is some kind of difference between CS3 and CS4 when placing images. The images I've dealt with right now were vector images but it might apply to all kinds of images.
When replacing an existing image, the CS4 behaviour is to let the image fill up the frame. In CS3 the percentage was set to 100% as default (the % you see when selecting the image, not the container).
Also when replacing an impage in CS4, the "inner" image frame is kept, while in C3, the percentage was kept.
Is there some kind of placement preferences / settings to let CS4 act the same wat as CS3 did, when placing an image?
-- Andreas

Yes, the behavior was changed in CS4 (and many users, like me, prefer the new system).
If you click and drag a loaded image place cursor the entire image will be be scaled to fit the proportionally drawn frame -- a huge timesaver if you mostly place uncropped art. If you want 100% of the image at 100% scale, just click and release -- same as before, or as before you can pre-draw a frame and place into it and your image will come in cropped at 100% (unless you've changed the fitting options for the frame before placing).
Peter

Illustrator cs6 locks up when placing image (yosemite)

Just upgraded to yosemite...was running fine for a week or so but now illustrator finder window freezes when placing an image. Thoughts?

spooky,
You may try the list.
The following is a general list of things you may try when the issue is not in a specific file, and when it is not caused by issues with opening a file from external media, see below. You may have tried/done some of them already; 1) and 2) are the easy ones for temporary strangenesses, and 3) and 4) are specifically aimed at possibly corrupt preferences); 5) is a list in itself, and 6) is the last resort.
If possible/applicable, you should save current artwork first, of course.
1) Close down Illy and open again;
2) Restart the computer (you may do that up to at least 5 times);
3) Close down Illy and press Ctrl+Alt+Shift/Cmd+Option+Shift during startup (easy but irreversible);
4) Move the folder (follow the link with that name) with Illy closed (more tedious but also more thorough and reversible), for CS3 - CC you may find the folder here:
https://helpx.adobe.com/illustrator/kb/preference-file-location-illustrator.html
5) Look through and try out the relevant among the Other options (follow the link with that name, Item 7) is a list of usual suspects among other applications that may disturb and confuse Illy, Item 15) applies to CC, CS6, and maybe CS5);
Even more seriously, you may:
6) Uninstall (ticking the box to delete the preferences), run the Cleaner Tool (if you have CS3/CS4/CS5/CS6/CC), and reinstall.
http://www.adobe.com/support/contact/cscleanertool.html

Black image boundry lines when placing image in Illustrator

I am making a business card in Illustrator 6.
I placed an image of my black signature with transparent background on the white background business card, and now it is leaving a box were that signature image canvas ends. This happens with both a .psd and .pnd files.
Now if I could just go into photoshop and extend the canvas and leave the image the same size that would be great. When I try to do this though there is still the old canvas boundry line.
If I was able to start all over I would have had the original canvas size way wider than the image of my signature that I drew on it. That way it's boundries would now be outside of my business cards boundries and I would not be seeing those black boundry lines.
There must be a simple way of fixing this?

I tried that, but where the instructions say "File > Print, and under Output, choose Composite CMYK" I don't have that option. Otherwise I did the rest and it did not help.
I forgot to say that it only prints what is inside my signatures boundries/canvas dimensions and will not even print to the edge of the Illustrator file.
I would attach the image, but it is too large of a file and whatever other formats I try to save it at it will only save it to the boundries of my signature and not the Illustrator image, artboard or whatever you call it.

Dimensions changes when placing image in Illustrator

I had a problem while placing an image created in photoshop into illustrator, dimensions of the image was changed in Illustrator (shorter in hight and longer in width). My image size in Photoshop is 30.6 cm x 6 cm, Resolution: 300 pixels/inch, it changed in illustrator to 30.4969 cm x 6.0029 cm.
After few tests, I found out that if I change image resolution from pixels/inch to pixels/cm, resolution hence will convert from 300ppi to 118.11. Here I just rounded resolution to 120ppc, only then this image will keep its dimensions in illustrator as 30.6 cm x 6 cm without any change when I drag it or place it in Ai again!
Apparently keeping resolution as rounded figures in pixels/cm will fix this issue… any one had this problem or had solved it in a different way?

I think this is down to specifiying metric dimensions in an imperial resolution, coupled with the fact that there's no such thing as a fraction of a pixel.
300dpi equals 118.1102362 pixels per cm. Therefore, 6cm equals 708.6614173 pixels. Because you can only have whole pixels, Photoshop rounds this up to 709 pixels. 709 divided by 118.1102362 equals 6.002866668 which accounts for the discrepancy that you're seeing.
As you've discovered, the only way around this is to use a metric resolution that your chosen dimension fits in exact pixels.

Help ... Image gap when placing images

When ever placeing an image in dreamweaver cs6 i am getting this white space.... http://paulwilson209.com/testerhats/index4.html.... this also happens win usig divs. what am i missing?

Glad to help. I don't post here much, but I do tend to give correct answers most of the time. Unfortunately, they are often overlooked in the noise . The issue is that the W3C specification always treated images as inline-replaced elements (just like text) and so browsers leave room, as Murray pointed out, for descending character parts (like the a lowercase "y") even though an image does not have those parts. It's one of many illogical decisions made by the folks who devised the specification. In older versions of HTML/xhtml this issue was only an issue when a strict DOCTYPE was used. You could get the same result in CS4 by simply converting your page to a strict DOCTYPE. The HTML5 DOCTYPE, which is often default in CS6, is always "strict" and so that's why you see this anomaly now. Relative to your e-mail, there really is no way to learn all this in one, or even a dozen, places. It's something you accumulate over time as you design Web pages. You see a problem like this and you Google for information, or you post on a forum and, hopefully, you come with a solution. If you do, you store it in your brain and, if you're like me, in a big spiral notebook .

? Mark when placing images

Any ideas why i am getting a question mark when i am trying to place certain images into a keynote document - i have placed about 50 images so far - all jpegs and low res -about 2mb - but when i get to certain images i get a cross and a question mark in the placeholder box - as if it can't find the image - but it is in the same location as the others and i can open it in photoshop etc so i know it's not a fault with the images itself
have tried deleting the page and creating a new one - still no luck
any ideas
many thanks

I'm having the same problem. I'm building a photo presentation of a medical trip... lots of pics... everything was going fine until on slide 53 I added a "smart build" with 14 photos in it and started working on the transitions in the smart build. Keynote began acting funny, so I saved and exited the program. Restarted the computer and reopened KN. Now the pics show up in thumbnail view but are missing in the actual slide. The closer Mac gets to the "PC" the more buggy our apps have become!!!!!
Hope someone can find a solution to this issue soon. I'm not fond of going through the process of rebuilding this entire presentation... in light of the fact that I've no idea of what is causing the problem.

Working in CS 5.5, ID continuously crashes when placing images of any kind, Adobe says its an apple error. What do I do?

Using an imac with 8gb ram, intel core, OS 10.9.5. I currently have CS 5.5. When working in InDesign, it continuously crashes whenever I place an image on the page. I've tried all types of images and sizes, but it still crashes. Talked to an adobe tech, they said it was an apple issue. I sent them the crash report and followed all of there instructions, but still crashes. Any suggestions on what to do next? Is there a patch that I'm missing?

I found 2 reports from InDesign: Just a note, my entire computer doesn't shut down, just InDesign.
Date/Time:
2014-10-22 10:44:52 -0400
OS Version:
10.9.5 (Build 13F34)
Architecture:
x86_64
Report Version: 18
Command:
InDesign
Path:
/Applications/Adobe InDesign CS5.5/Adobe InDesign CS5.5.app/Contents/MacOS/Adobe InDesign CS5.5
Version:
7.5.3.333 (7530)
Parent:
launchd [193]
PID:
746
Event:
wakeups (microstackshots only)
Wakeups:
168 wakeups per second for 268 seconds
Duration:
268.00s
Steps:
264
Hardware model: iMac14,2
Active cpus:
4
Fan speed:
1199 rpm
Powerstats for: Adobe InDesign C [746]
Start time:
2014-10-22 10:44:53 -0400
End time:
2014-10-22 10:49:20 -0400
Parent:
launchd
Microstackshots: 143 samples (54%)
Primary state:   79 samples Frontmost App, Non-Background Priority, User mode
User Activity:   0 samples Idle, 143 samples Active
Power Source:
0 samples on Battery, 143 samples on AC
104 start + 54 (Adobe InDesign CS5.5) [0x27c6]
104 main + 187 (Adobe InDesign CS5.5) [0x28ab]
103 GetPlugIn + 14282 (AppFramework) [0xce8d2ea]
66 ??? (AppFramework + 10798) [0xce67a2e]
66 ReceiveNextEvent + 72 (HIToolbox) [0x9aede99a]
66 ReceiveNextEventInMode + 75 (HIToolbox) [0x9aede936]
63 ReceiveNextEventCommon + 526 (HIToolbox) [0x9ad438e2]
63 RunCurrentEventLoopInMode + 259 (HIToolbox) [0x9ad43b5d]
63 CFRunLoopRunInMode + 123 (CoreFoundation) [0x983ab84b]
60 CFRunLoopRunSpecific + 394 (CoreFoundation) [0x983ab9ea]
38 __CFRunLoopRun + 1779 (CoreFoundation) [0x983ac353]
35 __CFRunLoopDoTimers + 349 (CoreFoundation) [0x9846f06d]
10 __CFRunLoopDoTimer + 1395 (CoreFoundation) [0x983f4863]
9   __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 22 (CoreFoundation) [0x983f4ea6]
5   processNotifications(__CFRunLoopTimer*, void*) + 61 (ExtensisFontManagementIDCS5.5) [0xc157c47]
4   PanelManager::SelectSocket(bool) + 82 (ExtensisFontManagementIDCS5.5) [0xc1146ac]
4   __select + 10 (libsystem_kernel.dylib) [0x91dfbace]
3   <Non-Frontmost App, Kernel mode>
1   <Kernel mode>
1   PanelManager::SelectSocket(bool) + 548 (ExtensisFontManagementIDCS5.5) [0xc11487e]
1   std::_Rb_tree_increment(std::_Rb_tree_node_base*) + 42 (libstdc++.6.dylib) [0x9222e6d3]
1   <Non-Frontmost App>
2   processNotifications(__CFRunLoopTimer*, void*) + 74 (ExtensisFontManagementIDCS5.5) [0xc157c54]
1   PanelManager::PopNotifications() + 68 (ExtensisFontManagementIDCS5.5) [0xc114176]
1   SuitcasePanel::PopNotifications() + 55 (ExtensisFontManagementIDCS5.5) [0xc1c23b5]
1   std::set<unsigned long, std::less<unsigned long>, std::allocator<unsigned long> >::begin() const + 17 (ExtensisFontManagementIDCS5.5) [0xc1a3bb1]
1   <Non-Frontmost App>
1   PanelManager::PopNotifications() + 71 (ExtensisFontManagementIDCS5.5) [0xc114179]
1   processNotifications(__CFRunLoopTimer*, void*) + 11 (ExtensisFontManagementIDCS5.5) [0xc157c15]
1   FontManagerInterface::GetFontManager() + 22 (ExtensisFontManagementIDCS5.5) [0xc11af30]
1   processNotifications(__CFRunLoopTimer*, void*) + 40 (ExtensisFontManagementIDCS5.5) [0xc157c32]
1   CoreAgentInterface::ProcessNotifications() + 50 (ExtensisFontManagementIDCS5.5) [0xc16fd14]
1   fork + 68 (libsystem_c.dylib) [0x916fc9aa]
1   SuitcaseIdleTask::TaskName() + 20 (ExtensisFontManagementIDCS5.5) [0xc157c0a]
1   <Non-Frontmost App>
8   __CFRunLoopDoTimer + 2763 (CoreFoundation) [0x983f4dbb]
5   __CFRepositionTimerInMode + 126 (CoreFoundation) [0x983b3dee]
3   mk_timer_arm + 10 (libsystem_kernel.dylib) [0x91df70ca]
2   <Non-Frontmost App, Kernel mode>
1   <Kernel mode>
1   __CFArmNextTimerInMode + 117 (CoreFoundation) [0x983b3fc5]
1   CFArrayGetValueAtIndex + 144 (CoreFoundation) [0x98363c50]
1   __CFArmNextTimerInMode + 545 (CoreFoundation) [0x983b4171]
1   __CFRepositionTimerInMode + 118 (CoreFoundation) [0x983b3de6]
1   CFArrayInsertValueAtIndex + 124 (CoreFoundation) [0x9839f0cc]
1   __CFBasicHashAddValue + 1920 (CoreFoundation) [0x9833fd10]
1   __CFRepositionTimerInMode + 93 (CoreFoundation) [0x983b3dcd]
1   CFArrayRemoveValueAtIndex + 118 (CoreFoundation) [0x9839f226]
1   _CFArrayReplaceValues + 1786 (CoreFoundation) [0x983706ba]
1   <Non-Frontmost App>
1   __CFRepositionTimerInMode + 102 (CoreFoundation) [0x983b3dd6]
1   __CFRunLoopInsertionIndexInTimerArray + 253 (CoreFoundation) [0x983b3f0d]
6   __CFRunLoopDoTimer + 2093 (CoreFoundation) [0x983f4b1d]
4   __CFRunLoopFindMode + 201 (CoreFoundation) [0x98386809]
4   CFSetGetValue + 101 (CoreFoundation) [0x9836d685]
1   CFBasicHashFindBucket + 780 (CoreFoundation) [0x983401cc]
1   __CFRunLoopModeHash + 20 (CoreFoundation) [0x98386d14]
1   __CFStringHash + 259 (CoreFoundation) [0x98347113]
1   <Non-Frontmost App>
1   CFBasicHashFindBucket + 791 (CoreFoundation) [0x983401d7]
1   <Non-Frontmost App>
1   CFBasicHashFindBucket + 2334 (CoreFoundation) [0x983407de]
1   CFBasicHashFindBucket + 2453 (CoreFoundation) [0x98340855]
1   CFEqual + 49 (CoreFoundation) [0x98355061]
2   __CFSetCreateGeneric + 496 (CoreFoundation) [0x9836d620]
4   __CFRunLoopDoTimer + 557 (CoreFoundation) [0x983f451d]
2   __CFArmNextTimerInMode + 570 (CoreFoundation) [0x983b418a]
2   _dispatch_kevent_find + 82 (libdispatch.dylib) [0x91da2f1b]
2   mk_timer_arm + 10 (libsystem_kernel.dylib) [0x91df70ca]
2   <Kernel mode>
1   CFRunArrayGetValueAtIndex + 144 (CoreFoundation) [0x983b11d0]
1   __CFRunLoopDoTimer + 2115 (CoreFoundation) [0x983f4b33]
1   CFRelease + 112 (CoreFoundation) [0x9834ed30]
1   __CFRunLoopDoTimer + 1976 (CoreFoundation) [0x983f4aa8]
1   CFDictionaryGetKeysAndValues + 496 (CoreFoundation) [0x98364a40]
1   CFAllocatorGetDefault + 48 (CoreFoundation) [0x9838f020]
1   <Non-Frontmost App>
1   __CFRunLoopCreate + 864 (CoreFoundation) [0x98386740]
1   <Non-Frontmost App>
1   __CFRunLoopDoTimer + 1831 (CoreFoundation) [0x983f4a17]
1   mach_absolute_time + 29 (libsystem_kernel.dylib) [0x91df60e8]
1   __CFRunLoopDoTimer + 2012 (CoreFoundation) [0x983f4acc]
1   CFRetain + 28 (CoreFoundation) [0x9833ce8c]
1   __CFRunLoopDoTimers + 381 (CoreFoundation) [0x9846f08d]
1   CFRelease + 436 (CoreFoundation) [0x9834ee74]
1   -[NSObject release] + 25 (libobjc.A.dylib) [0x998a85d9]
1   _objc_rootReleaseWasZero + 54 (libobjc.A.dylib) [0x998934b1]
1   os_lock_trylock + 11 (libsystem_platform.dylib) [0x9414f65a]
1   __CFRunLoopDoTimers + 146 (CoreFoundation) [0x9846efa2]
1   CFArrayGetValueAtIndex + 139 (CoreFoundation) [0x98363c4b]
1   __CFRunLoopDoTimers + 222 (CoreFoundation) [0x9846efee]
1   objc_msgSend + 29 (libobjc.A.dylib) [0x998924ad]
7   __CFRunLoopRun + 1022 (CoreFoundation) [0x983ac05e]
7   __CFRunLoopDoSources0 + 235 (CoreFoundation) [0x983ac95b]
7   __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15 (CoreFoundation) [0x983bbb5f]
7   ??? [0x2923e858]
5   ??? [0x291ef5d6]
2   ??? [0x291eb1c4]
2   ??? [0x28da63db]
2   ??? [0x291eb1bf]
2   ??? [0x28edad53]
1   ??? [0x28eda0e0]
1   ??? [0x290437b4]
1   pthread_mutex_lock + 16 (libsystem_pthread.dylib) [0x9041d7ac]
1   _pthread_mutex_lock + 53 (libsystem_pthread.dylib) [0x9041d7e6]
1   ??? [0x28eda2de]
1   pthread_mutex_unlock + 83 (libsystem_pthread.dylib) [0x9041daf9]
1   OSAtomicCompareAndSwap64Barrier$VARIANT$mp + 26 (libsystem_platform.dylib) [0x9414f39a]
1   ??? [0x291eb209]
1   <Non-Frontmost App>
2   ??? [0x291ef5e9]
2   ??? [0x291eee88]
2   ??? [0x29182660]
4   __CFRunLoopRun + 1393 (CoreFoundation) [0x983ac1d1]
4   __CFRunLoopServiceMachPort + 169 (CoreFoundation) [0x983acbf9]
2   mach_msg + 68 (libsystem_kernel.dylib) [0x91df616c]
2   mach_msg_trap + 10 (libsystem_kernel.dylib) [0x91df6f7a]
1   <Non-Frontmost App>
1   <Non-Frontmost App, Kernel mode>
4   __CFRunLoopRun + 974 (CoreFoundation) [0x983ac02e]
4   __CFRunLoopDoObservers + 399 (CoreFoundation) [0x983bb20f]
4   __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 30 (CoreFoundation) [0x983bb2be]
1   __NSConnectionDoQueuedWork + 86 (Foundation) [0x90fd3a23]
1   objc_msgSend + 29 (libobjc.A.dylib) [0x998924ad]
1   __NSConnectionDoQueuedWork + 47 (Foundation) [0x90fd39fc]
1   _CFAutoreleasePoolPush + 18 (CoreFoundation) [0x983708d2]
1   __NSConnectionDoQueuedWork + 690 (Foundation) [0x90fd3c7f]
1   __NSConnectionDoQueuedWork + 77 (Foundation) [0x90fd3a1a]
1   pthread_key_init_np + 105 (libsystem_pthread.dylib) [0x9041e90d]
2   __CFRunLoopRun + 1482 (CoreFoundation) [0x983ac22a]
2   __CFRunLoopRun + 2130 (CoreFoundation) [0x983ac4b2]
2   __CFRunLoopDoSource1 + 523 (CoreFoundation) [0x983bbd7b]
2   __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 53 (CoreFoundation) [0x983bbe15]
2   __CFMachPortPerform + 440 (CoreFoundation) [0x983bbfe8]
2   MessageHandler(__CFMachPort*, void*, long, void*) + 52 (HIToolbox) [0x9ad4c726]
1   PullEventsFromWindowServerOnConnection(unsigned int, unsigned char, __CFMachPortBoost*) + 99 (HIToolbox) [0x9ad4c7bd]
1   CGEventCreateNextEvent + 39 (CoreGraphics) [0x922c97cb]
1   CGSGetNextEventRecordInternal + 84 (CoreGraphics) [0x922c9864]
1   CGSSnarfAndDispatchDatagrams + 385 (CoreGraphics) [0x922c9aff]
1   CGSDatagramReadStreamDispatchDatagramsWithData + 160 (CoreGraphics) [0x922c9e19]
1   CGSDatagramReadStream::dispatch_datagrams() + 47 (CoreGraphics) [0x922ca007]
1   CGSDatagramReadStream::dispatch_next_datagram() + 806 (CoreGraphics) [0x922ca33a]
1   event_datagram_handler + 71 (CoreGraphics) [0x922cad15]
1   CGSDecodeEventRecord + 76 (CoreGraphics) [0x922cad6b]
1   CFDataCreate + 41 (CoreFoundation) [0x983972c9]
1   __CFDataInit + 233 (CoreFoundation) [0x9835c6b9]
1   _CFRuntimeCreateInstance + 225 (CoreFoundation) [0x983391f1]
1   CFAllocatorAllocate + 198 (CoreFoundation) [0x983393f6]
1   __CFAllocatorSystemAllocate + 24 (CoreFoundation) [0x98339428]
1   malloc_zone_malloc + 75 (libsystem_malloc.dylib) [0x918d255b]
1   szone_malloc + 24 (libsystem_malloc.dylib) [0x918c5b6a]
1   _os_lock_corruption_abort + 2 (libsystem_platform.dylib) [0x9414f6ea]
1   PullEventsFromWindowServerOnConnection(unsigned int, unsigned char, __CFMachPortBoost*) + 245 (HIToolbox) [0x9ad4c84f]
1   CreateAndPostEventWithCGEvent(__CGEvent*, unsigned long, unsigned char, __CFMachPortBoost*) + 60 (HIToolbox) [0x9aed76aa]
1   CreateEventWithCGEvent + 5391 (HIToolbox) [0x9ad4e100]
1   AddWindowDataToMouseEvent(OpaqueWindowPtr*, CGPoint, OpaqueEventRef*) + 187 (HIToolbox) [0x9ad8fc52]
1   _FindWindowPartHit + 71 (HIToolbox) [0x9ad8fd13]
1   HitTestWindowDefinition(WindowData*, Point) + 299 (HIToolbox) [0x9ad8fe85]
1   SendEventToEventTargetWithOptions + 94 (HIToolbox) [0x9ad1f4e0]
1   SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 386 (HIToolbox) [0x9ad1f668]
1   DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 430 (HIToolbox) [0x9ad1ff51]
1   GenerateHandlerStackForEventTypeFromTarget(EventTargetRec*, unsigned long, unsigned long, HandlerRec**, unsigned long*) + 47 (HIToolbox) [0x9aece047]
1   TEventTypeIndex::ContainsType(unsigned long, unsigned long) + 75 (HIToolbox) [0x9aecde69]
1   EntrySearch(void const*, void const*, long, unsigned long, void*, int (*)(void const*, void const*, void const*), unsigned long*) + 153 (HIToolbox) [0x9ad1f3e9]
1   TEventTypeIndex::ClassCompareProc(void const*, void const*, void const*) + 12 (HIToolbox) [0x9ad1f434]
2   __CFRunLoopRun + 1199 (CoreFoundation) [0x983ac10f]
2   __CFRunLoopDoObservers + 399 (CoreFoundation) [0x983bb20f]
2   __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 30 (CoreFoundation) [0x983bb2be]
1   FlushAllBuffers(__CFRunLoopObserver*, unsigned long, void*) + 543 (HIToolbox) [0x9ad4c22a]
1   CFRunLoopTimerSetNextFireDate + 101 (CoreFoundation) [0x983f3905]
1   CFAbsoluteTimeGetCurrent + 7 (CoreFoundation) [0x9838f027]
1   <Non-Frontmost App>
1   FlushAllBuffers(__CFRunLoopObserver*, unsigned long, void*) + 256 (HIToolbox) [0x9ad4c10b]
1   FlushWindowObject(WindowData*, void**, unsigned char) + 993 (HIToolbox) [0x9ad41dd3]
1   GetWindowProperty + 48 (HIToolbox) [0x9ad42263]
1   GetWindowData(OpaqueWindowPtr*) + 32 (HIToolbox) [0x9ad310e0]
1   HIObject::GetCFTypeID() + 73 (HIToolbox) [0x9ad1d777]
1   <Non-Frontmost App>
1   __CFRunLoopRun + 1490 (CoreFoundation) [0x983ac232]
1   pthread_mutex_lock + 16 (libsystem_pthread.dylib) [0x9041d7ac]
1   __psynch_mutexwait + 10 (libsystem_kernel.dylib) [0x91dfb802]
1   <Non-Frontmost App, Kernel mode>
2   CFRunLoopRunSpecific + 421 (CoreFoundation) [0x983aba05]
1   __CFRunLoopDoObservers + 436 (CoreFoundation) [0x983bb234]
1   CFRelease + 112 (CoreFoundation) [0x9834ed30]
1   __CFRunLoopDoObservers + 370 (CoreFoundation) [0x983bb1f2]
1   pthread_mutex_unlock + 83 (libsystem_pthread.dylib) [0x9041daf9]
1   OSAtomicCompareAndSwap64Barrier$VARIANT$mp + 26 (libsystem_platform.dylib) [0x9414f39a]
1   <Non-Frontmost App>
3   ReceiveNextEventCommon + 163 (HIToolbox) [0x9ad43777]
3   RunCurrentEventLoopInMode + 259 (HIToolbox) [0x9ad43b5d]
3   CFRunLoopRunInMode + 123 (CoreFoundation) [0x983ab84b]
1   CFRunLoopRunSpecific + 394 (CoreFoundation) [0x983ab9ea]
1   __CFRunLoopRun + 1393 (CoreFoundation) [0x983ac1d1]
1   __CFRunLoopServiceMachPort + 169 (CoreFoundation) [0x983acbf9]
1   mach_msg_trap + 10 (libsystem_kernel.dylib) [0x91df6f7a]
1   <Non-Frontmost App, Kernel mode>
1   CFRunLoopRunSpecific + 371 (CoreFoundation) [0x983ab9d3]
1   __CFRunLoopDoObservers + 399 (CoreFoundation) [0x983bb20f]
1   __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 30 (CoreFoundation) [0x983bb2be]
1   FlushAllBuffers(__CFRunLoopObserver*, unsigned long, void*) + 238 (HIToolbox) [0x9ad4c0f9]
1   <Non-Frontmost App>
1   CFRunLoopRunSpecific + 118 (CoreFoundation) [0x983ab8d6]
1   __CFRunLoopFindMode + 189 (CoreFoundation) [0x983867fd]
14 ??? (AppFramework + 11717) [0xce67dc5]
14 SendEventToEventTarget + 88 (HIToolbox) [0x9ad32811]
14 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 386 (HIToolbox) [0x9ad1f668]
13 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2546 (HIToolbox) [0x9ad20795]
9   ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 3046 (HIToolbox) [0x9ad53962]
9   SendEventToEventTarget + 88 (HIToolbox) [0x9ad32811]
9   SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 386 (HIToolbox) [0x9ad1f668]
9   DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1452 (HIToolbox) [0x9ad2034f]
9   _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36 (HIToolbox) [0x9aeccd89]
7   GetPlugIn + 288572 (Application UI) [0xe89595c]
7   GetPlugIn + 298150 (Application UI) [0xe897ec6]
7   CEventDispatcher::DispatchEvent(IEvent*, IEvent::SystemHandledState) + 24 (PublicLib.dylib) [0x1274228]
6   CEventDispatcher::DispatchToEventHandlers(IEvent*) + 222 (PublicLib.dylib) [0x127476e]
6   CTrackerEventHandler::MouseDrag(IEvent*) + 85 (WidgetBinLib.dylib) [0x2885b35]
3   ??? (Layout UI + 562209) [0xd910421]
3   CTracker::HandleContinueTracking(SysPoint const&) + 460 (WidgetBinLib.dylib) [0x288446c]
3   ??? (Layout UI + 174405) [0xd8b1945]
3   ??? (Layout UI + 188480) [0xd8b5040]
2   CSprite::Show(IGraphicsContext*, PMPoint const&, long, PMMatrix*) + 1271 (WidgetBinLib.dylib) [0x28aef37]
2   CSprite::ShowSprite(IGraphicsContext*, PMPoint const&, long, PMMatrix*) + 3944 (WidgetBinLib.dylib) [0x28ba788]
2   CSprite::DrawShapes(IGraphicsContext*, __HIShape*, short) + 1263 (WidgetBinLib.dylib) [0x28b152f]
2   GetPlugIn + 111358 (AppFramework) [0xcea4e1e]
2   ??? (Spread + 36774) [0x120defa6]
2   ??? (Spread + 27746) [0x120dcc62]
1   ??? (Spread + 16508) [0x120da07c]
1   ??? [0x136aa662]
1   ??? [0x136a9df5]
1   GetPlugIn + 154463 (Generic Page Item) [0x12dcfb4f]
1   ??? [0x136aa24c]
1   CShape::ProcessDrawShape(GraphicsData*, long) + 314 (PublicLib.dylib) [0x134fc1a]
1   CGraphicFrameShape::DrawShape(GraphicsData*, long) + 158 (PublicLib.dylib) [0x134d99e]
1   CGraphicFrameShape::DrawShape_Fill(GraphicsData*, long) + 257 (PublicLib.dylib) [0x134f9b1]
1   PathPageItem::Fill(IGraphicsPort*) + 766 (PublicLib.dylib) [0x12f88de]
1   GetPlugIn + 82472 (AppFramework) [0xce9dd48]
1   AGMInitialize + 1932130 (AdobeAGM) [0x38634e]
1   AGMInitialize + 2064146 (AdobeAGM) [0x3a66fe]
1   AGMInitialize + 2361923 (AdobeAGM) [0x3ef22f]
1   AGMInitialize + 65229 (AdobeAGM) [0x1be6b9]
1   AGMInitialize + 2361923 (AdobeAGM) [0x3ef22f]
1   AGMInitialize + 65229 (AdobeAGM) [0x1be6b9]
1   AGMInitialize + 65229 (AdobeAGM) [0x1be6b9]
1   AGMInitialize + 3770562 (AdobeAGM) [0x5470ae]
1   AGMInitialize + 3759712 (AdobeAGM) [0x54464c]
1   AGMInitialize + 3728396 (AdobeAGM) [0x53cbf8]
1   AGMInitialize + 3548403 (AdobeAGM) [0x510cdf]
1   AGMInitialize + 3227174 (AdobeAGM) [0x4c2612]
1   AGMInitialize + 3357975 (AdobeAGM) [0x4e2503]
1   ??? (Spread + 16857) [0x120da1d9]
1   GetPlugIn + 114769 (AppFramework) [0xcea5b71]
1   GetPlugIn + 114115 (AppFramework) [0xcea58e3]
1   ??? (Transparency + 12615) [0x100ac147]
1   ??? (Transparency + 11065) [0x100abb39]
1   ??? (Transparency + 9582) [0x100ab56e]
1   GetPlugIn + 83304 (AppFramework) [0xce9e088]
1   AGMInitialize + 1927887 (AdobeAGM) [0x3852bb]
1   AGMInitialize + 2061406 (AdobeAGM) [0x3a5c4a]
1   AGMInitialize + 2361627 (AdobeAGM) [0x3ef107]
1   AGMInitialize + 63163 (AdobeAGM) [0x1bdea7]
1   AGMInitialize + 2361627 (AdobeAGM) [0x3ef107]
1   AGMInitialize + 63163 (AdobeAGM) [0x1bdea7]
1   AGMInitialize + 63163 (AdobeAGM) [0x1bdea7]
1   AGMInitialize + 3758549 (AdobeAGM) [0x5441c1]
1   AGMInitialize + 3750751 (AdobeAGM) [0x54234b]
1   AGMInitialize + 3728396 (AdobeAGM) [0x53cbf8]
1   AGMInitialize + 3545306 (AdobeAGM) [0x5100c6]
1   AGMInitialize + 2896453 (AdobeAGM) [0x471a31]
1   AGMInitialize + 141366 (AdobeAGM) [0x1d1022]
1   ACEHasFeature + 9583 (AdobeACE) [0xa2a3d]
1   ACEHasFeature + 364604 (AdobeACE) [0xf950a]
1   ??? (AdobeACE + 264901) [0x67ac5]
1   ??? (AdobeACE + 242203) [0x6221b]
1   ??? (AdobeACE + 314102) [0x73af6]
1   ??? (AdobeACE + 280297) [0x6b6e9]
1   ACEHasFeature + 66107 (AdobeACE) [0xb0709]
1   CSprite::Show(IGraphicsContext*, PMPoint const&, long, PMMatrix*) + 316 (WidgetBinLib.dylib) [0x28aeb7c]
1   GetPlugIn + 246537 (Color Management) [0xe48a3c9]
1   GetPlugIn + 245749 (Color Management) [0xe48a0b5]
1   GetPlugIn + 242129 (Color Management) [0xe489291]
1   GetPlugIn + 238913 (Color Management) [0xe488601]
1   ??? (AdobeAGM + 143951) [0x1ad24f]
1   AGMInitialize + 2368057 (AdobeAGM) [0x3f0a25]
1   ??? (AdobeAGM + 41129) [0x1940a9]
2   ??? (Layout UI + 283687) [0xd8cc427]
2   ??? (Layout UI + 291556) [0xd8ce2e4]
2   ??? (Layout UI + 69882) [0xd8980fa]
2   ??? (Layout UI + 55601) [0xd894931]
2   ??? (Layout UI + 54119) [0xd894367]
2   ??? (Layout UI + 46146) [0xd892442]
2   ??? (Layout UI + 42187) [0xd8914cb]
2   GetPlugIn + 99899 (AppFramework) [0xcea215b]
2   ??? (Spread + 36774) [0x120defa6]
1   ??? (Spread + 23632) [0x120dbc50]
1   GetPlugIn + 82600 (AppFramework) [0xce9ddc8]
1   AGMInitialize + 1933000 (AdobeAGM) [0x3866b4]
1   AGMInitialize + 2064628 (AdobeAGM) [0x3a68e0]
1   AGMInitialize + 2362003 (AdobeAGM) [0x3ef27f]
1   AGMInitialize + 65955 (AdobeAGM) [0x1be98f]
1   AGMInitialize + 2362003 (AdobeAGM) [0x3ef27f]
1   AGMInitialize + 65955 (AdobeAGM) [0x1be98f]
1   AGMInitialize + 65955 (AdobeAGM) [0x1be98f]
1   AGMInitialize + 3769489 (AdobeAGM) [0x546c7d]
1   AGMInitialize + 3331364 (AdobeAGM) [0x4dbd10]
1   AGMInitialize + 3330289 (AdobeAGM) [0x4db8dd]
1   AGMInitialize + 3322985 (AdobeAGM) [0x4d9c55]
1   AGMInitialize + 3320486 (AdobeAGM) [0x4d9292]
1   AGMInitialize + 2912269 (AdobeAGM) [0x4757f9]
1   AGMInitialize + 2912899 (AdobeAGM) [0x475a6f]
1   AGMInitialize + 2459235 (AdobeAGM) [0x406e4f]
1   ??? (Spread + 27746) [0x120dcc62]
1   ??? (Spread + 16508) [0x120da07c]
1   ??? [0x136aa662]
1   ??? [0x136a9df5]
1   GetPlugIn + 154463 (Generic Page Item) [0x12dcfb4f]
1   ??? [0x136aa24c]
1   CShape::ProcessDrawShape(GraphicsData*, long) + 314 (PublicLib.dylib) [0x134fc1a]
1   CGraphicFrameShape::DrawShape(GraphicsData*, long) + 242 (PublicLib.dylib) [0x134d9f2]
1   CGraphicFrameShape::DrawShape_Hierarchy(GraphicsData*, long) + 326 (PublicLib.dylib) [0x134fdf6]
1   CShape::DrawHierarchy(GraphicsData*, long) + 365 (PublicLib.dylib) [0x134ce9d]
1   CShape::ProcessDrawShape(GraphicsData*, long) + 314 (PublicLib.dylib) [0x134fc1a]
1   GetPlugIn + 905566 (Text) [0x1145d5ce]
1   GetPlugIn + 901238 (Text) [0x1145c4e6]
1   CShape::ProcessDrawShape(GraphicsData*, long) + 314 (PublicLib.dylib) [0x134fc1a]
1   GetPlugIn + 1891073 (Text) [0x1154df71]
1   GetPlugIn + 1930509 (Text) [0x1155797d]
1   GetPlugIn + 1927280 (Text) [0x11556ce0]
1   GetPlugIn + 1832719 (Text) [0x1153fb7f]
1   GetPlugIn + 1832070 (Text) [0x1153f8f6]

When I create a calendar, in iphoto 8, I had an information pane lower left corner with date and time of the picture. Can it possibly be that the iphoto developers forgot about that in iphoto 9? This was very helpful when placing images according to date.

Today I updated to the latest iphoto version. The update itself went smooth and nice as one is used to from Apple. But when I wanted to finish my already started calendar, I have encountered two problems. The first is that I can't view the aperture library anymore directly from iphoto. Instead I have to open the iphtoto library in aperture but then my calendar isn't there. So now I have to copy images back and forth. No problem.
However, the old iphoto had a small information area in the lower left corner which was very nice to place images on an exact date. This seems to be gone...?? Really? How am I supposed to sort images according to date and time when I have to back to the library view every time? That's not very convenient..Or am I missing something?
Thanks for ANY help!
Patrick

The first is that I can't view the aperture library anymore directly from iphoto.
THat is exceeding strange since iPhoto '08 could not open or share an Aperture library - that ability was first introduced in iPhoto '11 - with the latest version of iPhoto and or Aperture you can open the same library with either application - http://support.apple.com/kb/HT5043
In the current version of iPhoto the photos are sorted by date in the film strip - I've not recently done a calendar so do not remember the specifics -
LN

InDesign CS6 Crashes When Placing Images

Crash data: http://pastebin.com/CaBML9zw
This problem just started this weekend, but every time I try to place an image into this file, InDesign crashes. I've exported the project to an IDML file, then worked off of it, but it does the same thing. When I try to relaunch InDesign, it often will not open again & gives a "serious error" pop-up (apologies for not having the screenshot on here).
Could someone help me decipher this please? I'm about to throw things.
I'd really appreciate some help with this. Thank you!

Does it happen in other files withthe same image(s)? How about in a new user?

InDesign Settings When Placing Image Screen Cap from SnagIt

I've already tried obtaining assistance from the SnagIt people, but they feel it's an InDesign setting I'm missing, which is likely since my skill with InDesign is very beginner level. Thank you kindly for any assistance.
I produce training materials for software and need to take screen captures that will then be inserted into InDesign. I do the production myself and then give to a printer.
I cannot, for the life of me, get the images to look half decent in InDesign. I save at 96 dpi, 300 dpi, tif RGB, tif CMYK, PNG etc. and to be honest, the captures look worse once they hit InDesign than if I took a basic windows screen cap.
The screen caps should be presented at a reasonable, readable size in InDesign as they are for instruction purposes. Professionally printed computer manuals is the quality I'm looking for.
SPECS:
CPU: Intel Core 2 Series Processor (2400 MHz) -- THIS IS A QUAD CORE
Memory: 4095 MB
OS Version: Microsoft Windows 7 64-bit (Build 7600) -- ULTIMATE VERSION
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 8800 GTX/PCI/SSE2 -- 2 SLI'd
Windows Graphics Driver Version: 8.17.0011.9562
I know I'm doing something wrong. The saved images look fine on my screen (I use ACDSee to view). But the moment I put them in InDesign, they look horrid (blurry, jaggy).
If you can't help me, do you know of someone who can?
I tried on the SnagIt forums, and no helpful responses.
Thank you kindly.
Sincerely,
Alexandria

You don’t say what’s wrong with the screen captures, but since you list several different resolutions I can guess. You are resampling and Photoshop is trying to produce smooth results, assuming the image is a photograph and that aliased (pixelated) details are undesirable.
Screen captures look best when they are not resampled. Save them in a lossless format like PNG or TIF and place them unmodified. If you edit them and add any layers or text (Layers panel shows anything but a single Background layer), then save as PSD or Photoshop PDF. Some print shops might either flag those low-res files as problems, or try to “help” you by upsampling them. You can avoid these issues by resampling in Photoshop using Nearest Neighbor interpolation. Use full 100% increments, ie: not from 72 ppi to 300 ppi (416.67%) but 72 to 288 ppi (400%).
Other tricks to explore are changing the antialiasing method of your display. Sub-pixel antialiasing is often used for LCD displays, but when enlarged and printed (look at the noise around “Font Family”) can be ugly. On a Mac you can turn this off in the Appearance Preference Pane.
Black can be a nuisance with screen captures. Your screen captures are probably saved in RGB. When they are printed the RGB values are converted to CMYK by the print shop. Normally, this is not something to be concerned with. But Black in RGB (0,0,0) is usually treated as a rich black or photographic black, and is converted to a colour with lots of each CMYK ink in it. For the fine type, dialogues, and lines of a screen grab, that is undesireable.
I have my own way of dealing with this, and I know others who have similar, but not identical, workflows. All require Photoshop. If you want further help with this, please ask either here or in the Photoshop forum.

Dreamweaver quits unexpectedly when placing images

I'm running Dreamweaver CS 5.5 on Mac OS X 10.6.7. I've been using Dreamweaver for about 11 or 12 years.
I just upgraded hoping this particular glitch would have been corrected. Alas it's not been.
About 30-40% of the time, when I try to insert an image in a page, Dreamweaver will unexpectedly quit as soon as I click "choose" in the dialog box.
This has happened whether I initiate the action via:
keyboard command (opt-cmd-i)
a click on the insert file icon in the application bar
selecting the code hint, "browse", after typing <img src="" in the code
The key seems to be the open/save dialog box. I am running the Default Folder X utility. Disabling it doesn't have an effect on the problem's frequency.
Aside from that, I haven't noticed any correlation with other open apps or other actions.
Because it happens so often, I avoid using the dialog box now to insert images. I just type in the source window. It's slowed down my workflow a bit.
Anyone else have this problem?
Any suggestions?
Thanks.

Thanks for your response.
Well, "mastery" is a strong term. I'm pretty competent, though. I manage a couple of dozen websites for my clients and am quite familiar with defining sites, managing my files, and interacting with my servers through DW. I'm fairly good at HTML, CSS, and JavaScript with a little PHP thrown in.
I can drag images from my local files panel onto my web page without crashing. I can target images with the point to file feature (though there's an unrelated DW glitch with the pointer that's being discussed in another forum).
The problem occurs only when I interact with the OS's open/save dialog box.
My MacPro (2 x 2.66 GHz Dual-Core Xeon) is coming up on 3 years old. I think it's my fifth Mac since first using DW a dozen or so years ago.
My box has 11GB of 667MHz memory and about 2.5TB of free disk space on 4 internal disks.
I use separate machines for my Windows testing, so this is strictly a Mac OS production box.
Though I'm sure I could do better, I try to keep everything well-managed and do fairly regular file system checks and PRAM cleanings. I run up-to-date anti-viral software (Norton).
I also keep my system and applications up to snuff with the latest updates.
I often have a good number of other applications open at one time (Photoshop, Illustrator, Flash, Safari, et al), though I've had this same problem when DW is one of only a couple of applications running.
The unexpected quitting problem isn't something I recall happening prior to CS5. As I mentioned, I had hoped the CS5.5 upgrade would correct it.
I believe my current Mac started with CS3 installed, later upgraded to CS4, then to CS5.
Thanks again.

Spinning wheel when placing web content.

Whenever I place HTML files or .oam files into DPS folios I get the spinning wheel briefly on the page before the HTML content loads, only for maybe half a second (longer on my old iPad 1!!) but it's very annoying as the animation is only very simple. The oam file especially is only 78k!! Can someone explain why the action isn't instant as with the internal functionality of DPS such as auto play MSOs and such. And if there is a way to avoid it.
Thanks in advance,
Jon

Hi,
It is something I have tried to look into before with no answer as of yet.
It is annoying, really this should be something that we should be able to turn off in the web overlay because a lot of the interactive features we build are through HTML or edge files it always seems like you are loading an add on rather than the content being integrated into the app. Maybe there should be a feature to preload the HTML5 content and only play on page load which would stop the content delay issues.
Cheers
Rob

Strange problem with image scaling when placed

I'm currently running InDesign CS6 from the Creative Cloud, and it's version 8.0. I have a PC and am running Windows 8.
I am experiencing a really odd problem when placing images, and it only recently (within the last two weeks perhaps?) has developed. I do ebook production for a publisher. I have an InDesign template (INDD file really, but "blank" and ready to be filled in, and as such I refer to it as a "template") that I use, and the cover for the book goes on the first page. The document is set to pixels as the ruler measurement, and the pages are 650 pixels wide by 800 pixels tall. The margins are all set at zero. The cover images are sent to me as JPEGs and always have the same size: 72dpi setting and 500 pixels wide by 750 pixels tall. This is chosen to be about the size of the full screen on most ereaders, or close enough to be so.
So when working on a new book, I put my cursor in the blank line that is set up to take the cover as an inline image. I do control-D to place, select the file, and hit enter. This SHOULD place an image at that location that is 500 pixels wide and 750 pixels tall when looking at the InDesign page rulers. Instead, InDesign insists on placing this image at 50% scaling, so that it is only 250 pixels wide by 375 pixels tall. And in the link info panel, it shows the actual PPI as 72 and the effective PPI as 144. It does this no matter how many preference changes I try (including the ones under file handling and the import setting options).
The strangest part is that if the file is just a tiny bit different than 500x750 @72dpi, then there is no problem. For example, if I open the JPEG in Photoshop and change the image settings to 500x750 @73dpi, then InDesign places it at 100% scale like I want. If I change the image to 499x749 @72dpi it also gets placed in InDesign at 100% scaling. I've tried this with various new INDD documents with settings in pixels, inches, or picas as the ruler amounts, and with different page or margin sizes (just in case the problem is with my template). I get the same result no matter what.
It appears that InDesign somehow thinks that any image that is exactly 500x750 @72dpi should be scaled at 50% when placing it into an InDesign file. Has anyone else run across this? Is it a bug or something I'm doing wrong? I've been doing this exact procedure for over a year, first with CS5 and now CS6, and I've never had this happen until just recently. I suppose it COULD be an accidental change in settings or preferences. But if it is, I cannot figure out how to change it back.
UPDATE: I installed the 8.0.1 update and it did not resolve the issue. I also tried more image options. It looks like this scaling to 50% upon placing ONLY happens when all three attributes match this: 500x750@72dpi. All of the following modifications to the exact same image placed in the exact same spot in the exact same document resolved the issue:
501x750@72dpi
499x750@72dpi
500x751@72dpi
500x749@72dpi
500x750@71dpi
500x750@73dpi
But of course, I don't want to have to modify every cover image I'm sent in order to prevent this scaling issue.

I just tried this and got the same results (CS6, 8.0.1, on WinXP SP3). One other tidbit: the same 500px × 750 px @ 72ppi image saved as TIFF instead of JPEG worked correctly (at least for me). I haven't tried any other image formats yet.
This sounds like a good candidate for an official bug report: http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
-Bill

Odd pause in Ai2014 when selecting placed image

So as I’m working in AI2014, Im noticing a rather annoying glitch. Every time I select a placed image (.psd, .eps, .tiff, etc) there is a long pause when the ‘rainbow spinning wheel’ comes up for a few seconds to a few minutes. Not sure what AI is doing but it’s really annoying. (it also will crash from time to time or lock up for so long that I have to force quit it.
Last night I closed my Links tab and I noticed that the pause wasn’t happening…. what is it about having the links panel open that effects my performance?? I must mention that this WAS NOT the case in CC and 6.
Any dev have any workaround? (and no, keeping the links panel closed isn't really a good option)

Maybe -- with regard to sharing. I had modified the file since this problem came up (by removing the underlying type in photoshop) so I need to see if I still have an original to share.
One other note. I had gotten the ad from a co-worker who had set it up. One mistake in my original post is that the black box placed over the underlying type was 100% K and not a 4-color black.
In order to share, how do I get you the file(s) and do you want both the PDF and InDesign/Photoshop files?

Spinning rainbow when placing images

Similar Messages

Maybe you are looking for