Auto Indent in uVision3

It's the same behaviour on my system (using uVision3 with Win2K).

Sometimes the editor surprises me in making the auto indent correctly but this only happens every now and then, usually it doesn't work as long as virtual spaces are disabled...

Carsten

It's the same behaviour on my system (using uVision3 with Win2K).

Sometimes the editor surprises me in making the auto indent correctly but this only happens every now and then, usually it doesn't work as long as virtual spaces are disabled...

Carsten

Thanks, at least I know I am not the only one experiencing this.

Hopefully the guys at Keil will fix this in the next release, I really miss my auto-indent!

btw - My platform is also Win2K.

Russell

"I really miss my auto-indent!"

So why don't you just turn on the "virtual space," then?

I always have "virtual space" space enabled in UV2 anyway!

I don't like virtual spaces and have never enabled them. Old typing habits die hard and I like being able to navigate through my code using the left & right arrow keys.

Auto-indenting without virtual spaces worked fine in UV2!

AutoIndent really only works when Virtual Spaces is ON. This is a bug that we will solve.

Thank you for pointing to this issue.

Reinhard

Virtual spaces are quite annoying to me when navigating through the code, so I don't use them.

But I expect the auto indentation to work with or without any other editor settings beeing enabled.

Clearly a matter of preference - but I find it really annoying without "virtual spaces!
I don't like the way the cursor keeps disappearing back to the LH margin without virtual space on!

"But I expect the auto indentation to work with or without any other editor settings beeing enabled."

Quite so - and it seems that Keil agree, too!

Many, many moons ago when "single chip" was unheard of and "embedded" was a minicomputer weighting quite 20+ pounds, I made a parameter entry program, tested it and delivered it to testing with a smile. 10 minutes later "the crap" came back. I tested and tested, could find nothing wrong and resubmitted. This time it came back with a nastygram. At a loss, I asked testing to break the rule of no contact with programming and show me. It turned out that the program spec said "separated by tab or space" I used the space, the tester used the tab. 10 minute fix and they lived happily ever after.

Erik