| View previous topic :: View next topic |
| Author |
Message |
Captain Jake Guest
|
Posted: Sat Jun 11, 2005 3:21 am Post subject: Yet More D7 Gripes |
|
|
There seems to be an odd intermittent bug in D7 that randomly marks a buffer
as Read Only and doesn't allow it to be changed back to read-write until it
is closed and reopened. This stupid very annoying bug is rather rare but when
it happens it nearly always causes some work to be lost.
--
***Free Your Mind***
|
|
| Back to top |
|
 |
Florian Necula Guest
|
Posted: Sat Jun 11, 2005 3:55 am Post subject: Re: Yet More D7 Gripes |
|
|
"Captain Jake" <jake[nospam]@jsnewsreader.com> wrote:
| Quote: | There seems to be an odd intermittent bug in D7 that randomly marks a buffer
as Read Only and doesn't allow it to be changed back to read-write until it
is closed and reopened. This stupid very annoying bug is rather rare but when
it happens it nearly always causes some work to be lost.
|
I can confirm this. It is in D6 too. However it is not quite random, it appears when
there are some syntax errors. It seems to be related to the kibitz compiler.
Best regards,
Florian Necula
Cresco Software (www.crescosoft.com)
Home of "Compass for Delphi" - code browsing/refactoring
|
|
| Back to top |
|
 |
John Kaster (Borland) Guest
|
|
| Back to top |
|
 |
Dave Nottage [TeamB] Guest
|
Posted: Sat Jun 11, 2005 11:42 am Post subject: Re: Yet More D7 Gripes |
|
|
Captain Jake wrote:
| Quote: | There seems to be an odd intermittent bug in D7 that randomly marks a
buffer as Read Only and doesn't allow it to be changed back to
read-write until it is closed and reopened. This stupid very annoying
bug is rather rare..
|
I know... it annoys me on rare occasions, too.
| Quote: | but when it happens it nearly always causes some
work to be lost.
|
It never causes loss of work for me. How come it does for you?
--
Dave Nottage [TeamB]
|
|
| Back to top |
|
 |
Rudy Velthuis [TeamB] Guest
|
Posted: Sat Jun 11, 2005 11:57 am Post subject: Re: Yet More D7 Gripes |
|
|
At 05:21:44, 11.06.2005, Captain Jake wrote:
| Quote: | There seems to be an odd intermittent bug in D7 that randomly marks a
buffer as Read Only and doesn't allow it to be changed back to
read-write until it is closed and reopened.
|
This only happens to me (also in D2005) when there was some kind of weird
IDE or compiler error first. The first time I can usually reset the flag,
but the second time, I can't, and have to close and reopen the file.
--
Rudy Velthuis [TeamB] http://velthuis.homepage.t-online.de
"... one of the main causes of the fall of the Roman Empire was that,
lacking zero, they had no way to indicate successful termination of
their C programs." -- Robert Firth
|
|
| Back to top |
|
 |
Rudy Velthuis [TeamB] Guest
|
Posted: Sat Jun 11, 2005 11:58 am Post subject: Re: Yet More D7 Gripes |
|
|
At 05:55:41, 11.06.2005, Florian Necula wrote:
| Quote: | I can confirm this. It is in D6 too. However it is not quite random, it
appears when there are some syntax errors. It seems to be related to
the kibitz compiler.
|
That could be, indeed.
--
Rudy Velthuis [TeamB] http://velthuis.homepage.t-online.de
"Everywhere I go I'm asked if I think the university stifles writers. My
opinion is that they don't stifle enough of them."
- Flannery O'Connor (1925-1964)
|
|
| Back to top |
|
 |
Lars Black Guest
|
Posted: Sat Jun 11, 2005 12:59 pm Post subject: Re: Yet More D7 Gripes |
|
|
| Quote: | There seems to be an odd intermittent bug in D7 that randomly marks a
buffer
as Read Only and doesn't allow it to be changed back to read-write until
it
is closed and reopened.
|
I have this once in a while in D6 but I can just right-click in the editor
windows and unclick the Read-only options..
Cheers,
Lars
|
|
| Back to top |
|
 |
Frank de Groot Guest
|
Posted: Thu Jun 23, 2005 9:46 pm Post subject: Re: Yet More D7 Gripes |
|
|
"Rudy Velthuis [TeamB]" <velthuis (AT) gmail (DOT) com> wrote
| Quote: | I can also imagine that some employers wouldn't like it if their
employees bitch about other companies, no matter which one.
|
And to avoid that Borland does what they did to me (contact my employer), he
is clever and avoids Borland's nasty tactics.
|
|
| Back to top |
|
 |
|