![]() I managed to get them working with the Edit With and Open with menus maybe a month or so ago and have 'fiddled' with the BuiltInOpenWithPluginSettings.xml before. I have had so many problems with the OpenWith plugin during my time with C1, initially I could not get the plugin to recognise any of the apps I had installed (Nik being the main set of plugins I use, at least occasionally anyway. I have not tried installing 13.1.1 in it's own folder, I could try it I suppose.but I am a bit reluctant as I don't want to screw up my settings as discussed above.Īs I said I have submitted a request and C1 returned the answer that it's a bug, and while I usually don't mind having a play to try and fix these things myself, I don't have time this week.maybe on the weekend ) I want to make sure I fully backup all my settings before jumping in and have a play. ![]() Note the picture is from 13.1.0 and not 13.1.1 (as I said earlier the BuiltInOpenWithPluginSettings.xml file did not change as a result of installing 13.1.1) The file and the picture are plainly not the same. ![]() and these are the apps I have available through the plugin: This is what my BuiltInOpenWithPluginSettings.xml file has contained within:Ĭ:\program files\affinity\designer\designer.exeĬ:\program files\affinity\photo\photo.exeĬ:\program files\windows photo viewer\photoviewer.dll I have found that the contents does not represent the list of applications that I have available to me either in the working 13.1.0 version or the non working 13.1.1 version of Capture One. It has been suggested to me before that the BuiltInOpenWithPluginSettings.xml contains the list of Allowed Applications but I am not convinced this is the case. I did try to install again and I noticed that the BuiltInOpenWithPluginSettings.xml file did not change. No, I just installed 13.1.0 over the top and I did not completely uninstall due to fear of loosing all my settings, configurations and pre-sets/styles, etc. The last line indicates that the plugin finds itself in an unanticipated situation. | Exception when trying to get result from the plugin - called from: Actually, on my system (Windows ), the problem clearly occurs when the plugin tries to access the registry data about. Some program execution monitoring and a look at the log files show that the plugin crashes before accessing that configuration file, just after being initialized. ![]() BuiltInOpenWithPluginSettings.xml doesn't seem to be involved. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |