CSIDE Import doesn't respect original source importing

Migrateduser

I've noticed a quirk with the CSIDE import process. It does odd things with the indents of your Oscript. When you write a new function in a new package, typically it puts your function prototype at tab 1, and (if you're using the code generation widget), the next line is at tab 2, and the end function is at tab 1 again. Now, if you take that ospace and import it on a different CSIDE instance, it will respect the position of the function prototype, but it will push out all your code, adding a second tab (for a total of three tabs), and put your end statement for the function at tab position 2, not 1. The following figure illustrates:

The problem is that if you have developers import from the ospace multiple times, the indentation is cumulative and you end up with the source tabbed over in some cases, almost the entire width of the page over. Thus making the code very difficult to read. I noticed a similar behaviour with script objects. WHen your oscript is interpreted as type Script (code written between script and endscript tags), it indents out even further. If you correct it in your source, the next person who imports will get the extra indents back.

I know everyone should just share the source meaning that you import once to get your environment built then replace the code, but I tend to work with different teams, some of whom still try to work as was done in Builder, where you edit the .OLL file. meaning I almost never get the source of the latest version of the module.
Anyway, not sure if this is a known issue, or if there's a fix for the import, or if the only workaround is to get everyone on board with editing only in the Oscript tab of your Eclipse project (which also lends itself better to source control).
just my observations on the import process in CSIDE.
-Hugh