Author Topic: VisualAge C++ 3.0 editor  (Read 2164 times)

Robert Roland

  • Newbie
  • *
  • Posts: 7
  • Karma: +1/-0
    • View Profile
VisualAge C++ 3.0 editor
« on: September 16, 2023, 05:44:36 am »
So, the LXPM in VAC 3.0 does not like widescreen resolutions, but the LXPM in VAC 4.0 works great there.

For VAC 3.0, is it possible to override which editor WorkFrame launches? Either to the LXPM in VAC 4.0 or to NEPMD? (or some other good coding editor?)

Thanks!

SoundChaser

  • Newbie
  • *
  • Posts: 26
  • Karma: +0/-0
    • View Profile
Re: VisualAge C++ 3.0 editor
« Reply #1 on: September 16, 2023, 01:08:21 pm »
LXPMs should have a backward compat command line interface. I would try renaming one instance to, say, lxpm.old and have OS2 find the other executable through the PATH as first experiment if there's no configuration setting for it...


Lars

  • Hero Member
  • *****
  • Posts: 1262
  • Karma: +65/-0
    • View Profile
Re: VisualAge C++ 3.0 editor
« Reply #2 on: September 17, 2023, 07:37:49 am »
So, the LXPM in VAC 3.0 does not like widescreen resolutions, but the LXPM in VAC 4.0 works great there.

For VAC 3.0, is it possible to override which editor WorkFrame launches? Either to the LXPM in VAC 4.0 or to NEPMD? (or some other good coding editor?)

Thanks!

Workframe comes with a default project and any own projects inherit from this project (unless you deliberately change that for a specific project). In that default project you can modify the corresponding "edit action" (Workframe Slang) to use the VAC 4 editor instead of the VAC 3 editor. And once you have done so, you will therefore have changed it for all of your projects.
« Last Edit: September 17, 2023, 07:50:28 am by Lars »