OpenEdge Development - Products Enhancements - Progress Community

 OpenEdge Development

  • Enhance stack trace to identify USER-INTERFACE-TRIGGER used

    Stack traces are brilliant for identifying whereabouts code is failing. But when it tells you the code is part of a USER-INTERFACE-TRIGGER it makes it a lot harder to track down. Yes, it tells you the line number, but when icode is involved it becomes...
  • proxygen dotnet (.net) core dlls

    • Under Review
    • 0 Comments
    Similar to: https://community.progress.com/community_groups/products_enhancements/i/openedge/net_core_linux We would like dotnet core version 2.0 of the proxygen generated .net dlls including Progress.Messages.dll and Progress.o4glrt.dll.
  • Add expected error message numbers per statement/method/... to the documentation

    When handling specific Progress.Lang.SysErrors currently it's always try and error to know the error message numbers to filter on. If the expected error message numbers would be documented this would make creating rock-solid code much simpler. Other...
  • SUPPROMSGS for OEDK: Classroom Edition

    Non english language pack exists only in additional language pack and is not available for OEDK: Classroom Edition users. This is serious problem for newbie. Please add a language pack (SUPPROMSG) to the OEDK: Classroom Edition
  • Add write-json and write-xml methods to query object handles

    • Under Review
    • 0 Comments
    Currently you can apply the method to a buffer handle and write out the entire table as json or xml. If you only want some of it, the only way is to copy the records into a temp-table and then apply the method to that. Creating temp-table records takes...
  • ABL Scratchpad - Tabbing

    • Complete
    • 0 Comments
    Re: https://progress.my.salesforce.com/articles/Article/000043396?popup=true A bit of a nuisance that is. Tab key doesn't tab in the ABL Scratchpad. Confirmed as still broken in 11.4.
  • Rationalize procedure references in xref

    Currently, procedure references in xref (both kinds) are placed in the output in sequence with the end of that procedure rather than at the line where the procedure actually begins. The line number referenced is the line number of the end. My understanding...
  • Ability to use properties anywhere a scalar can be used

    • Under Review
    • 0 Comments
    This includes all UI input / output fields, dialogue boxes, etc. Presently an intermediate scalar variable has to be used to shuttle data from the property to the UI element and back again.
  • Docs: Replace "Explain everything everywhere" policy with links

    • Under Review
    • 0 Comments
    I'm reviewing the ABL Ref Doc for stuff on WIDGET-POOLs, and I noted that each case where NO-ERROR is part of the doc, there's a whole dissertation on NO-ERROR relating to CATCH, ERROR-STATUS, etc. In the case of the DELETE WIDGET-POOL statement...
  • Add CANCEL-REQUEST() method to Async request handle

    Currently you can't cancel a single asynchronous AppServer request. AppServerHandle:CANCEL-REQUESTS() cancels ALL pending requests, which is too much for my needs. A CANCEL-REQUEST() method on the asynchronous request handle could be useful to...