#target photoshop doesn't find Photoshop CC - target

I installed Photoshop CC 2015 on my Mac airbook with the result that my javascripts for photoshop show an error message 'app.bringToFront is not a function'.
The scripts start with:
target photoshop
app.bringToFront()
On my iMac the scripts are running without any problem in Phoroshop CC.
Does anybody have an idea what's wrong on my laptop/library/application support?
$.writeln(app) returns 'ExtendScript Toolkit'.
Thanks for any help
Hans

How do you run your scripts? If you're running those from ESTK, change the target app from ESTK to PS. If you're running them from File menu, you don't need to target photoshop in the script

Related

Intel XDK iOS build produce zero sized ipa files

I'm trying to make this build system to work.. I've managed to create and build several projects, everything is cool all the way from building to running on the iPhone. But at some point today, the XDK started to produce zero sized ipa files and the links it sends by email to download the binaries are broken. No errors, no warnings. The android files are produced fine and downloadable, yet iOS files are zero sized. But it was OK just few minutes ago, nothing changed on my side..
Kind of show stopper to me. Does anyone use Intel XDK for practical things? How stable is it?
There was a problem with the build system that has been resolved.

Exporting Release Build FlashBuilder 4.7

I have a Action script Mobile Project and I want to export a Release Build. Debug build works perfect, however when I select Export Release Build it hangs at 0 percent even after 24 hours. I have tried restarting, updating JAVA home variable and I don't know what else to do. I might uninstall flash builder and do a fresh install but I wasn't sure if anybody else has seen this?
Problem Solved and the game has been published!
You cannot have an actionscript file with more than 30,000 lines of code....rookie mistake
changing it to 10 files with 3,000 worked like a charm.

Error Building MonoDevelop Project - Your .NET Runtime does not support '-win32icon'

I'm getting the following build error when trying to build a sample project using MonoDevelop:
Error CS8088: Your .NET Runtime does not support `-win32icon'. Please use the latest Mono runtime instead. (CS8088)
The only thing I've done is create a new, empty project and added some PNG files as the App Icons and Spotlight & Settings Icons. I know that the error is related to these icons in some way, but I can't find any reference to this particular issue. The PNG files were created from an EPS file using GIMP.
My system information is as follows:
MonoDevelop 3.0.3.2
NET Runtime => Mono 2.10.9 (Default)
uname -a => Darwin unknown406c8f2c1099 11.4.0 Darwin Kernel Version 11.4.0: Mon Apr 9 19:32:15 PDT 2012; root:xnu-1699.26.8~1/RELEASE_X86_64 x86_64
It looks like you set a Win32 exe icon in your project options. It looks like the MonoTouch C# compiler has been modified to such icons, since they would be completely redundant on iOS. It should really be removed from the project options UI too, so it doesn't get set accidentally.
To fix the error, clear the "Win32 icon" field from the Build->General section in the Project Options.

Blackberry older simulator

my client wants me to make an application which works on pre4.0 os... i understand that if i make 1 like that then it wont work on the latest os...
But my actual problem is that though i did the coding correctly coz the application was just a simple WebIcon... i cant load it onto the 7290 simulator...
i tried javaloader -u load MyApp.jad and javaloader -u load MyApp.cod... but i get the following error
Error: unable to open port...
earlier it couldnt find javac... so i placed javac in the System32 folder... now the below shown error is displayed and further the simulator doesnt connect with even the 4.0 IDE....
even tried compiling in the 4.0 IDE itself... but i get the following error...
Error!: Error: java compiler failed: javac -source 1.3 -target 1.1 -g -O -d MyDir
Don know wat to do... plz help...
screenshot of the simulator...
alt text http://www.freeimagehosting.net/uploads/d9e1840ce0.jpg
Well friends at last i tried uploading the applications .cod and .jad along with the optional .jar onto my company's server... and guess wat... it did download using the jar file but after trying all the techniques mentioned here... i guessed this was it...
But the application though gets listed in the applications but doesnt show up on the menu... and neither does it run in anyway...
Hence im closing with the research here... thanx a lot guys...
I load my programs doing the following:
(Note: This is on an Curve 8310--which has a memory card slot--not sure if you can plug in the phone and use it in HardDisk mode)
Plug the phone into the computer to enable HD mode
Copy the .jad, .jar and .cod to the memory card (or device memory in your case if HD mode works for this) of the phone
Click the Media Icon
Open the menu within media and hit explore (Here I have an option for memory card OR device memory) -- Select the device memory
Finally, find and select the .jad file -- the phone will ask if you want to download--just hit yes, and this will prompt for the install
Again, I realize this is a different (older) phone which you are using, so this method may not work.
Hope it helps!
Greg

Application not getting deployed on Blackberry simulator

I am tried deploying .cod,.alx.jar files on blackberry simulator 8100;the application is not getting deployed on phone.I am using Blackberry plugin for Eclipse.
How can I solve this issue?
Please help
Update
Hi,
Thanks for your reply.
I am trying to run the application the way you suggested.
Do I need to setup new run configuration every time I run any project?
What should be default value for build configuration ? [Debug,Private,or Release]
Copying the .cod files into the simulator's directory (where all the other .cod files are) and restarting the simulator will work.
Probably though you want to automatically deploy from Eclipse. If this isn't working for you, there are a couple of things to check:
Check that the project has been activated for BlackBerry - from the right-click menu for the project, make sure that Activate For BlackBerry is checked.
If that's already checked (as it is by default when you create a new BB project), then sometimes explicitly building the project will do the trick: From the Project menu, choose Build Active BlackBerry Simulation
EDIT: In response to some comments below I thought of something else. The configuration you choose may have something to do with your problems (BlackBerry -> Build Configurations). The configuration in the JDE Plug-in doesn't affect the code generated, but it does affect which projects are activated for BlackBerry. If you switch configurations, your project may become un-activated.
Since it doesn't affect the code, I usually just pick one configuration and stick with it throughout debugging and release.
You might be missing 'jar' in your PATH. If so, the eclipse BB plugin silently fails and your application won't be pushed to your simulator plugin directory. To see this failure within eclipse, choose 'Project > Build Active BlackBerry Simulation'.
If you don't have jar in your path, then you will see:
I/O Error: Cannot run program "jar": CreateProcess error=2, The system cannot find the file specified rapc executed for the project
So, if your JDK is here:
C:\Sun\SDK\jdk\bin
Then append it to your system environment's PATH variable, then re-run 'Build Active BlackBerry Simulation' and you should see:
rapc executed for the project [YOUR PROJECT]
Here are a couple of ideas:
1) If you have any build errors then the application won't deploy to the Simulator. The Eclipse compiler (that underlines compile errors in red) is different to the "rapc" one that creates the binary for the Simulator. I have heard of situations where the Eclipse build seems to work, but the rapc compile fails - check the Console for the detailed rapc output (this might not look like a normal Eclipse build error).
2) In the Eclipse menu, open BlackBerry -> Configure BlackBerry Workspace.
Under BlackBerry JDE choose Code Signing and make sure the three RIM checkboxes are selected. I had compile errors when these weren't selected.
Under BlackBerry JDE choose Installed Components. Choose to use the Component Package 4.7.0 as I have heard of problems with the 4.5.0 Simulator.
You should delete all these extra answers you posted, or you might get downvotes - they should be comments instead of answers.
Check if your simulator is set up to clean the file system / configuration before launching the simulator. Simulators can be set up like this. If you deactivate it, the application should not disappear.
For future readers, there is another possibility for this issue. Check your workbench project directory (folder) for a ProjectName.err file. This may provide a clue as to why your build is silently failing and thus not deploying. In my case, it was an "Error!907", a new icon I added to my project was too big. There was absolutely no other indications in Eclipse 3.4.1 that there was a problem in my build.
Just ran through the same kind of problem : project compiled fine but didn't deploy on any device or on any simulator, even though the debugger said it was attached !
The problem came from a .zip file that was located in the ./src directory of the project, deleting or moving it somewhere else resolved this case.
I wish I hadn't spend 2+ hours on such a stupid problem :/
I know this is old, but you have to do the "generate ALX" option from right clicking the project menu as well or it won't deploy, at least it doesn't for me.
I ran into the same problem again and none of answers posted here worked for me.
I played around and finally made it work. The problem was that the output file name contained a hyphen ('-'). Changing this name in the Build section of BlackBerry app descriptor did the trick.
I mean, how stupid a developer must be to slip that kind of bug. No error reported and why reject the names with hyphens in the first place? Give me back my two hours RIM "developers"!
I had the same problem. The reason was using 'ΓΌ' character in the title.
I have been facing this problem today, but with a MIDlet project. It turned out to be that I forgot to specify the "Name of main MIDlet class" in the BlackBerry Application Descriptor (BlackBerry_App_Descriptor.xml). Once I specified it the application appeared on the simulator correctly.

Resources