Every time I try to open the manual (F1) it says that the file is not contained within the folder. There is no manual html in the doc folder nor can I find it online.
Can anyone point me in the right direction here please and thanks:)
Every time I try to open the manual (F1) it says that the file is not contained within the folder. There is no manual html in the doc folder nor can I find it online.
Can anyone point me in the right direction here please and thanks:)
Yikes, what platform are you on? We re currently preparing online docs, but in the mean time you can find them >here<. Please don’t forward that link as it’s only temporary!
I’m on OSX Yosemite running latest version of cabbage. I’m sure the manual (F1) was working yesterday, but Today I get that message, and I have not moved files around or anything. If the same information is available in those docs then it’s all the one:)
… oh, and thanks for the link Rory:)
This happened to me too recently… the f1 / internal docs seemed to stop working. It’s weird, because the docs are actually still there and usable. Try this putting this URL in your browser: file://localhost/Applications/Cabbage.app/Contents/MacOS/Docs/index.html
Or alternately try this: “open file://localhost/Applications/Cabbage.app/Contents/MacOS/Docs/index.html” from a terminal, without the quotes. Either way will hopefully get you up and going with your local copy of the docs.
Also, I thought it was Ctrl+1 for OSX?
Ooops, Command+1… but either way, it doesn’t work anymore for some reason I can’t find where I reported it before, but I know I had brought it up once. I thought you’re the one who pointed me to find the offline docs in the app’s folder in the first place.
The full error message is “Could not find Cabbage manual. Make sure it is located in the Docs folder in the same directory as the main Cabbage executable”
The docs are definitely there, launching them in either of the manual methods works fine.
You certainly did alert me to it before but I’ve yet to reacquaint myself with my OSX machine in order to fix it. Should happen this week with a new release some days later I hope.
No worries, I was just surprised that I couldn’t find my old thread about it… it must have been a comment buried in a thread of a test release or something. I’ve been up and running with working docs, so it wasn’t really a priority.
Glad to hear it doesn’t just affect me tho… I was starting to feel like this mac is cursed.