Binary 3.0.0.44 Build does not include console app
Shouldn't the binary build include the console app?
It's included in the source download...will this eventually be in the binary build, or, will this always only be available in the source download?
thanks,
David
I guess I consider the console application to be more of a sample or optional than being required. It is included in the turnkey and in the source distros, as you've mentioned. Perhaps the best way to resolve this is to log a bug in JIRA requesting its inclusion in the bianary distro and we'll see how many votes it gets. :-)
How do you use the console? What value is it providing to you and do you have any suggestions for its improvement? Again, please log concrete suggestions in JIRA.
Thanks for your interest in BlazeDS!
Trevor
Similar Messages
-
Workshop IDE Build does not include all files
We have property files also which we want included as part of the build process
but if we use the IDE build it does not include them. We have to therefore export
the IDE build and customize it to include *.properties like this
<zip basedir="${dest.path}" zipfile="${ejb.outputJar}" encoding="UTF8"> <!-- JARs
filenames are encoded UTF8 -->
<zipfileset dir="${project.local.directory}" includes="*.properties" />
</zip>
which causes a problem for us because the exported build file is specific to a
user's local PC and cannot be used in a team environment.
How can we have the IDE build include all the files within a project i.e. include
properties files also.
Thanks
MindyHi Mindy,
Why not in EJB?
Yes there is no argument as to why property files cannot be copied over from EJB
project.
The reason is that Workshop has not implemented the feature with EJBProject. We
have that feature only for Java projects and not for EJB project.
Thanks a lot,
Vimala
"Mindy" <[email protected]> wrote:
>
You are saying the same thing again. My question is why not for EJB projects?
I know we can create the files in Java project and read them with specific
java
files to read them but WHY NOT IN EJB IS THE QUESTION?
"Carl" <[email protected]> wrote:
Feature of the EJB Project:)
"Mindy" <[email protected]> wrote in message
news:4034c351$[email protected]..
We have these property files in the EJB project, not Java project.Why
should they
not be copied if they are part of the EJB project?
"Carl" <[email protected]> wrote:
The properties file do get copied over if they are part of Java project.
Hence, we have created utility classes in Java project that read
the
property file.
For other project types, like EJB the property files didn't get copied...
"Mindy" <[email protected]> wrote in message
news:4033b944$[email protected]..
We have property files also which we want included as part of the
build
process
but if we use the IDE build it does not include them. We have to
therefore
export
the IDE build and customize it to include *.properties like this
<zip basedir="${dest.path}" zipfile="${ejb.outputJar}" encoding="UTF8"><!-- JARs
filenames are encoded UTF8 -->
<zipfileset dir="${project.local.directory}"includes="*.properties" />
</zip>
which causes a problem for us because the exported build file is
specific
to a
user's local PC and cannot be used in a team environment.
How can we have the IDE build include all the files within a projecti.e.
include
properties files also.
Thanks
Mindy -
Flex 4, exporting a Release Build does not include CSS/XML?
Hello
So I'm using external CSS and XML. I'm pulling the CSS with <fx:Style source="CSS/styles.css" /> and am using HTTPService to fetch the XML data.
It works great, until I export as a Release Build.
It doesn't include the CSS or XML files, but still pulls the CSS colors and whatnot, I just can't update them.
What gives? How can I get the CSS and XML external files to.. well, stay "external"?
I need the user to be able to update the CSS and XML on their end, but can't if the Release Build embeds the CSS and XML files before exporting..
Any help would be appreciated, thanks!dont think Flex can read a raw CSS sheet. You have to precompile them, right click on the file in project explorer and chose compile CSS to SWF
http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7f8c.html -
Default Target Main Build does not exist in this project
I am learning ant with eclipse and wanted to use ant build.xml to compile and run my class. I was getting the following error when i just tried to use ant.
Default Target Main Build does not exist in this project
package src;
public class Ch05_02 {
public static void main(String[] args) {
System.out.println("This code was built using Ant.");
<?xml version="1.0" encoding = "UTF-8"?>
<project name="Ch05_02" default="Main Build" basedir=".">
</project>Ref: http://www.javabeginner.com/Ch05_02.zip
Edited by: hemanthjava on Oct 28, 2007 5:43 AMYou gave a default target in the build.xml, and then didn't define the target.
This is an Ant question. You're better off asking Ant questions on an Ant forum. -
Compiling fmb module in Form builder does not change the fmx file
Hi,
I am using Oracle Forms Builder version 10.1.2.0.2 To edit 10g2 forms.
In the last month, it happened twice that an fmb file I edited in the forms builder did not change the fmx aftrer compilation.
namely, when I opened the fmx file in the application, I didn't see the changes, but they were present in the fmb form opened in the Form Builder.
Usually when we have the fmx file open in the application, the form builder won't let me compile it - showing the following error:
FRM-30087: Unable to create form file
When this error happens and the changes are not reflected, this error message doesn't appear even though the fmx file is open in the application.
I tried deleting the fmx file, and then opening it in the application to see if there is another copy of it.
The application gave an error 40010 - can't read form.
When I recompiled the file, the fmb didn't show any changes either, even though the file was created again in the file system.
I could not find a way to consistently reproduce this problem.
Did you ever encounter such a problem?
I noticed the edit -> preferences -> general menu has the option to "save befor building".
Does it mean the Form Builder keeps a cached copy of the fmb in memory, and when this error happens it compiles the original file system fmb file rather than the cached memory copy with the changes?
Thanks,
Eyal Azran
Configuration Management Engineer - IsracardHey Craig,
Thank you for your response.
I verified the version of the forms on the Application Server and they are the same.
This problem is quite tricky to reproduce, it happens once every few months!
(we have about 10 developers, who are developing and testing on multiple servers - so far two of the servers showed this issue)
I've determined that the reason this happens is that:
1. The compiled fmx is vied in the application.
** for some reason, the frmweb.exe process on the server does not terminate properly **
2. The developer compiles the form again in Form Builder
3. The Form Builder does not detect that the form is open in the mal-terminated process
There usually is an error message here saying the fmx module is locked - this error happens because this message is not displayed.
I will attach an image of the process monitoring tool we use ( ProceXP ) showing the ghost process that locks the fmx module.
<edit>oops, I guess I can't attach the image- I can e-mail it if you'd like</edit>
If anyone has an idea for a solution, this will help immensely.
Eyal
Edited by: Hey_Al on 06:04 06/05/2010 -
Interface Builder does not open when I click Mainwindow.xib file on Monotouch.
I did a lot research about it, What the most of view say it is because of the iOS SDK, not because of the MonoTouch, they say that iOS SDK provides the Interface Builder? Any suggestions? Thanks in advance. iOS SDK Version 4.3.
Does Monotouch work within Xcode? I'm not sure what it is. If so then Interface Builder does not open a separate window in Xcode 4. When you first go to your .xib, you must select your "Window" to see the window. Otherwise you get an empty grid. Here's an image with the "Window" selected. I have it set for Mac applications not iOS but what you have should look similar.
-
Folio Builder does not support proxy authorisation on the mac.
Folio Builder does not support proxy authorisation on the mac.
Which’s solution to connect ?It does not work because the Folio Builder tries to connect to the proxy as "anonymous". I don't know any solution up to now... Anyone?
-
Applet does not load on app server when Free Design Layout
Hi,
I have to embed a an applet in a webpage of an web application. Before I go on to anything.. let me first tell you, I am using Netbeans 6.0
As shown in the tuorial:
[http://www.netbeans.org/kb/articles/tutorial-applets-40.html]
1. I first made the "Applet" source say HelloApplet. java. After compiling and running it I get the HelloApplet.jar.
2. I created a WebApplication and then from the properties -> packaging -> I "Add Project" HelloApplet.jar.
3. Then I a webpage I "embeded" the applet.
4. I run the web app and the applet gets loaded and everything is just fine.
But before I go on I must tell you that the applet was designed in Null Layout. Now I edited the applet source once again and changed the layout to Free Design Layout*. ( this is available from Netbeans..on the HelloApplet.java .. go to the design view.. right click on the form and from the context menu you can change the layout to FreeDesign or whatever you might want).
When I expand the "Libraries" node I see the that the library Swing Layout Extensions - swing-layout-1.0.3.jar has been added.
When I "run" the "HelloApplet.java" file, the applet is shown in the appletviewer. No problems with that.
But!
When I try to Clean & Build and Run the WebApplication, the applet does not get loaded. On inspecting the java console I see the following error:
java.lang.NoClassDefFoundError: org/jdesktop/layout/GroupLayout$Group
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
at java.lang.Class.getConstructor0(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at sun.applet.AppletPanel.createApplet(Unknown Source)
at sun.plugin.AppletViewer.createApplet(Unknown Source)
at sun.applet.AppletPanel.runLoader(Unknown Source)
at sun.applet.AppletPanel.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: org.jdesktop.layout.GroupLayout$Group
at sun.applet.AppletClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.applet.AppletClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
... 10 moreIt clearly shows that the Free Design Layout has something to do with the GroupLayout which can be found by expanding the "Swing Layout Extensions - swing-layout-1.0.3.jar". Now when the HelloApplet.jar is created only the HelloApplet.class file gets included together with some other data but NOT the swing extensions. Hence when I run the web app the class file looks for the GroupLayout.class definition but can find it in the jar as its not included when the HelloApplet.jar is created.
But with null layout there isint a problem because null layout takes the definitions from the JRE on the machine.. and so it runs without a hitch.
My Question is : How can I run the applet with Free Design Layout? or is it possible to package the swing layout extensions in the HelloApplet.jar?<</u>
Thanks for all your replies.
Cheers.
Edited by: arijit_datta on May 15, 2008 4:07 PMSolved.
Here is the solution:
[http://www.nabble.com/Applet-does-not-load-on-app-server-when-Free-Design-Layout-to17259115.html|http://www.nabble.com/Applet-does-not-load-on-app-server-when-Free-Design-Layout-to17259115.html]
Cheers..
Edited by: arijit_datta on May 16, 2008 7:41 AM -
EJB project IDE build dos not include properties files
We have property files also which we want included as part of the build process
for EJB projects but if we use the IDE build it does not include them. We have
to therefore export the IDE build and customize it to include *.properties like
this
<zip basedir="${dest.path}" zipfile="${ejb.outputJar}" encoding="UTF8"> <!-- JARs
filenames are encoded UTF8 --> <zipfileset dir="${project.local.directory}" includes="*.properties"
/> </zip>
which causes a problem for us because the exported build file is specific to a
user's local PC and cannot be used in a team environment.
How can we have the IDE build include all the files within an EJB project i.e.
include properties files also.Hey Jamie,
Currently there is no support to include other .properties files into
the internal build. There's a build.properties that you get as part of
an EJB project which you could place your values into and use that as
your template for your team based development and check that into your
source control.
If you'd really like to get gross and hack Workshop a little bit you
could modify the default EJB project template to use your .properties
file for every EJB project you create. This would then splat a copy of
your .properties file into the root of the EJB project.
To do that you'd go to {your BEAHOME}\workshop\templates and crack open
the ejb-project.zip template zip file and merge your settings into the
existing build.properties file. This has the same
effect as replacing the .properties file after you've created your
project only it keeps you from having to perform that step each time.
The downside of this is that each person on your team would then have to
update that template zip file in their workshop installation. (I'd make
sure to backup the original template file before performing this
activity so you can always go back to the original template).
Hope this helps,
-Michael
Jamie wrote:
We have property files also which we want included as part of the build process
for EJB projects but if we use the IDE build it does not include them. We have
to therefore export the IDE build and customize it to include *.properties like
this
<zip basedir="${dest.path}" zipfile="${ejb.outputJar}" encoding="UTF8"> <!-- JARs
filenames are encoded UTF8 --> <zipfileset dir="${project.local.directory}" includes="*.properties"
/> </zip>
which causes a problem for us because the exported build file is specific to a
user's local PC and cannot be used in a team environment.
How can we have the IDE build include all the files within an EJB project i.e.
include properties files also. -
FB4 Beta2 does not include swz files
When compiling a release Build, FB4 does not include the smaller swz files but bigger swf files (e. g. framework_4.0.0.10945.swf) instead. The swz files where included only a few time at the beginning of the project.
I need to finish this project with the 4.0.0.10945 SDK.
How can I let FB4 Beta 2 include and link to the framework etc. swz files?
Thanks,
DavidHi,
For the moment I would suggest that you use 'merge into code' rather than runtime libraries. After flashbuilder is released I would assume that the runtime libraries will be available online through Adobe, then it makes sense for applications that are used on a regular basis to use cached libraries, right now everytime you change a build you will also have a new set of libraries to upload/download, along with issues of libraries getting mixed up. SO rather than having to be concerend about a bunch of libraries being stored in the flashplayer cache you only have a single swf to think about.
David. -
Simulate Acquisition does not include new image file created after first call
For example, I have 5 images in a folder.
I call Simulate Acquisition.
It cycles through all 5 images.
Now If I include 1 more image it does not include this image in the "cycle". I need to reload this step by clicking Main\path\browse button and select any image in the folder and then it cycles through all 6 images.
Is there anyway to automatically include new images added to the folder after the step has been created?
Thanks.
CVI 2010
LabVIEW 2011 SP1
Vision Builder AI 2011 SP1Here's a sample inspection and VI to illustrate how you could do this. I used an image variable and passed this into the Run LV step so the VI could read the file and update the image variable and then I used the Select Image step to get the image variable into the VBAI script so you can process it. I also added a delete option in the VI so you can delete the previous image when you read the next available image. Make sure to go to the Setup State and initialize the path variable to where your image files will live (to access the Setup State, go to View>>View Complete Inspection and select on the Setup option on the left hand side. I initialized it to c:\Image Folder
Hope this helps,
Brad
Attachments:
Read Dynamic Image File.zip 15 KB -
I see that OSX Lion does not include iPhoto; if I upgrade from Snow Leopard will I lose iPhoto9?
I see that OSX Lion does not include iPhoto; if I upgrade from Snow Leopard will I lose iPhoto9?
I migrated my SnowLeopard data to Lion, but cannot open iPhoto. When launched iPhoto tried to upgrade the database but crashes every time. Here's the log:
Process: iPhoto [71868]
Path: /Applications/iPhoto.app/Contents/MacOS/iPhoto
Identifier: com.apple.iPhoto
Version: 9.1.5 (9.1.5)
Build Info: iPhotoProject-6150000~1
Code Type: X86 (Native)
Parent Process: launchd [256]
Date/Time: 2011-09-30 17:07:17.079 -0700
OS Version: Mac OS X 10.7.1 (11B26)
Report Version: 9
Interval Since Last Report: 305820 sec
Crashes Since Last Report: 1
Per-App Interval Since Last Report: 131 sec
Per-App Crashes Since Last Report: 1
Anonymous UUID: 80B76B3A-F25B-4806-AD10-7EF551769BD0
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x000000000000000b
VM Regions Near 0xb:
--> __PAGEZERO 0000000000000000-0000000000001000 [ 4K] ---/--- SM=NUL /Applications/iPhoto.app/Contents/MacOS/iPhoto
__TEXT 0000000000001000-0000000000f00000 [ 15.0M] r-x/rwx SM=COW /Applications/iPhoto.app/Contents/MacOS/iPhoto
Application Specific Information:
objc[71868]: garbage collection is OFF
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.CoreFoundation 0x91d40e5a __CFCopyFormattingDescription + 26
1 com.apple.CoreFoundation 0x91d3c392 __CFStringAppendFormatCore + 12258
2 com.apple.CoreFoundation 0x91d3920b CFStringCreateWithFormatAndArguments + 107
3 MetadataLib.dylib 0x97b6667a readRawTiffPropsFromPath + 161264
4 MetadataLib.dylib 0x97b4c102 readRawTiffPropsFromPath + 53368
5 MetadataLib.dylib 0x97b4c2e1 readRawTiffPropsFromPath + 53847
6 MetadataLib.dylib 0x97b3ec2c readRawTiffProps + 11836
7 MetadataLib.dylib 0x97b3ec62 readRawTiffProps + 11890
8 MetadataLib.dylib 0x97b73572 readRawTiffPropsFromPath + 214248
9 MetadataLib.dylib 0x97b3bc25 readMakerNoteProps + 137
10 com.apple.ImageIO.framework 0x9bab1733 readProps + 2870
11 com.apple.ImageIO.framework 0x9bab1489 readProps + 2188
12 com.apple.ImageIO.framework 0x9bad7e8c readTiffPropsFromData + 228
13 com.apple.ImageIO.framework 0x9baa248c readExifData + 94
14 com.apple.ImageIO.framework 0x9baa017a initImageJPEG + 4372
15 com.apple.ImageIO.framework 0x9ba9f03d _CGImagePluginInitJPEG + 89
16 com.apple.ImageIO.framework 0x9ba9e798 makeImagePlus + 768
17 com.apple.ImageIO.framework 0x9baa8bcf _CGImageSourceGetPropertiesAtIndexInternal + 57
18 com.apple.ImageIO.framework 0x9baa8b63 CGImageSourceCopyPropertiesAtIndex + 134
19 com.apple.RedRock 0x01d19312 -[RKMetadata initWithPath:cgImageSource:imageIOMethodVersion:includeFileAttributes:includeRa w:sidecarFile:movie:] + 434
20 com.apple.RedRock 0x01d19157 -[RKMetadata initWithPath:imageIOMethodVersion:includeRaw:sidecarFile:] + 87
21 com.apple.RedRock 0x01dbba61 -[RKMetadata initWithPath:] + 65
22 com.apple.iPhoto 0x0024f89f 0x1000 + 2418847
23 com.apple.iPhoto 0x0003a809 0x1000 + 235529
24 com.apple.iPhoto 0x000357e6 0x1000 + 215014
25 com.apple.iPhoto 0x00034796 0x1000 + 210838
26 com.apple.iPhoto 0x0003244b 0x1000 + 201803
27 com.apple.iPhoto 0x000320f9 0x1000 + 200953
28 com.apple.iPhoto 0x00031a03 0x1000 + 199171
29 com.apple.iPhoto 0x0002fa2e 0x1000 + 191022
30 com.apple.Foundation 0x924deebe __NSFireDelayedPerform + 615
31 com.apple.CoreFoundation 0x91d92256 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 22
32 com.apple.CoreFoundation 0x91d91be7 __CFRunLoopDoTimer + 743
33 com.apple.CoreFoundation 0x91d70ce0 __CFRunLoopRun + 1888
34 com.apple.CoreFoundation 0x91d701ec CFRunLoopRunSpecific + 332
35 com.apple.CoreFoundation 0x91d70098 CFRunLoopRunInMode + 120
36 com.apple.HIToolbox 0x981fd487 RunCurrentEventLoopInMode + 318
37 com.apple.HIToolbox 0x98204cee ReceiveNextEventCommon + 168
38 com.apple.HIToolbox 0x98204c32 BlockUntilNextEventMatchingListInMode + 88
39 com.apple.AppKit 0x9bcd08ec _DPSNextEvent + 678
40 com.apple.AppKit 0x9bcd0159 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113
41 com.apple.AppKit 0x9bccc4cb -[NSApplication run] + 904
42 com.apple.AppKit 0x9bf5fb54 NSApplicationMain + 1054
43 com.apple.iPhoto 0x0000f092 0x1000 + 57490
44 com.apple.iPhoto 0x0000ec65 0x1000 + 56421
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libdispatch.dylib 0x9b1e1397 _dispatch_source_set_timer3 + 18
1 libdispatch.dylib 0x9b1dc80b _dispatch_queue_drain + 224
2 libdispatch.dylib 0x9b1dc8e6 _dispatch_mgr_thread2 + 43
3 libdispatch.dylib 0x9b1dcac5 _dispatch_mgr_invoke + 450
4 libdispatch.dylib 0x9b1db71b _dispatch_mgr_thread + 53
Thread 2:
0 com.apple.Foundation 0x92502b47 CFBasicHashFindBucket + 172
1 com.apple.Foundation 0x92502a86 -[NSClassicMapTable objectForKey:] + 34
2 com.apple.Foundation 0x92502a5d NSMapGet + 86
3 com.apple.proxtcore 0x016e519b -[XTDistributor subscriptionsForMessage:] + 75
4 com.apple.proxtcore 0x016e5117 -[XTDistributor newSubscribersListForMessage:] + 119
5 com.apple.proxtcore 0x016e4da9 -[XTDistributor distributeMessage:] + 201
6 com.apple.proxtcore 0x016e47a4 -[XTMessageHub handleMessage:] + 100
7 com.apple.proxtcore 0x016e3266 -[XTThread run:] + 422
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 3:
0 libsystem_kernel.dylib 0x94b6cc22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x94b6c1f6 mach_msg + 70
2 com.apple.CoreFoundation 0x91d679ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x91d70b14 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x91d701ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x91d70098 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x924debdb -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273
7 com.apple.proxtcore 0x016e56a5 -[XTRunLoopThread run:] + 453
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 4:
0 libsystem_kernel.dylib 0x94b6cc22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x94b6c1f6 mach_msg + 70
2 com.apple.CoreFoundation 0x91d679ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x91d70b14 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x91d701ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x91d70098 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x924debdb -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273
7 com.apple.proxtcore 0x016e56a5 -[XTRunLoopThread run:] + 453
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 5:: com.apple.appkit-heartbeat
0 libsystem_kernel.dylib 0x94b6ebb2 __semwait_signal + 10
1 libsystem_c.dylib 0x970337b9 nanosleep$UNIX2003 + 187
2 libsystem_c.dylib 0x97033558 usleep$UNIX2003 + 60
3 com.apple.AppKit 0x9bf16f84 -[NSUIHeartBeat _heartBeatThread:] + 2399
4 com.apple.Foundation 0x925325ed -[NSThread main] + 45
5 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
6 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
7 libsystem_c.dylib 0x970826de thread_start + 34
Thread 6:
0 libsystem_kernel.dylib 0x94b6e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97082e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97082f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x92564b77 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9252af9a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9252ae6e -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x016e446f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x016e3250 -[XTThread run:] + 400
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 7:
0 libsystem_kernel.dylib 0x94b6e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97082e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97082f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x92564b77 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9252af9a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9252ae6e -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x016e446f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x016e3250 -[XTThread run:] + 400
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 8:
0 libsystem_kernel.dylib 0x94b6e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97082e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97082f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x92564b77 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9252af9a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9252ae6e -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x016e446f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x016e3250 -[XTThread run:] + 400
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 9:
0 libsystem_kernel.dylib 0x94b6e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97082e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97082f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x92564b77 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9252af9a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9252ae6e -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x016e446f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x016e3250 -[XTThread run:] + 400
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 10:
0 libsystem_kernel.dylib 0x94b6cc22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x94b6c1f6 mach_msg + 70
2 com.apple.CoreFoundation 0x91d679ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x91d70b14 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x91d701ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x91d70098 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x924debdb -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273
7 com.apple.proxtcore 0x016e56a5 -[XTRunLoopThread run:] + 453
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 11:
0 libsystem_kernel.dylib 0x94b6e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97082e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97082f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x92564b77 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9252af9a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9252ae6e -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x016e446f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x016e3250 -[XTThread run:] + 400
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 12:
0 libsystem_kernel.dylib 0x94b6e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97082e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97082f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x92564b77 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9252af9a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9252ae6e -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x016e446f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x016e3250 -[XTThread run:] + 400
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 13:
0 libsystem_kernel.dylib 0x94b6e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97082e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97082f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x92564b77 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9252af9a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9252ae6e -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x016e446f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x016e3250 -[XTThread run:] + 400
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 14:
0 libsystem_kernel.dylib 0x94b6e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97082e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97082f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x92564b77 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9252af9a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9252ae6e -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x016e446f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x016e3250 -[XTThread run:] + 400
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 15:
0 libsystem_kernel.dylib 0x94b6e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97082e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97082f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x92564b77 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9252af9a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9252ae6e -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x016e446f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x016e3250 -[XTThread run:] + 400
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 16:
0 libsystem_kernel.dylib 0x94b6e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97082e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97082f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x92564b77 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9252af9a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9252ae6e -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x016e446f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x016e3250 -[XTThread run:] + 400
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 17:
0 libsystem_kernel.dylib 0x94b6e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97082e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97082f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x92564b77 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9252af9a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9252ae6e -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x016e446f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x016e3250 -[XTThread run:] + 400
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 18:
0 libsystem_kernel.dylib 0x94b6e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97082e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97082f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x92564b77 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9252af9a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9252ae6e -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x016e446f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x016e3250 -[XTThread run:] + 400
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 19:
0 libsystem_kernel.dylib 0x94b6e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97082e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97082f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x92564b77 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9252af9a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9252ae6e -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x016e446f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x016e3250 -[XTThread run:] + 400
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 20:
0 libsystem_kernel.dylib 0x94b6e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97082e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97082f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x92564b77 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9252af9a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9252ae6e -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x016e446f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x016e3250 -[XTThread run:] + 400
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 21:
0 libsystem_kernel.dylib 0x94b6e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97082e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97082f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x92564b77 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9252af9a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9252ae6e -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x016e446f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x016e3250 -[XTThread run:] + 400
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 22:
0 libsystem_kernel.dylib 0x94b6e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x97082e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x97082f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x92564b77 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9252af9a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9252ae6e -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x016e446f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x016e3250 -[XTThread run:] + 400
8 com.apple.Foundation 0x925325ed -[NSThread main] + 45
9 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
11 libsystem_c.dylib 0x970826de thread_start + 34
Thread 23:: com.apple.NSURLConnectionLoader
0 libsystem_kernel.dylib 0x94b6cc22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x94b6c1f6 mach_msg + 70
2 com.apple.CoreFoundation 0x91d679ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x91d70b14 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x91d701ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x91d70098 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9253e88c +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 378
7 com.apple.Foundation 0x925325ed -[NSThread main] + 45
8 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
9 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
10 libsystem_c.dylib 0x970826de thread_start + 34
Thread 24:
0 libsystem_kernel.dylib 0x94b6cc22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x94b6c1f6 mach_msg + 70
2 com.apple.iLifeSQLAccess 0x017bb5d1 -[RALatchTrigger wait] + 81
3 com.apple.iLifeSQLAccess 0x017bb4c6 -[RAOperationQueueImpl _workThread] + 358
4 com.apple.Foundation 0x925325ed -[NSThread main] + 45
5 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
6 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
7 libsystem_c.dylib 0x970826de thread_start + 34
Thread 25:
0 libsystem_kernel.dylib 0x94b6cc22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x94b6c1f6 mach_msg + 70
2 com.apple.iLifeSQLAccess 0x017bb5d1 -[RALatchTrigger wait] + 81
3 com.apple.iLifeSQLAccess 0x017bb4c6 -[RAOperationQueueImpl _workThread] + 358
4 com.apple.Foundation 0x925325ed -[NSThread main] + 45
5 com.apple.Foundation 0x9253259d __NSThread__main__ + 1582
6 libsystem_c.dylib 0x9707eed9 _pthread_start + 335
7 libsystem_c.dylib 0x970826de thread_start + 34
Thread 26:
0 libsystem_kernel.dylib 0x94b6e83e __psynch_cvwait + 10 -
when the apple review team review our app，they point out that our app uses a background mode but does not include functionality that requires that mode to run persistently。but in fact，when the app in background ，the app need data update to make the function of trajectory replay come ture。in fact， we have added function when the app is in background mode。we have point out the point to them by email。but they still have question on the background mode，we are confused，does anyone can help me，i still don't know why do review team can't find the data update when the app is in background and how do i modify the app，or what is the really problem they refered，do i misunderstand them？
the blow is the content of the review team email：
We found that your app uses a background mode but does not include functionality that requires that mode to run persistently. This behavior is not in compliance with the App Store Review Guidelines.
We noticed your app declares support for location in the UIBackgroundModes key in your Info.plist but does not include features that require persistent location.
It would be appropriate to add features that require persistent use of real-time location updates while the app is in the background or remove the "location" setting from the UIBackgroundModes key. If your application does not require persistent, real-time location updates, we recommend using the significant-change location service or the region monitoring location service.
For more information on these options, please see the "Starting the Significant-Change Location Service" and "Monitoring Shape-Based Regions" sections in the Location Awareness Programming Guide.
If you choose to add features that use the Location Background Mode, please include the following battery use disclaimer in your Application Description:
"Continued use of GPS running in the background can dramatically decrease battery life."
Additionally, at your earliest opportunity, please review the following question/s and provide as detailed information as you can in response. The more information you can provide upfront, the sooner we can complete your review.
We are unable to access the app in use in "http://www.wayding.com/waydingweb/article/12/139". Please provide us a valid demo video to show your app in use.
For discrete code-level questions, you may wish to consult with Apple Developer Technical Support. When the DTS engineer follows up with you, please be ready to provide:
- complete details of your rejection issue(s)
- screenshots
- steps to reproduce the issue(s)
- symbolicated crash logs - if your issue results in a crash log
If you have difficulty reproducing a reported issue, please try testing the workflow as described in <https://developer.apple.com/library/ios/qa/qa1764/>Technical Q&A QA1764: How to reproduce a crash or bug that only App Review or users are seeing.Unfortunately, these forums here are all user to user; you might try the developer forums or get in touch with the team that you are working with.
-
Material document 4900000006 does not include an accounting document
Hi guys
I created normal sales order, delivery and and released it thr VF01.
Then I created the RE document without order reference and PGR. But while checking the accounting documents in VL02N it gives the error as follows
Material document 4900000006 does not include an accounting document
Diagnosis
The system cannot find an accounting document for the material document 4900000006.
Possible reasons for this are:
The goods movement has no relevance to accounting. Therefore, the system did not generate an accounting document for the material document.
The material document is a document that was posted before Release 2.1. Such documents must be converted so that the system can find the relevant accounting document.
The procedure for the subsequent calculation of value is not active in your system. For further information, refer to the documentation on the program for valuating goods movements: RM07MWBU.
Procedure
Choose Continue and then choose another function.
Find out when the material document was created. If the document was created prior to the Release changeover, ask your system administrator to carry out the conversion of the documents. The individual steps required for document conversion are described in the Release Notes for Release 2.1B
Please give me the solution
Thanks in advance
RahulHi Rahul,
Can you tell me how did you resolve this error indetail or step by step? I have a same error in test client. I am doing returns with stock catergory of E while PGI and then it throws error message.
Material document 4900000006 does not include an accounting document
Diagnosis
The system cannot find an accounting document for the material document 4900000006.
Possible reasons for this are:
The goods movement has no relevance to accounting. Therefore, the system did not generate an accounting document for the material document.
The material document is a document that was posted before Release 2.1. Such documents must be converted so that the system can find the relevant accounting document.
The procedure for the subsequent calculation of value is not active in your system. For further information, refer to the documentation on the program for valuating goods movements: RM07MWBU.
Procedure
Choose Continue and then choose another function.
Find out when the material document was created. If the document was created prior to the Release changeover, ask your system administrator to carry out the conversion of the documents. The individual steps required for document conversion are described in the Release Notes for Release 2.1B
regards
rc gopi -
The content menu in my Acrobat X Standard does not include the "multimedia" selection??
What am I missing? The Adobe Classroom In A Book clearly refers to it...
Hi,
I am sorry to hear that you're having trouble in locating 'Multimedia' tools in Acrobat.
Acrobat X Standard does not include most of the interactive object tools. You need to use Acrobat X Pro for those features. Kindly check the comparison matrix at:
http://www.adobe.com/products/acrobat/matrix.html
~Sandeep V.
Maybe you are looking for
-
Why is the back ground image like this? is it supposed to be blurred? I've tried almost everything to change it but never comes out right.
-
ITunes not playing songs from iCloud in Match
I keep 50% of my music library on an external HD. I subscribed to iTunes Match to be able to access my entire library when my HD isn't available (traveling, HD in sleep mode, etc.). But iTunes won't play any songs that are stored on my external HD wh
-
Hi All, Hope there should be some real good experts here. I have been posting in this forum for the past one week to get a solution for my requirement, but unfortunately I have not found any. I have referred to some documents and have created a singl
-
Does anyone know how to fix keynote when it won't start up?
-
Dear Friend , Presently one of our client has three plants and they are taking all finished product to one account . They will sell to directly from there . Now they want to maintain sales profit / sales revenue of each plant wise and product wise .