Now after saving our changed " " file, we copy that over to the original file location, namely. Key = ShowFrameTextRuler Type = Boolean Value = YES Key = ShowFrameTextRuler Type = Boolean Value = NO We have to open and edit the above file copy with some binary format capable "plist"-file editor (aka Xcode or some third party editor)Īnd look inside that file for a key/value pair which initially reads "ShowFrameTextRuler/NO", the value type is a boolean here, so. since we will modify that file, we will first make a backup of the original " " file and work on a copy of that one. > /Users/username/Library/Containers//Data/Library/Preferences/ On my MAS APh version the preferences "plist"-file to alter can be found under the path. Ok let's start to enable FrameText rulers for APh under MacOS now. PRE-NOTE2: Under Windows systems doing the same should be much easier, since there (on Win) you usually just deal with text based XML settings files, so no binary versions of those, which eases the overall changing process. Usually one would use Apple's Xcode in order to manipulate and change a binary "plist"-file, but there are also some easier to use third party editor tools available, which can showup and edit binary "plist"-files in an easier to use fashion (without the need of Xcode). PRE-NOTE: On a MacOS system Affinity Preferences settings are stored in OS related binary "plist" files (aka binary representations of XML-files), so in order to read/write and perform changes to such binary "plist"-files, the right tools have to be used. Further since I'm too lazy, I will show it only for APh here, but it should be equally for ADe too. I'll demonstrate that under MacOS here since that's what I have & run Affinity apps on. Well, let's show some prefs hack here how one could enable FrameText rulers for the other Affinity apps like APh & ADe then too.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |