Include the help files (markdown) with the installer.

[LordDurus]

Include the help files (markdown) with the installer.

This will make setup for new users easier.
The existing setting will be used, this way if someone wants to use a custom path for the help they can.

[LordDurus]

This is done in dev. Also fixed several issues with the hovertext not working in Linux (case sensitive file names).

[LordDurus]

Need a good way of updating the help files. Currently I'll have to remember to do it.

[DualBrain]

Are there help files for the actual extension? How do you get to these? Or are you talking about the QB64 markdown files? If so, I thought the solution that was there was already working? If not working, what needs to be done?

[LordDurus]

These are the qb64 help files. Used for the F1 help and hovertext. Including them with the extension gives new users one less thing to setup.

The extension still uses the helpPath setting. It will get defaulted to the markdown files included with the extension. But it can be changed to the QB64 folder. If the helpPath is already set it won't get changed. The setting will be already set for anyone who already has working hovertext/f1.

For now I just copied the files in since they don't change very much.

Having a process that pulls them down at build would be better.

I did find an issue while I was in there. If the case of the keywork in the code didn't match the case of the filename. Then the hovertext would show on Linux. I fixed that.

I'm going to create a different issue for this, what files are needed to QB64 IDE running? I'd like to include that as well. Then someone would only need to install the extension to start coding.

[LordDurus]

Looks like including QB64 IDE is not going to work. It needs about 550mb of support files. The c/c++ compiler mostly.