UI Layout suggestion; Given the requirement to use a full pathname for saving and loading a ui layout as written, perhaps it's worth adding instruction for making a quickslot shortcut to load a saved layout i.e.;
/shortcut xx /ui layout load "/Users/<userid>/Library/Application Support/com.turbine.lotroclient/ui/<layoutname>"
- Interesting idea -- never thought about it that way... thanks. Wm Magill - Valamar - OTG/OTC (talk) 18:34, 5 November 2012 (EST)
For some reason today when I tried using the shortcut <alias /shortcut 34 /ui layout load "/Users/simon/Library/Application Support/com.turbine.lotroclient/ui/layouts/default"> the actual shortcut from the quick slot was failing, cutting off at <"/Users/simon/Library/Application">. It works if I copy/paste </ui layout load "/Users/simon/Library/Application Support/com.turbine.lotroclient/ui/default">. Any idea why it's failing? Seems to be a problem with an Alias and the folder name space between Application Support. It drops off the "" in the path. —The preceding unsigned comment was added by Moonraker (Contribs • Message • Email) at 22 November 2012.
- Hard to say, but I would venture a guess that the ?shortcut? command is truncating the value when it is being saved in the Quickslot.
- It also might be the classic Unix parser issue -- space is a delimiter!
- Try: /alias /shortcut 34 /ui layout load "/Users/simon/Library/Application\ Support/com.turbine.lotroclient/ui/layouts/default"
- Note the "\ " (Backslash space) between Application and Support - This is called "escaping the special character. Even though the file name is enclosed in quotes, which should escape the string, they are probably being stripped off BEFORE the string is passed along to the next component.
- Wm Magill - Valamar - OTG/OTC (talk) 13:37, 25 November 2012 (EST)
Use installation on multiple accounts
I think the command chmod -R ug+rX ... is missing the write bit, isn't it? Starting with the plain installation, the first problem is, that the group is missing the write permissions. Anyway, wouldn't it be easier to set the group bits equal to the user bits? That would be chmod -R g=u, then. --Vidurr (talk) 10:08, 8 November 2012 (EST)
- I don't know anything about installing on Mac, but if you are confident your suggestions are valid you are free to edit/add/update/improve/etc. the article. This is a Wiki and you and other users are free to improve on any existing page and add new pages that should exist ;) -- Zimoon (talk) 12:00, 8 November 2012 (EST)
- Yeah ... I suppose the "simple" answer would be to have folks "chmod -R ug+rwX" and be done with it. I suppose there really is no difference between "chmod -R ug+rwX" and "u=x". One issue is that all .dat files need to be "rwx" -- my umask is 0077, and I have no idea what the OSX default umask is ... and I do not know which one the Finder uses when copying from a .dmg file. —The preceding unsigned comment was added by Magill (Contribs • Message • Email) at 22:32, 8 November 2012.
Notes on 10.9 Mavericks
29 July Patch to the Steam Mac Client.
- Added support for Mac OS X 10.9 (Mavericks) App Nap feature
- Updated Overlay check to work correctly with API changes in Mac OS X 10.9 (Mavericks). Note that the location to enable Accessibility services in 10.9 has moved to System Preferences > Security and Privacy > Privacy
- Fixed crash on OSX when using an AirPlay display
- Fixed the overlay check mis-reporting causing some games to believe the overlay is unavailable when it actually was present
From the Relase notes:
- The LOTRO Store once again opens using an in-game browser. Note that the Mac client will continue to use an external browser for now.
- There is now an option to open the LOTRO Store in an external window. This option can be found under Game Options > UI Settings > WebStore > External Store.
- Pop-up windows that open when clicking certain links using the in-game browser will continue to open using an external browser.
- From the discussion thread:
- We're using Chromium Embedded Framework, the underlying Chrome is 56.0.2924.76, from approximately January 2017. It does seem reasonable to think that the browser technology and the older OS's may not mix.