When enabled it seems to struggle to allow key input

[MullinsN]

Hello,

So it seems when running with this extension on v1.57 the extension when enabled, stops VSC from allow the user to type. The program is 3000+ lines, so I did wonder if that was the problem. However smaller applications, were also struggling.

It didn't seem to be a problem previously, but I haven't used it in a while. Has something changed behind the scenes in VSC to cause a problem.

It is a shame this isn't actively developed. I had hoped that Progress would have stepped in and written a extension, like MongoDB have, but still no joy.

[chriscamicas]

Hi @MullinsN thanks for your feedback.
I don't work in the Progress ecosystem anymore, but still provide support for those using this extension.
Do you have a program available I can use to test if I can reproduce this behaviour ?

[chriscamicas]

btw, I did contact Progress but they don't seem interested in supporting such projects/initiative.

[gquerret]

I did contact Progress but they don't seem interested in supporting such projects/initiative.

Who ?

[chriscamicas]

I did contact Progress but they don't seem interested in supporting such projects/initiative.

Who ?

Via Peter Judge In the OE Slack team, he told me he contacted the Product Management

[MullinsN]

I was at Progress PUG a couple of years back, prior to the pandemic and raised the issue of lack of intergration of Progress/Openedge ABL into VSC.

[chriscamicas]

I was at Progress PUG a couple of years back, prior to the pandemic and raised the issue of lack of intergration of Progress/Openedge ABL into VSC.

Thank you ! Please continue raising your concern to Progress, hopefully they'll hear (all of) you and finally support this extension :)