I am trying to integrate Finder Sync Extension in my Cocoa Application to show badge in files and folders. But i faced some query:
1) Problem of to run the application means i want to run extension using my host application. Refer the below screen shots of that:
See the run pop-up menu, If i run app through FinderSyncExtension then it is added to Extension in System Preference but when i run my app through my host app like see blue menu item then it won't create extension.
2) FinderSync.m class is called only first time then it won't call so what is the issue of that?
Please give me brief idea related to integrate the FinderSync Extension.
And I refered the Apple official document of FinderSync.
Any help is appreciated..!
1.On developing you can run FinderSync extension by selecting "FinderSyncExt" from product-->Scheme. In my knowledge there is no direct connection between containing app and extension.
To stop your running Extension use "Stop" option from Product instead of button given to stop running application.On running a extension it initialise two process so to stop you have to press "Stop" twice(from product).
And before you run Extension in Xcode make sure that your extension is unchecked from extensions list(System preference--> Extensions).
Hope it will help you.
Related
I Just installed Ranorex studio trial version 8.3.0. While I was going through tutorial trying to learn it, I encountered a problem. After creating new solution when I try to record test, it's just start recording. It doesn't give option to select run an application or open a browser to provide specific path or URL.
I have tried a lot but it's the same way. As I have seen in many tutorials when you click on record it asks you to choose one of these. Is something changed in new release?
Yes, it is part of the new release of Ranorex 8.3.0. Ranorex has made some changes to Ranorex Recorder and now it no longer asks to select the application you want to test. I think the workaround would be that you can leave your application open before recording and also add the application to the white-list so that when it runs the test it can only focus on the white-listed application and hence would increase efficiency.
More information can be found here https://www.ranorex.com/what-is-new/ under "Ranorex Recorder Improvements" or in the "Release Notes" https://www.ranorex.com/release-notes/
I have created an XCode 8 Extension (For Deleting Lines, Like Sublime and Android Studio). I have code-signed it and it works as expected in the Gray Xcode Test thing.
I haven't seen a single instruction on how to get it to run with "Regular" XCode? What should I do to be able to use my extension whenever I start XCode?
After somehow getting this to work (once) by restarting my computer, I have finally found some working instructions on how to use an Extension with XCode 8. These are the steps:
Enable target signing for both the Application and the Source Code Extension using your developer ID.
Product > Archive.
Right click archive > Show in Finder.
Right click archive > Show Package Contents.
Open Products, Applications.
Drag "YourExtension".app to your Applications folder.
Go to System Preferences -> Extensions -> Xcode Source Editor and enable this extension.
Restart XCode if necessary
im making a vb.net app and i want to set the icon, how can i do this?
--edit--
turns out i was a bit confused, and it was working. but the answers can still be useful for others.
If I understand the question and issue, your setup/installer might be missing something.
It would seem you did create a shortcut, add it to the Setup project to install to the Desktop (else you wouldnt have one at all)
Select the shortcut in your setup project, open the properties window
Click Target. The list of files you are installing will come up. Select the App.Exe (ie the main executable "MyApp.exe" ususally the primary output). I think Icon is supposed to be set to "Icon" as well.
I think those 2 things combined link the Desktop Shortcut's Icon property to Use the App.Exe's. If there is also a shortcut in the user's programs menu do the same thing (or drag drop a copy).
You are basically doing to the Setup Project's shortcut what you would do to a normal desktop icon to change it or set it. The proj apparently fills in the actual path etc at install.
EDIT
PUBLISH simply compiles everything and produces files for the dev to distribute. It is called PUBLISH because in many cases the output includes a ready to use Setup program for the END USER to install on the PC. (Based on your new Pic, you are trying to reinstall everytime you click the icon or file inside the folder.)
Again, if you do not add a Setup proj to your project, the default one is used and it gives no option for where to install and does not add a shortcut.
Just delete all that junk, Publish again to the default location (VS Studio\...Project name\bin\Publish). Go to that folder and run setup. It will still install to Users\AppData.. but will add a shortcut (to the program) to the start menu.
For a desktop icon, do the "Send To Desktop ..." thing. To INSTALL an icon, you have to add and modify a Setup proj to your Solution.
HTH
'The folder shows the icon for the app, but the icon for the form is different. change the form's icon(in the property grid) to the same as the app and you should see it then.
When you publish it there's 2 files produced that are basically setup files. One relies on the ClickOnce Application Deployment Support Library and the other is a standalone setup app. Since neither one is the actual app you designed, they aren't going to have the icon you want. You'll probably have to investigate other more configurable deployment options.
I had a few automator actions developed under OSX 10.6, which successfully executed under automator without an issue. The binary products of these actions continues to work under OSX 10.7 (Lion), but compiling them from source fails.
In trying to debug this issue, I created the dirt simple "Hello, World" action, but it will not successfully execute in automator, both the ObjC and Applescript variant getting "launch path not accessible", no matter where in the workflow they are placed.
The development path I have followed is:
In XCode 4.1 (build 4B110, from the App Store), create a new project, and select Automator Action" as the type
Set Output type to com.apple.cocoa.string
Under the ObjC variant, change the runWithInput:error method to return #"Hello, World!" Under the AppleScript variant, change the runWithInput_fromAction_error_ method to return "Hello, World!"
Compile the action via the run arrow
Open the new action in finder via right click on the action under the Products group
Double click on the action and let automator install it
In automator, create a single item workflow (but have tried multi-item workflows) with the new action
Execute the workflow via the run arrow and receive the "launch path not accessible" error
I have tried restarting xcode, restarting automator, removing my ~/Library/Automator directory after shutting down automator, and combinations of the above without change. At this point, however, I'm out of ideas.
Thanks for your help.
As per the comment recommendation, and for posterity, the issue appears to be localized to XCode 4.1. XCode 4.2 betas do not exhibit this behavior and appear to operate as expected following the workflow I outlined in the question.
after stopped searching for it, found an tutorial but can't test it anymore because I already upgraded to Xcode 4.2. It would be nice if someone could verify that:
http://macosxautomation.com/automator/xcodefix/index.html
Any suggestions as to why the app will launch and quickly disappear from the dock? It's a very small app with about 80 lines of code and no outside API's, libraries, or dependencies. A simple countdown app created in about an hour.
Have your friend run it from the Terminal window (ie ./MyApp.app/Contents/MacOS/MyApp ) and see if it prints out any helpful error message to stdout.
Check the settings in info of the project. Check the product Name in target and project.
And also check the "set Active target" and "set Active SDK"(Simulator).
This should work.