What is the use of History Brush Tool?
What is the use of History Brush Tool?
"The History Brush takes the power of the History panel and lets you focus it on
specific parts of an image. So instead of sending the entire image back in time, you
can use this brush to paint edits away selectively, revealing the previous state of
your choosing. For example, you could darken a portrait with the Burn tool
and then use the History Brush to undo some of the darkening if you went too
far."
Which is precisely what I said, in only 9 words
(sorry, couldn't resist)
Similar Messages
-
lightroom 5 on mac osx 10.9.2 keeps crashing, seem to be when using my mask brush tool but I'm using it a lot so I'm not sure its the cause or what
Here is the report, but i don't understand it. can anyone help, PLEASE
Process: Adobe Photoshop Lightroom 5 [1343]
Path: /Applications/Adobe Photoshop Lightroom 5.app/Contents/MacOS/Adobe Photoshop Lightroom 5
Identifier: com.adobe.Lightroom5
Version: Adobe Photoshop Lightroom 5.4 [955652] (5.4)
Code Type: X86-64 (Native)
Parent Process: launchd [170]
Responsible: Adobe Photoshop Lightroom 5 [1343]
User ID: 501
Date/Time: 2014-05-13 15:04:50.033 -0400
OS Version: Mac OS X 10.9.2 (13C1021)
Report Version: 11
Anonymous UUID: 6ABE1616-31D9-8D3E-5E0B-EEF8ED3F6706
Crashed Thread: 10 AsyncDataServer
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff8e81aa1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8e819d18 mach_msg + 64
2 com.apple.CoreFoundation 0x00007fff8d49ffc5 __CFRunLoopServiceMachPort + 181
3 com.apple.CoreFoundation 0x00007fff8d49f5e9 __CFRunLoopRun + 1161
4 com.apple.CoreFoundation 0x00007fff8d49ef25 CFRunLoopRunSpecific + 309
5 com.apple.HIToolbox 0x00007fff856fba0d RunCurrentEventLoopInMode + 226
6 com.apple.HIToolbox 0x00007fff856fb7b7 ReceiveNextEventCommon + 479
7 com.apple.HIToolbox 0x00007fff856fb5bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
8 com.apple.AppKit 0x00007fff8b1303de _DPSNextEvent + 1434
9 com.apple.AppKit 0x00007fff8b12fa2b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
10 com.apple.AppKit 0x00007fff8b123b2c -[NSApplication run] + 553
11 com.apple.AppKit 0x00007fff8b10e913 NSApplicationMain + 940
12 com.adobe.Lightroom5 0x0000000104ffb613 main + 1107
13 com.adobe.Lightroom5 0x0000000104ffb1b8 start + 52
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff8e81f662 kevent64 + 10
1 libdispatch.dylib 0x00007fff8bd3143d _dispatch_mgr_invoke + 239
2 libdispatch.dylib 0x00007fff8bd31152 _dispatch_mgr_thread + 52
Thread 2:: ace
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.apple.CoreServices.CarbonCore 0x00007fff921d3800 TSWaitOnCondition + 108
3 com.apple.CoreServices.CarbonCore 0x00007fff921d39ff TSWaitOnConditionTimedRelative + 172
4 com.apple.CoreServices.CarbonCore 0x00007fff921a4145 MPWaitOnQueue + 192
5 com.adobe.ag.AgImageIO 0x0000000107ba81a6 0x1079aa000 + 2089382
6 com.adobe.ag.AgImageIO 0x0000000107ba7ed3 0x1079aa000 + 2088659
7 com.apple.CoreServices.CarbonCore 0x00007fff921a46c3 PrivateMPEntryPoint + 58
8 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
9 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
10 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 3:: ace
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.apple.CoreServices.CarbonCore 0x00007fff921d3800 TSWaitOnCondition + 108
3 com.apple.CoreServices.CarbonCore 0x00007fff921d39ff TSWaitOnConditionTimedRelative + 172
4 com.apple.CoreServices.CarbonCore 0x00007fff921a4145 MPWaitOnQueue + 192
5 com.adobe.ag.AgImageIO 0x0000000107ba81a6 0x1079aa000 + 2089382
6 com.adobe.ag.AgImageIO 0x0000000107ba7ed3 0x1079aa000 + 2088659
7 com.apple.CoreServices.CarbonCore 0x00007fff921a46c3 PrivateMPEntryPoint + 58
8 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
9 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
10 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 4:: cr_scratch
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.adobe.ag.AgImageIO 0x0000000107ab82b1 0x1079aa000 + 1106609
3 com.adobe.ag.AgImageIO 0x0000000107c77b6b 0x1079aa000 + 2939755
4 com.adobe.ag.AgImageIO 0x0000000107a821a1 0x1079aa000 + 885153
5 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
6 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
7 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 5:: Worker Thread Dispatcher
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x000000010503c5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x00000001050361a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x00000001050370a8 0x105016000 + 135336
5 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
6 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
7 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
8 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
9 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
10 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
11 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
12 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
13 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
14 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
15 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
16 com.adobe.ag.substrate 0x000000010518761b 0x105175000 + 75291
17 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
18 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
19 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
20 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 6:: Queue Processor - AgPhotoAvailability
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x000000010503c5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x00000001050361a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x00000001050370a8 0x105016000 + 135336
5 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
6 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
7 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
8 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
9 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
10 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
11 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
12 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
13 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
14 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
15 com.adobe.ag.kernel 0x000000010501a149 0x105016000 + 16713
16 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
17 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
18 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
19 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
21 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
22 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
23 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
24 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
25 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
26 com.adobe.ag.substrate 0x000000010518761b 0x105175000 + 75291
27 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
28 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
29 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
30 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 7:
0 libsystem_kernel.dylib 0x00007fff8e81aa1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8e819d18 mach_msg + 64
2 com.apple.CoreFoundation 0x00007fff8d49ffc5 __CFRunLoopServiceMachPort + 181
3 com.apple.CoreFoundation 0x00007fff8d49f5e9 __CFRunLoopRun + 1161
4 com.apple.CoreFoundation 0x00007fff8d49ef25 CFRunLoopRunSpecific + 309
5 com.apple.AppKit 0x00007fff8b2d016e _NSEventThread + 144
6 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
7 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
8 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 8:
0 libsystem_kernel.dylib 0x00007fff8e81aa1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8e819d18 mach_msg + 64
2 com.apple.CoreFoundation 0x00007fff8d49ffc5 __CFRunLoopServiceMachPort + 181
3 com.apple.CoreFoundation 0x00007fff8d49f5e9 __CFRunLoopRun + 1161
4 com.apple.CoreFoundation 0x00007fff8d49ef25 CFRunLoopRunSpecific + 309
5 com.apple.Foundation 0x00007fff88a99adc -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 253
6 com.adobe.wichitafoundation 0x00000001052763ea 0x1051e3000 + 603114
7 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
8 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
9 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
10 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 9:: com.apple.NSURLConnectionLoader
0 libsystem_kernel.dylib 0x00007fff8e81aa1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8e819d18 mach_msg + 64
2 com.apple.CoreFoundation 0x00007fff8d49ffc5 __CFRunLoopServiceMachPort + 181
3 com.apple.CoreFoundation 0x00007fff8d49f5e9 __CFRunLoopRun + 1161
4 com.apple.CoreFoundation 0x00007fff8d49ef25 CFRunLoopRunSpecific + 309
5 com.apple.Foundation 0x00007fff88a97967 +[NSURLConnection(Loader) _resourceLoadLoop:] + 348
6 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
7 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
8 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
9 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 10 Crashed:: AsyncDataServer
0 com.adobe.ag.kernel 0x000000010502be32 0x105016000 + 89650
1 com.adobe.ag.kernel 0x000000010502bf86 0x105016000 + 89990
2 com.adobe.ag.kernel 0x000000010502bae3 0x105016000 + 88803
3 com.adobe.ag.kernel 0x000000010502c251 0x105016000 + 90705
4 com.adobe.ag.kernel 0x000000010502c36d 0x105016000 + 90989
5 com.adobe.ag.kernel 0x0000000105023268 0x105016000 + 53864
6 com.adobe.ag.kernel 0x0000000105023990 0x105016000 + 55696
7 com.adobe.ag.kernel 0x000000010502333d 0x105016000 + 54077
8 com.adobe.ag.kernel 0x00000001050280c6 0x105016000 + 73926
9 com.adobe.ag.kernel 0x0000000105027bb4 0x105016000 + 72628
10 com.adobe.ag.kernel 0x0000000105028713 0x105016000 + 75539
11 com.adobe.ag.kernel 0x00000001050280a4 0x105016000 + 73892
12 com.adobe.ag.kernel 0x0000000105027bb4 0x105016000 + 72628
13 com.adobe.ag.kernel 0x0000000105028628 0x105016000 + 75304
14 com.adobe.ag.kernel 0x00000001050280b1 0x105016000 + 73905
15 com.adobe.ag.kernel 0x0000000105027bb4 0x105016000 + 72628
16 com.adobe.ag.kernel 0x0000000105028713 0x105016000 + 75539
17 com.adobe.ag.kernel 0x00000001050280a4 0x105016000 + 73892
18 com.adobe.ag.kernel 0x0000000105027bb4 0x105016000 + 72628
19 com.adobe.ag.kernel 0x0000000105028628 0x105016000 + 75304
20 com.adobe.ag.kernel 0x00000001050280b1 0x105016000 + 73905
21 com.adobe.ag.kernel 0x0000000105027bb4 0x105016000 + 72628
22 com.adobe.ag.kernel 0x0000000105028713 0x105016000 + 75539
23 com.adobe.ag.kernel 0x00000001050280a4 0x105016000 + 73892
24 com.adobe.ag.kernel 0x0000000105027bb4 0x105016000 + 72628
25 com.adobe.ag.kernel 0x0000000105027a46 0x105016000 + 72262
26 com.adobe.ag.kernel 0x0000000105027931 0x105016000 + 71985
27 com.adobe.ag.kernel 0x0000000105026a81 0x105016000 + 68225
28 com.adobe.ag.kernel 0x000000010502687b 0x105016000 + 67707
29 com.adobe.ag.kernel 0x00000001050202d4 0x105016000 + 41684
30 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
31 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
32 com.adobe.ag.kernel 0x000000010502025a 0x105016000 + 41562
33 com.adobe.ag.kernel 0x0000000105018113 lua_load + 68
34 com.adobe.ag.kernel 0x0000000105019470 luaL_loadbuffer + 32
35 com.adobe.ag.kernel 0x000000010501a109 0x105016000 + 16649
36 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
37 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
38 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
39 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
40 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
41 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
42 com.adobe.ag.kernel 0x000000010501a149 0x105016000 + 16713
43 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
44 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
45 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
46 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
47 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
48 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
49 com.adobe.ag.kernel 0x000000010501a149 0x105016000 + 16713
50 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
51 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
52 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
53 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
54 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
55 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
56 com.adobe.ag.kernel 0x000000010501a149 0x105016000 + 16713
57 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
58 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
59 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
60 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
61 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
62 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
63 com.adobe.ag.kernel 0x000000010501a149 0x105016000 + 16713
64 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
65 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
66 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
67 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
68 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
69 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
70 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
71 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
72 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
73 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
74 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
75 com.adobe.ag.substrate 0x000000010518761b 0x105175000 + 75291
76 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
77 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
78 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
79 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 11:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x00007fff8e81e9aa __select + 10
1 com.apple.CoreFoundation 0x00007fff8d4ebab3 __CFSocketManager + 867
2 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
3 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
4 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 12:: Preview Server
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x000000010503c659 AgConditionLock_wait + 184
3 com.adobe.ag.kernel 0x00000001050361a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x00000001050370a8 0x105016000 + 135336
5 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
6 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
7 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
8 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
9 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
10 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
11 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
12 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
13 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
14 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
15 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
16 com.adobe.ag.substrate 0x000000010518761b 0x105175000 + 75291
17 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
18 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
19 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
20 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 13:: Queue Processor - PreviewFileStore
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x000000010503c5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x00000001050361a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x00000001050370a8 0x105016000 + 135336
5 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
6 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
7 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
8 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
9 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
10 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
11 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
12 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
13 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
14 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
15 com.adobe.ag.kernel 0x000000010501a149 0x105016000 + 16713
16 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
17 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
18 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
19 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
21 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
22 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
23 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
24 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
25 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
26 com.adobe.ag.substrate 0x000000010518761b 0x105175000 + 75291
27 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
28 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
29 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
30 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 14:: Queue Processor - NegativeQueue
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x000000010503c5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x00000001050361a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x00000001050370a8 0x105016000 + 135336
5 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
6 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
7 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
8 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
9 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
10 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
11 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
12 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
13 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
14 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
15 com.adobe.ag.kernel 0x000000010501a149 0x105016000 + 16713
16 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
17 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
18 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
19 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
21 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
22 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
23 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
24 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
25 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
26 com.adobe.ag.substrate 0x000000010518761b 0x105175000 + 75291
27 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
28 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
29 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
30 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 15:: Queue Processor - HistogramQueue
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x000000010503c5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x00000001050361a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x00000001050370a8 0x105016000 + 135336
5 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
6 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
7 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
8 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
9 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
10 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
11 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
12 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
13 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
14 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
15 com.adobe.ag.kernel 0x000000010501a149 0x105016000 + 16713
16 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
17 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
18 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
19 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
21 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
22 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
23 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
24 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
25 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
26 com.adobe.ag.substrate 0x000000010518761b 0x105175000 + 75291
27 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
28 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
29 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
30 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 16:: Queue Processor - RenderQueue_Render
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x000000010503c5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x00000001050361a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x00000001050370a8 0x105016000 + 135336
5 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
6 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
7 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
8 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
9 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
10 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
11 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
12 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
13 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
14 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
15 com.adobe.ag.kernel 0x000000010501a149 0x105016000 + 16713
16 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
17 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
18 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
19 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
21 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
22 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
23 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
24 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
25 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
26 com.adobe.ag.substrate 0x000000010518761b 0x105175000 + 75291
27 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
28 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
29 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
30 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 17:: Queue Processor - RenderQueue_ReadPreview
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x000000010503c5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x00000001050361a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x00000001050370a8 0x105016000 + 135336
5 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
6 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
7 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
8 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
9 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
10 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
11 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
12 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
13 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
14 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
15 com.adobe.ag.kernel 0x000000010501a149 0x105016000 + 16713
16 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
17 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
18 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
19 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
21 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
22 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
23 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
24 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
25 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
26 com.adobe.ag.substrate 0x000000010518761b 0x105175000 + 75291
27 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
28 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
29 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
30 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 18:: Queue Processor - RenderQueue_Video
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x000000010503c5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x00000001050361a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x00000001050370a8 0x105016000 + 135336
5 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
6 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
7 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
8 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
9 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
10 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
11 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
12 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
13 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
14 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
15 com.adobe.ag.kernel 0x000000010501a149 0x105016000 + 16713
16 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
17 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
18 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
19 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
21 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
22 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
23 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
24 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
25 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
26 com.adobe.ag.substrate 0x000000010518761b 0x105175000 + 75291
27 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
28 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
29 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
30 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 19:: Queue Processor - RenderQueue_Face
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x000000010503c5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x00000001050361a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x00000001050370a8 0x105016000 + 135336
5 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
6 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
7 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
8 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
9 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
10 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
11 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
12 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
13 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
14 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
15 com.adobe.ag.kernel 0x000000010501a149 0x105016000 + 16713
16 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
17 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
18 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
19 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
21 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
22 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
23 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
24 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
25 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
26 com.adobe.ag.substrate 0x000000010518761b 0x105175000 + 75291
27 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
28 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
29 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
30 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 20:: Queue Processor - AgAsyncRenderingQueue
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x000000010503c5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x00000001050361a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x00000001050370a8 0x105016000 + 135336
5 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
6 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
7 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
8 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
9 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
10 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
11 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
12 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
13 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
14 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
15 com.adobe.ag.kernel 0x000000010501a149 0x105016000 + 16713
16 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
17 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
18 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
19 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
21 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
22 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
23 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
24 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
25 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
26 com.adobe.ag.substrate 0x000000010518761b 0x105175000 + 75291
27 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
28 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
29 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
30 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 21:: Queue Processor - OpenNegativesForDevelop
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x000000010503c5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x00000001050361a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x00000001050370a8 0x105016000 + 135336
5 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
6 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
7 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
8 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
9 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
10 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
11 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
12 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
13 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
14 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
15 com.adobe.ag.kernel 0x000000010501a149 0x105016000 + 16713
16 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
17 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
18 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
19 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
21 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
22 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
23 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
24 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
25 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
26 com.adobe.ag.substrate 0x000000010518761b 0x105175000 + 75291
27 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
28 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
29 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
30 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 22:: Worker Thread
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x000000010503c5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x00000001050361a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x00000001050370a8 0x105016000 + 135336
5 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
6 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
7 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
8 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
9 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
10 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
11 com.adobe.ag.kernel 0x000000010501a149 0x105016000 + 16713
12 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
13 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
14 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
15 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
16 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
17 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
18 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
19 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
20 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
21 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
22 com.adobe.ag.substrate 0x000000010518761b 0x105175000 + 75291
23 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
24 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
25 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
26 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 23:: Worker Thread
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x000000010503c5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x00000001050361a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x00000001050370a8 0x105016000 + 135336
5 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
6 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
7 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
8 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
9 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
10 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
11 com.adobe.ag.kernel 0x000000010501a149 0x105016000 + 16713
12 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
13 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
14 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
15 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
16 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
17 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
18 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
19 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
20 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
21 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
22 com.adobe.ag.substrate 0x000000010518761b 0x105175000 + 75291
23 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
24 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
25 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
26 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 24:: Worker Thread
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x000000010503c5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x00000001050361a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x00000001050370a8 0x105016000 + 135336
5 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
6 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
7 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
8 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
9 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
10 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
11 com.adobe.ag.kernel 0x000000010501a149 0x105016000 + 16713
12 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
13 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
14 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
15 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
16 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
17 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
18 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
19 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
20 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
21 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
22 com.adobe.ag.substrate 0x000000010518761b 0x105175000 + 75291
23 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
24 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
25 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
26 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 25:: Worker Thread
0 libsystem_kernel.dylib 0x00007fff8e81e716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8bd24c3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x000000010503c5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x00000001050361a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x00000001050370a8 0x105016000 + 135336
5 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
6 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
7 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
8 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
9 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
10 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
11 com.adobe.ag.kernel 0x000000010501a149 0x105016000 + 16713
12 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
13 com.adobe.ag.kernel 0x000000010501ff01 0x105016000 + 40705
14 com.adobe.ag.kernel 0x0000000105017f69 lua_call + 36
15 com.adobe.ag.substrate 0x0000000105193610 AgLua_callWithAutoReleasePool + 84
16 com.adobe.ag.kernel 0x000000010501fc3f 0x105016000 + 39999
17 com.adobe.ag.kernel 0x000000010502e14f 0x105016000 + 98639
18 com.adobe.ag.kernel 0x000000010501ff12 0x105016000 + 40722
19 com.adobe.ag.kernel 0x000000010501f59d 0x105016000 + 38301
20 com.adobe.ag.kernel 0x000000010502016a 0x105016000 + 41322
21 com.adobe.ag.kernel 0x0000000105017feb lua_pcall + 101
22 com.adobe.ag.substrate 0x000000010518761b 0x105175000 + 75291
23 com.apple.Foundation 0x00007fff88a9776b __NSThread__main__ + 1318
24 libsystem_pthread.dylib 0x00007fff8bd22899 _pthread_body + 138
25 libsystem_pthread.dylib 0x00007fff8bd2272a _pthread_start + 137
26 libsystem_pthread.dylib 0x00007fff8bd26fc9 thread_start + 13
Thread 26:
0 libsystem_kernel.dylib 0x00007fff8e81ee6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8bd23f08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff8bd26fb9 start_wqthread + 13
Thread 27:
0 libsystem_kernel.dylib 0x00007fff8e81ee6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8bd23f08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff8bd26fb9 start_wqthread + 13
Thread 28:
0 libsystem_kernel.dylib 0x00007fff8e81ee6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8bd23f08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff8bd26fb9 start_wqthread + 13
Thread 29:
0 libsystem_kernel.dylib 0x00007fff8e81ee6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8bd23f08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff8bd26fb9 start_wqthread + 13
Thread 30:
0 libsystem_kernel.dylib 0x00007fff8e81ee6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8bd23f08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff8bd26fb9 start_wqthread + 13
Thread 10 crashed with X86 Thread State (64-bit):
rax: 0x0008000000000000 rbx: 0x000000015904d120 rcx: 0x0000000105044ca0 rdx: 0x000000015904d120
rdi: 0x0000608011c74740 rsi: 0x00006080116435a0 rbp: 0x000000010d6321d0 rsp: 0x000000010d6321d0
r8: 0x0000000000000000 r9: 0x0000000000000003 r10: 0x0000000000000000 r11: 0x0000000000000246
r12: 0x000000000000333b r13: 0x000060000057fb08 r14: 0x0000608011c74740 r15: 0x000060000057fb08
rip: 0x000000010502be32 rfl: 0x0000000000010206 cr2: 0x0000000181aa7008
Logical CPU: 3
Error Code: 0x00000000
Trap Number: 13
Binary Images:
All 3 of my books transferred over without my having had to do anything at all. If you're worried about retaining books, you could try moving your ADE 4 to an external drive & confirming that your books are also there. I believe that the book information is saved elsewhere (separately from the ADE) and it should simply transfer over, but since I only had three books, all library items, I didn't have much to lose. All I can speak from is my own experience. I had to get rid of ADE 4 in order to successfully install ADE 2.0.
-
What is the use of maestro tool &unix in BW (production system)
Hi SAPBW guru's,
I have one query regarding .in
what is the use of maestro tool &unix in BW (production system) - my ponit is i schedule the query in SQ02 in back ground after wards i want to schedule in UNIX &Maestro tool ..
PLZZZZZZZZ,help me regarding this topic ..if any wrong on my query plzzzzz forgive me..
regards,
goodyear..Hi Good Year,
As much as I would like to help you but I think you got an <i>Off Topic</i> here. <b>Unix & Maestro Tools</b>?
I think the <b>BASIS</b> fanatics may have more idea on this.
Try this link as well...
<https://www.sdn.sap.com/sdn/search.sdn?contenttype=url&selected=0&content=/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fSDN!2fiViews!2fWCM!2fcom.sap.sdn..wcm.search.search_adv%3Fprttheme%3DCSIN&SearchPluginName=sdn_all&SelectedCustomProps=resourcetype&QueryString=MaestroTool&sourceid=Mozilla-search&query=MaestroTool>
Regards,
--Jkyle -
How to create a 'Previous History' brush tool along with content aware
Truly did not know how to create a good title here.
When you use the 'Content Aware' tool and move subject 'A' to point B what happens is that A now sits on top of B which in turn means part of the image within B may be missing and you may still want it there where it was and where it should be. You could use the 'history brush' tool to brush away part of the new insert and erase what is there to reveveal what was there. How do you do the same thing to image A which now sits on B (to reveal what was there on A originally). What I mean is this. I moved a person from point A to point B. but parts of this person are missing (his ear, his knee, his shoe) so how do I get those parts back (in the new location)?
The history brush tool appears to be erasing by subtracting, what I would like to do in this case of course is not subtract but add or 're-add'.
Thank youHello,
here's a possible solution, before using content aware, take a snapshot of A and B, then use it as your history brush source whenever you need to 're-add':
please post back if you have any questions -
Texture attributes not saving with an Art History brush tool preset.
I am sure that in the past Texture settings saved when I loaded a saved Art History Brush tool preset. But suddenly, the Texture setting - specifically Depth, is not being remembered. In other words - I have saved an Art History Brush as a Tool Preset. I have then used some other brushes and experimented with texture including the Depth setting. When I go back to the saved tool preset, the Texture Depth setting has changed to whatever it was when I last used it - not its saved value. I thought the point of Tool Presets is that they save all brush characteristics. Maybe I have got this wrong.
Help or info would be much appreciated. I'm using CS6.
...this is weird. The tool presets and their Texture attributes work fine in CS5. Maybe I need to reinstall CS6....I reinstalled CS6 and imported old preferences. The problem of reluctant attributes persisted after installation. The answer appears to have been to reset the preferences. Texture settings now behaving themselves. I should have tried this first. Oh well.
-
Hi,
Iam new to Enterprise portal.
Can anybody tel me what are the uses of portal
correct me if iam wrong " EP can be used from anywhere where the internet conncetion is available and anybody who is authorised to view the content"
Thanks in advance
SAIHi,
Your statement is correct. To be crisp, the portal offers a single point of access to SAP and non-SAP information sources, enterprise applications, information repositories, databases and services in and outside your organizationall integrated into a single user experience. It provides you the tools to manage this knowledge, to analyze and interrelate it, and to share and collaborate on the basis of it.
With its role-based content, and personalization features, the portal enables usersfrom employees and customers to partners and suppliersto focus exclusively on data relevant to daily decision-making processes
To read more visit,
http://help.sap.com/saphelp_nw04/helpdata/en/a9/76bd3b57743b09e10000000a11402f/frameset.htm
Regards
Srinivasan T -
What are the uses of diffrent concepts in data warehousing
What are the uses of diffrent concepts in data warehousing? Why?
naveenHi,
Your statement is correct. To be crisp, the portal offers a single point of access to SAP and non-SAP information sources, enterprise applications, information repositories, databases and services in and outside your organizationall integrated into a single user experience. It provides you the tools to manage this knowledge, to analyze and interrelate it, and to share and collaborate on the basis of it.
With its role-based content, and personalization features, the portal enables usersfrom employees and customers to partners and suppliersto focus exclusively on data relevant to daily decision-making processes
To read more visit,
http://help.sap.com/saphelp_nw04/helpdata/en/a9/76bd3b57743b09e10000000a11402f/frameset.htm
Regards
Srinivasan T -
What is the difference between Component,Server,Tool and Software?
HI,
What is the difference between Component,Server,Tool and Software?
SHABEERHi
Every individual part that constitutes in making an SAP System is called a COMPONENT.e.g DB instance, Java CI, ABAP CI etc
SERVER is the actual composition of different components of SAP.e.g. a database alongwith can instance would constitue an application server.
TOOLS are the products from different organisations (SAP or Non SAP) that can be used for different functionalities like keeping a check on jobs, monitoring of the system , e.g Tivoli
SOFTWARES are a kind of tool that help you to bring up results from the system in a user acceptable format. These are utilities that act as interfaces between the user and the system.
regards
Chen -
What is the use of t-code MD74 - Reorganising independant requirements
what is the use of t-code MD74 - Reorganising independant requirements
basically it to delete the unwanted PIR for the last period.
Let us say you planned PIR for 100.
At the end of Period the total salae order were 90, PIR shows 10 excess, this has to be deleted. We can do it manually, but this can be done collectively
pl go through the link below
http://help.sap.com/saphelp_47x200/helpdata/en/cb/7f9b7043b711d189410000e829fbbd/frameset.htm
With the reorganization function, you can delete planned independent requirements for which there are no sales orders in the database. You can delete the planned independent requirements history.
A key date is required to carry out reorganization which is calculated as follows: the system checks whether a reorganizing interval is maintained in Customizing for the plant that you want to reorganize. If an interval is maintained for this plant, the system uses this information to calculate the key date. If no interval is maintained for this plant, the system checks whether intervals are maintained for any other plants, and selects the largest interval to calculate the key date. You can change the key date proposed in the initial screen for reorganization.
You can change the proposed key date when deleting the history. You can set a shorter interval for deleting histories than for deleting the requirements records. -
How do I get the "File, Edit, History, Bookmarks, Tools & Help Bar to appear on my browser. I also need my "Previous Page & Next Page" arrow... and my "Start" button to appear at the bottom of my screen. I can't navigate without these.
Be sure you are not in Full Screen Mode. The F11 key will toggle Full Screen Mode on or off. If you have no Firefox toolbars, tab bar, etc., you are probably in Full Screen Mode; your Windows Taskbar (with the "Start" button) will also not be visible.
*See --> http://kb.mozillazine.org/Netbooks#Full_screen
You can choose to use the Menu Bar (''File, Edit, History bookmarks, tools & help'') or the Firefox button menu in Firefox 4 and newer versions.
*See --> https://support.mozilla.com/en-US/kb/common-questions-after-upgrading-firefox-36
The Back/Forward button (''Previous Page & Next Page" arrow'') are on the Navigation Toolbar; be sure the Navigation Toolbar is checked (to be displayed)
*See --> https://support.mozilla.org/en-US/kb/Back%20and%20forward%20or%20other%20toolbar%20items%20are%20missing
Windows Start button and Windows Taskbar:
*Be sure that "Auto-hide the taskbar" is '''''not checked''''' (if checked, moving the cursor pointer to the bottom of your monitor screen will cause it to slide up; it will disappear again when the cursor pointer is moved up from the bottom
*It is best to '''check''' "Keep the taskbar on top of other windows" so that application windows like Firefox cannot cover it.
*See --> http://windows.microsoft.com/bs-Latn-BA/windows-xp/help/keep-taskbar-visible
'''If this reply solves your problem, please click "Solved It" next to this reply when <u>signed-in</u> to the forum.'''
Not related to your question, but...
You may need to update some plug-ins. Check your plug-ins and update as necessary:
*Plug-in check --> http://www.mozilla.org/en-US/plugincheck/
*'''''Adobe Shockwave for Director Netscape plug-in''''': [https://support.mozilla.com/en-US/kb/Using%20the%20Shockwave%20plugin%20with%20Firefox#w_installing-shockwave Installing ('''''or Updating''''') the Shockwave plugin with Firefox]
*'''''Adobe PDF Plug-In For Firefox and Netscape''''': [https://support.mozilla.com/en-US/kb/Using%20the%20Adobe%20Reader%20plugin%20with%20Firefox#w_installing-and-updating-adobe-reader Installing/Updating Adobe Reader in Firefox]
*'''''Shockwave Flash''''' (Adobe Flash or Flash): [https://support.mozilla.com/en-US/kb/Managing%20the%20Flash%20plugin#w_updating-flash Updating Flash in Firefox]
*'''''Next Generation Java Plug-in for Mozilla browsers''''': [https://support.mozilla.com/en-US/kb/Using%20the%20Java%20plugin%20with%20Firefox#w_installing-or-updating-java Installing or Updating Java in Firefox] -
What is the use of at-exit in mudule pool
hi
what is the use of at-exit in mudule pool. what is the use when we keep the function type as 'E' for a function codeAT EXIT-COMMAND lets you call a module before the system executes the automatic fields checks.
Automatic field checks can be avoided through AT EXIT-COMMAND, which works exactly the same way as CANCEL works from standard tool bar. In the R/3 screen, if your want to quit the processing of that particular screen without entering the mandatory fields then user can click the CANCEL button, same functionality can be incorporated in the user defined transaction by usine AT EXIT-COMMAND. This module can be called before the system executes the automatic field checks.
Code for AT EXIT-COMMAND in flow logic and in module pool program can be written as follows.
In Flow Logic:
PROCESS AFTER INPUT.
MODULE EXIT AT EXIT-COMAND.
In Module Pool Program:
MODULE EXIT.
case okcode.
when 'EXIT'.
leave to screen 0.
ENDMODULE.
To achieve this kind of functinality, the pushbutton or menu item should be assigned a function type 'E' (Exit). It tells the system to process this particular module before carrying out any field checks.
Rewards if useful. -
What is the Use of Text Module Radio buton in Smartforms
Hi all,
What is the Use of Text Module Radio buton in Smartforms T - code ? How can we link this to our form ?
Thanks in advance
KRText modules
Text modules are used to centrally store texts that are used frequently in forms in the system.
Text modules are included in forms using texts nodes. The text node can either refer to the text module or take its text. You can then change the text or add to it to suit the form.
Text modules have the following attributes:
They are client-independent
They are connected to the transport system
They are connected to the translation tools in the system
The third attribute means that a text module can be uniquely assigned to a language using the logon language. When including a text module, you can also access translations of the text module, for example, to include an English text module in a German form.
Reward Points if useful. -
What is the use of change pointer technique in IDOC
hi
could anybody suggest me
what is the use of change pointer technique and how to use it
thank you
kalyan.Change pointers are used for changes to the master data objects are flagged for distribution by SMD Tool.i.e.shared Master Data.
You need change pointers to distribute changes with the ALE SMD tool. If you do not use this tool, you do not need to write change pointers.
You can deactivate change pointers and activate them again with the transaction BD61
The SMD tool is connected to the change document interface. If the master data changes are to be distributed, the application writes a change document. The contents of this are passed to the SMD tool. The tool writes change pointers, reads the application data and creates the master IDoc.
The master IDoc is then passed to the ALE layer, which sends it to all interested systems.
The change pointer tables (BDCP und BDCPS) should be as small as possible. Use as few change pointers as possible and delete change pointers which you no longer need.
You can increase the rate of processing by using the Analyze Change Pointer and Reorganize Change Pointer functions. -
What is the use of variant in the alv report
hello all,
what is the use of variant in the alv reportHi,
For Variants
follow the link:
http://help.sap.com/search/highlightContent.jsp
Variants allow you to save sets of input values for programs that you often start with the same selections. You can use them for any programs except subroutine pools (type S).
Contents
Variants: Overview
Initial Screen
Displaying a Variant Overview
Creating and Maintaining Variants
Creating Variants
Attributes of Variants
Changing Variants
Deleting Variants
Printing Variants
Variable Values in Variants
Creating Variables for Date Calculations
User-specific Selection Variables
Creating User-specific Variables
Changing Values Interactively
Changing Values from the Program
Fixed Values from Table TVARV
Creating Table Variables from TVARV
Changing TVARV entries
Running a Program with a Variant
Variants: Overview
Use
Whenever you start a program in which selection screens are defined, the system displays a set of input fields for database-specific and program-specific selections. To select a certain set of data, you enter an appropriate range of values.
For further information about selection screens, see Working with selection screens in the ABAP User's Guide.
If you often run the same program with the same set of selections (for example, to create a monthly statistical report), you can save the values in a selection set called a variant.
You can create any number of variants for any program in which selection screens are defined. Variants are assigned exclusively to the program for which they were created.
You can also use variants to change the appearance of the selection screen by hiding selection criteria. This is particularly useful when you are working with large selection screens on which not all of the fields are relevant.
Reports, module pools, and function groups may have several selection screens. It is therefore possible to create a variant for more than one selection screen.
Variants are an interface between the user and the selection screen. They can be used both in dialog and in background mode, although their uses are slightly different.
Variants in Dialog Mode
In dialog mode, variants make things easier for the user, since they save him or her from continually having to enter identical values. They can also make the selection screen easier to read, because you can use them to hide input fields. Running an executable program with a variant containing an optimal set of values also reduces the capacity for user error. The optimized database selections speed up the runtime of the program.
Variants in Background Mode
Variants are the only method for passing values to a report program in a background job. Therefore, when you run a program in the background, you must use a variant (or SUBMIT... VIA JOB). To avoid you having to create a new variant each time you run the report, ABAP contains a mechanism allowing you to pass variable values to variants. See variable values in variants.
To ensure that an executable program is always started using a variant, you can specify in the program attributes that the program may only be started in this way.
Features
Creation of variants
Display, change, copy, print, and delete variants
Use and definition of variables in variants
Variable date calculation
User-specific fixed values
Fixed values in table TVARV
You access the variant maintenance tool from the initial screen of the ABAP Editor. Enter the name of the program, select Variants in the Sub-objects group box, and then choose Display or Change.
Functions
The above screen allows you to:
Create variants
Display the variant directory
Display and change values and attributes
Copy, delete, and rename variants
Before creating a new variant for a program, you should check whether you can use or adapt an existing variant instead.
There are two ways to display variants:
Position the cursor on the Variant field on the initial screen and press F4. The following dialog box lists all of the available variants:
Choose Variants ® Directory on the initial screen:
Creating Variants
Prerequisites
You must have defined one or more selection screens for the relevant program. The program may have any type except type S.
Procedure
On the initial screen of the ABAP Editor, enter the name of the program for which you want to create a variant, select Variants in the Sub-objects group box, and choose Change.
On the variant maintenance initial screen, enter the name of the variant you want to create.
Note the naming convention for variants (see below).
Choose Create.
If the program has more than one selection screen, a dialog box appears in which you can assign the variant to one or more screens. The dialog box does not appear if the program only has one selection screen. In this case, the selection screen of the program appears straight away.
If there is more than one selection screen, select the screens for which you want to create the variant.
Example:
If you choose Variant for all selection screens, the variant also applies to any selection screens that you create after creating the variant.
Otherwise, the variant only supplies values to the selection screens that you select in the list.
Choose Continue.
The (first) selection screen of the program appears.
If your program has more than one selection screen, use the scroll buttons in the left-hand corner of the application toolbar to navigate between them. If you keep scrolling forwards, the Continue button appears on the last selection screen.
Enter the required selections, including multiple and dynamic selections.
Choose Continue.
Result
When you have finished, an overview screen appears (ABAP: Save Attributes of Variant), on which you can enter the attributes of your variant and save it.
Note that when you create a new variant, you must enter both values and attributes.
Names of variants: Names can consist of up to 14 alphanumeric characters. The "% " character is not allowed. If you want the variant to be transported automatically with its program, you must create a system variant. The name of a system variant starts "CUS&" for customers, and "SAP&" for SAP system variants. You can only use the "&" character within this prefix in the name of a system variant. It may not occur in any other context. System variants are administered by the Workbench Organizer. Although you can create and access variants from any client, they are always stored in client "000".
Creating Variants
Prerequisites
You must have defined one or more selection screens for the relevant program. The program may have any type except type S.
Procedure
On the initial screen of the ABAP Editor, enter the name of the program for which you want to create a variant, select Variants in the Sub-objects group box, and choose Change.
On the variant maintenance initial screen, enter the name of the variant you want to create.
Note the naming convention for variants (see below).
Choose Create.
If the program has more than one selection screen, a dialog box appears in which you can assign the variant to one or more screens. The dialog box does not appear if the program only has one selection screen. In this case, the selection screen of the program appears straight away.
If there is more than one selection screen, select the screens for which you want to create the variant.
Example:
If you choose Variant for all selection screens, the variant also applies to any selection screens that you create after creating the variant.
Otherwise, the variant only supplies values to the selection screens that you select in the list.
Choose Continue.
The (first) selection screen of the program appears.
If your program has more than one selection screen, use the scroll buttons in the left-hand corner of the application toolbar to navigate between them. If you keep scrolling forwards, the Continue button appears on the last selection screen.
Enter the required selections, including multiple and dynamic selections.
Choose Continue.
Result
When you have finished, an overview screen appears (ABAP: Save Attributes of Variant), on which you can enter the attributes of your variant and save it.
Note that when you create a new variant, you must enter both values and attributes.
Names of variants: Names can consist of up to 14 alphanumeric characters. The "% " character is not allowed. If you want the variant to be transported automatically with its program, you must create a system variant. The name of a system variant starts "CUS&" for customers, and "SAP&" for SAP system variants. You can only use the "&" character within this prefix in the name of a system variant. It may not occur in any other context. System variants are administered by the Workbench Organizer. Although you can create and access variants from any client, they are always stored in client "000".
reward all help full answers -
What is the use of guid in CRM?
Hi ,
what is the use of guid in crm.
there is nothing like this in r/3.if the data is to flow in from r/3 to crm or crm - r/3 is do we verify the guid.partner guid or product guid.
please make me understand this.
thank you,
hunGUIDs are system generated unique keys which identifies CRM objects (campaigns, sales documents, business partners, products etc.). CRM & MSA works on GUIDs. Most of the table relationships are defined on GUIDs.
Important CRM tables:
COMM_PRODUCT : Products
CRMC_T077D : customer account groups
CRMD_ORDERADM_H (for header) CRMD_ORDERADM_I (Item data)
CRMD_ORDERADM_H Business Transactions CRM
CRMD_ACTIVITY_H Activity
CRMD_OPPORT_H Opportunity
BUTOO : Customer details
BUT001 BP: General data II
BUT100 BP: Roles
BUT150 BP relationship: Attribute table (test
different
BUT_HIER_TREE Business Partner Group Hierarchy
CDBC_T_PRODUCTID Mapping: Product Id
CDBD_ORGMAN Business transaction - organizational unit -
set
COMC_PRODUCT General Product Settings
COMC_R3_FIELDS Assignment of R/3 material master fields to
CFOP
COMM_CATEGORY Category
COMM_CFGMAT Basic Data for Materials
COMM_HIERARCHY Category Hierarchy
COMP_TYPES Hierarchy Tool: Comparison Type Check
Table
CRMC_CPRICPROC Customer Pricing Procedures
SMOKVBEZ15 Assignment employees to positions
All transactions are uniquely identified by their guids internally
Transaction numbers are not unique
System calls a function module GUID_CREATE to create a unique GUID everytime you create a transaction.
Whenever you are creating some transaction programatically you will have to first create a unique GUID for the transaction by calling GUID_CREATE.
Look at What is GUID in CRM & its significance please? maybe it helps
<b>Please, Reward Points.....</b>
Maybe you are looking for
-
I have Lion installed. AirDrop does not show up in the Finder. What to do?
-
Itunes wont startup and getting exception errors
So, here I am with my brand spanking new ipod touch 4 gen and very excited, that is until.... I realise something's wrong, very wrong. I download the new version of itunes ontop of my old version, and try to start itunes and get this error: "The exce
-
"On time pick rate" logical column defined as INT instead of DOUBLE
Hi, I noticed that there is a problem with the indicator "Top 10 Plants by Pick Rate". The calculation of this formula results in a decimal number indicating the number of selections made in time in relation to the total number of selections. However
-
Hi Experts, in 2lis_04_p_arbpl datasource not having field IGMNG in both extract structure & commnication structure but backend table AFKO is having this field if can i enhance this to datasource i need to write ABAP code or not let me know this . Re
-
Problem installing OSX Mountain Lion on MacPro
Hi, i'm trying to install the new OSX on my macpro but it fails when should reboot for install... I'm starting from the latest Snow Leopard version and the MacPro isa a MacPro4,1 Quad-Core Intel Xeon 2.26Ghz. I have already installed on my macbookpro