Not just for comic books, but for many people, like myself, who work with nontechnical individuals, this is how large groups of image files are distributed. Instead of keeping tack of 100 individual image files, you keep track of a single zip. ![]() Also as was pointed out, the reason for this is not size, it is convenience. Only when they are treated exactly the same way as folders, natively or via an add-on, will XnView be usable as my full time image software.įirst of all, as was pointed out, this is the standard format for distributing digital comics, so saying no one uses it is grossly inaccurate. The lack of ability to use standard methods for moving around inside these files is crippling. The way the archive add-on for XnView currently works is in no way shape or form a suitable or useful replacement for the way ACDSee handles these files. Many things are distributed as large numbers of image files inside a zip or rar file so as to distribute a single file instead of a large number of separate files, and not being able to view these types of pseudo-folders is an extremely large problem, since about 80% of what I use a program like XnView to look at is in this format. What I need to be able to do is browse around these files with all features enabled, such as being able to go to the next and previous file, use a slideshow, and other strictly viewing oriented functions. Editing the files inside works differently (mostly, you can't, although in the newer versions they have gotten some features to work), but I am not concerned with this. In ACDSee, a zip or rar is 100% identical to a regular folder for the purpose of browsing. The behavior of zip and rar files as no different than folders is the one and only reason I am still using ACDSee. Then just copy the whole filename to the clipboard, choose in photolab "open in application" -> choose the right location where you have saved your. The Problem here seams to be, that you have saved the File as a Text File (.txt = Text Document), just save it under the File Type All Files (*.*) as NAME.bat.Īlternative = enable that you can see the file extentions in windows and remove. And the Affinity Photo2 and the rest of the Affinity 2 apps are installed as you can see in my systems folders window. The third image is what it looks like when Affinity Photo 1 is selected, this is what it would look like when I point DXO in the export to program file menu. I point DXO to the location of the file and this is what I get. My question is where the hell is the application hiding in windows. And by the way this hack does not work, unless I am doing something wrong. This is absurd to have to go through this to have something working as it should out of the gate. This should have been one of their main check list items before launching the software to the masses, making sure that the end user is able to use it out of the box with software like LR and dxophotolab, just like with Affinity Photo 1. The file should be in my programs folder as Affinity 1 is, dxophotolab is, DaVinci Resolve is, and every other software that I have downloaded to my PC. ![]() I don't have time for this hack nonsense. ![]() That's the reason the execution alias exists - it lets you have a consistent way to launch the program without worrying about where it's actually located. The folder's name is likely to change with the version of the Affinity program that has been installed so don't keep it as a permanent shortcut. Executables are located under the "App" folder. Go to Task Manager, expand the "Affinity 2" group in Processes -> Apps, then right-click the child entry and press "Open file location".Īlternatively, launch an administrator Command Prompt window, go to C:\Program Files\WindowsApps\, find the Affinity program you're looking for, then copy-paste the folder path (including the program's package folder name) into Explorer. You can directly access the program directory. Heck even in the initial main drive location where the program is installed you have no access to the program folder. The problem is that windows "the developer" has locked any access to the file when you move the file to a different drive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |