IniParser | PHP INI file parser supporting section inheritance | Parser library

The problem here is that when you have access to a file via a StorageFile instance at a arbitrary location (user-chosen), you need to use this specific instance to work with the file. You cannot access the file directly by accessing its path (file.Path).

I have checked the IniParser source code on GitHub and found out you can use the IniDataParser API instead, for example the following method:

Syntax highlighting in Sctintilla is done by dedicated highlighter classes, which are lexers. A parser is not well suited for such kind of work, because the syntax highlighting feature must work, even if the input contains errors. A parser is a tool to verify the correctness of the input - 2 totally different tasks.

So I recommend you stop thinking about using ANTLR4 for that and just take one of the existing Lex classes and create a new one for the language you want to highlight.

You can't write code like that at the class level. You can fix it by overload the constructor or the Form_Load

You should NOT be using an fstream at all to create/open the INI file manually. WritePrivateProfileString() and GetPrivateProfileInt() handle that for you.

Also, if you read their documentation, you would see that you SHOULD NOT use a relative path for the INI file, or else the file will be relative to the Windows installation folder, not your app folder. So, you probably ARE reading/writing the INI file, just not where you are expecting from/to. If you want your INI file to be relative to your app's folder, you need to retrieve the path of your app's folder ¹ and append the INI filename to it.

¹: that is really not a good idea in general, though. Depending on where you install your app, the user might not have write access to that folder. You should instead use SHGetFolderPath() or SHGetKnownFolderPath() to get the user's local %AppData% folder, then create your own subfolder inside of it, and then create your INI file inside of that subfolder.

Try this instead:

Atom-default package line-ending-selector have a Default line ending for new files setting.

It depends on how you want to use the main form - you could have a static property which you could set (which would update the text for all main form instances).

If you only have one main form, and have a reference to it when you create the FormAddUrls object then you should just change the constructor to accept a MainForm (or as generic a type as possible), store the reference as a field and update the property on it when the button is clicked: