Hi Herwig,

"Code completion" does not work.
You have to disable it - via Options -> Editor Options.
Also unchecked "Code parameters" and "Tooltip symbol insight" .
I am on RAD Tokyo coding for Win 64 - but these features did not work since at least ten years - not in Seattle, not in Berlin, not in Tokyo (I think they are slightly improved, but waiting 30 seconds is just as unacceptable as waiting 60 seconds).

As far as I can remember the stability of Seattle was Ok - so maybe you have also some other problems with your installation.

Best - Oliver

Am 30.03.2017 um 17:01 schrieb Herwig Huber:
I've the same problem. IDE crashed every 5..10 Minutes. I guess, c++11
is unusable in RAD Studio

Martin

snip

Herwig, you are more likely to shove a stick of butter up a wildcat's rear with a red hot fireplace poker, than you are to get your money back.

Funny that you should pose that question.

After I purchased my bright, shiny Seattle 10, specifically to build a single x64 project for the 4th largest company in the U.S., and to be used by every single domestic and international tax account within that company, I found that x64 was so horribly broken that I ended up having to hand-disassemble and then remake numerous library pieces.

Bug reports produced NOTHING, ever. In desperation, my backup plan was to use Visual Studio 17, and it would have been a much-protracted process.

10.1 came with promise to correct 10 million bugs, but none of which affected my problems.

I was in weekly contact with the Austin sales girl, who apparently got wise to the trash being sold, and may have left for better company.

In any event, there was a constant push to "upgrade" to Tokyo, which I refused, pointing out that not a single problem I had reported had been corrected, much less properly addressed.

After the pushy sales chick left, her replacement had the gall to call me one day. He got his stupid head handed back to him, with an offer that I just come down to Austin and place it where the sun never shines, with a rejoinder to never call me again, and that Emb would NEVER receive another thin cent from me.

No, you will not receive a dime of your money back, and I don't care how sorry the product you received is found to perform. You'll be lucky to get your application built and out the door, without a bunch of fixes, most of which you will have to make, as you will get 0 (ZERO NULL) from quality.xxx

My numerous requests for refund were literally laughed at by sales. They simply pointed to the EULA, which clearly states that Emb is protected 100% from your gripe, and what you get is what you get.

My honest appraisal (based on 35+ years of programming history) is that you "might" get a functional XE?? something in the year 2525, if man is still alive.

Jaded about Emb? You bet.

I had extreme high regard and hope for XE, and was shafted from DAY 1 with the product.

For practically every C++ Windows application, I use Borland C++ Builder 5, which, for the most part, WORKS, x32.

VS for reliable x64, or XE 10.1 for VERY SIMPLE applications that have little 3rd party components, try/catch, etc.

For Android, I use Eclipse, for IOS, I use XCode on a Mac, and for embedded, I use whatever the manufacturer recommends.

10.1? ha it's a toy, an expensive experiment of failure. Check quality.emb, it is replete with fail

Edited by: Keith Dopson on Dec 27, 2017 5:27 PM

For me (still on XE8 Enterprise) the IDE instability was caused by Castalia. I had to go into the registry and remove the key that causes the IDE to load the Castalia BPL. Before I did that, I had access violations on virtually every single key stroke I typed in the editor. After I removed Castalia completely from the IDE, it has been rock solid.