Did this article resolve your question/issue?



PDSOE: How to improve the Indentation (CTRL+I) in Progress Developer Studio?


TitlePDSOE: How to improve the Indentation (CTRL+I) in Progress Developer Studio?
URL Name000047084
Article Number000169326
EnvironmentProduct: OpenEdge
Version: 10.1C, 10.2x, 11.x
OS: All Supported Platforms
Question/Problem Description
How to improve the Indentation (CTRL+I) in Progress Developer Studio?
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
CTRL+I feature is used to automatically correct the indentation of a source file, 
By default this follows tabular indentation meaning if there is a source code like below: 
<<Snippet 1>> 
User-added image
On performing CTRL+SHIFT+I all the variables on top of the file will be aligned in a tabular format, the output will look something like this: 
<<Snippet 2>> 
User-added image

The extra space after AS CLASS is because of tabular format indentation, it tries to indent all keywords and other variables under columns, if you observe you can find CTRL+I has arranged all the statements of variables in 5 columns. 

However, the tabular formatting can be turned off by changing a preference. 
In Windows>Preferences>Progress Openedge>Editor uncheck the option “Enable tabular formatting” 

Now performing CTRL+I on <<Snippet 1>> will result in output which will look something like this: 
<<Snippet 3>> 
User-added image
The code inside REPEAT block is given one tab space to represent that the code is inside REPEAT block. 

However do note that once you perform tabular formatting and then removing the preference option will not change the indentation of the variables. 

Which means after removing the preference option if we perform CTRL+I on <<Snippet 2>> will not result in <<Snippet 3>>, 
But performing CTRL+I on <<Snippet 1>> will result to <<Snippet 3>> 

When tabular formatting is enabled, each keyword will be aligned with a new column. The gaps appeared in the code is due to some extra keywords (like Class) in variables definitions.
The tabs are added before each line and the normal code won't format as Table. When a statement has multiple keywords then only table formatting applies (like var. definitions, temp-table fields etc...).
Last Modified Date12/20/2018 12:10 PM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.