Funny formatting with :index - Forum - OpenEdge Development - Progress Community
 Forum

Funny formatting with :index

  • It isn't consistent, but I am finding that OEA spontaneously takes lines like

    Index_Feature = objNode:Index.

    and turns them into:

    Index_Feature = objNode:

    Index.

    I am presuming this happens during reformatting. Anyone else encountering this? I think it might happen only once per file so that once I fix it, it sticks.

    Consulting in Model-Based Development, Transformation, and Object-Oriented Best Practice  http://www.cintegrity.com

  • I don't think I'm having this problem...

    All my Index properties are on the same line with the class itself...

  • What are your settings for insert spaces/tab and the number of spaces for an indent. I am at indent spaces and 2 and there is a rather significant rearrangement that occurs when it gets around to doing a bulk reformat. I am pretty sure that is when it is happening.

    Consulting in Model-Based Development, Transformation, and Object-Oriented Best Practice  http://www.cintegrity.com

  • I just looked at the original files and they have tab characters instead of spaces, so I think this must be happening on the reformat.

    Consulting in Model-Based Development, Transformation, and Object-Oriented Best Practice  http://www.cintegrity.com

  • Don't know. Can't seem to find where you set these preferences...

    (So I am using the default settings )

  • Windows->Preferences-OpenEdge Architect->Editor

    Consulting in Model-Based Development, Transformation, and Object-Oriented Best Practice  http://www.cintegrity.com

  • Ah, I was so focused on the General, Editors section somehow I missed the other OE settings altogether.

  • Ah, I was so focused on the General, Editors section somehow I missed the other OE settings altogether.

  • Ah, I was so focused on the General, Editors section somehow I missed the other OE settings altogether.

  • I see you got caught in the long pause too ... only I was on the way to composing a post, not trying to post one already written.

    Consulting in Model-Based Development, Transformation, and Object-Oriented Best Practice  http://www.cintegrity.com

  • Well, until this morning, I thought I was getting a handle on this. Quite consistently, I would open the file from which I had stripped the excess ^Ms, stick in a using for the path, add the path to the class name, and save. Sometime during that interval, the screen would shimmy like an earthquake, and the file would reformat from 4 space indents to 2 space indents. Checking behind the scenes it also turned out that the tabs were being replaced by spaces. Since the outline was being refreshed at the same time, I suspected that this might have something to do with the AST refresh.

    After that initial shift, which broke any :Index references, it would usually stay fixed, but a couple of times I have had it re-break the :Index references, perhaps because it is a file that required more edits than most.

    Today, I can't get it to reformat at all. I am trying to come up with a test case for TS and doing what seems like the same things, but it is staying with the four space indents.

    I don't suppose anyone knows a way to force a reformat?

    Consulting in Model-Based Development, Transformation, and Object-Oriented Best Practice  http://www.cintegrity.com

  • ^F

    In find put \t

    In Replace put 2 spaces (or more of the perverse among us )

    Check wrap search and regular expressions then choose Replace all.

    Then ^A

    Right click

    Choose Source -> Correct indentation

  • This fixes everything expect OEA's very annoying habit of putting do: on a new line.

    You can tell that this is a feature installed by people who are not professional developers.

    No sane developer would put "do:" on a line by itself (unless creating a standalone do block); every such instance forces an additional click when stepping through code with the debugger.

    Since progress doesn't allow assignments in a logical test (unlike, for example, C), the values of variables at the do are the same as the values on the line preceding a do.

  • No sane developer would put "do:" on a line by itself

    (unless creating a standalone do block);

    quess this confirms what TMH already thinks - I am insane.

  • however, I could say with certainty that I must be one of the few who has never used the debugger to debug code