Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow a .ini file instead of "propath" array #24

Open
andresapao opened this issue Oct 9, 2018 · 3 comments
Open

Allow a .ini file instead of "propath" array #24

andresapao opened this issue Oct 9, 2018 · 3 comments

Comments

@andresapao
Copy link

It could be easier point a INI file instead of copying all of its entries to "propath" array of .openedge.json

@chriscamicas
Copy link
Owner

What do you use your ini file for ? Only Propath ?
Could you provide a sample file so I can test few things ?
Thank you

@ntreeby
Copy link

ntreeby commented Jun 1, 2022

  1. .ini file contains font definitions, including default font. Syntax checks can fail if the default fonts (in progress.ini) are the only ones available to the AVM.
  2. For correct syntax checking of .w files, should use prowin.exe not _progres.exe

Since it is not allowed to specify -ininame in a .pf file, and there is no general command line parameters option in .openedge.json, there is no way to specify a .ini file.

See: https://docs.progress.com/bundle/openedge-startup-and-parameter-reference-117/page/Initialization-File-ininame.html

@gquerret
Copy link
Collaborator

gquerret commented Jun 2, 2022

New version of this plugin will allow INI file declaration so that the right fonts / colors can be used. Propath has to stay in the JSON config file though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants