Re: First click ignored
Re: First click ignored
- Subject: Re: First click ignored
- From: David Ewing <email@hidden>
- Date: Fri, 5 Dec 2003 11:35:30 -0700
On Dec 5, 2003, at 6:34 AM, Bill Cheeseman wrote:
For quite some time (back into beta days), I have noticed that Xcode
ignores
the first click in many circumstances. Actually, it ignores several
"first
time" actions, so it might not just be a click issue.
I am curious to know if everyone experiences this. I haven't seen it
mentioned, so it occurs to me that it may be something else on my
system
that is causing this very annoying problem.
Examples:
I click in a source file to place the text insertion point, but it
doesn't
"take." When I start typing, the text is inserted wherever the text
insertion point was last located.
I don't seem to see this. It would be good to file a bug with very
specific instructions on how to reproduce this at
<http://developer.apple.com/bugreporter>.
I try to reduce two adjacent space characters to a single space
character by
hitting the delete key while the insertion point is located after the
second
space character. Both space characters are deleted, and I have to type
the
space bar once to reinsert a single space character. (Maybe this is a
different issue.)
This is a known issue.
I edit my source files, then click the build button. The project asks
me to
save the edited files, which I do, and it then builds. But the error
messages are based on the source file as it existed before the edits I
just
saved. I have to hit the build button a second time to get the build
system
to recognize the edited source files.
There was a known issue where the temporary text from an in-progress
code completion would end up being compiled into a file when
speculative compilation was turned on. This is fixed for our next
release. If this isn't what you're seeing, then please also file a bug
for this as well.
Oddly, the first two issues sometimes (but not always) hit me when I'm
typing in TextEdit or some other application, but apparently only
after or
while I've been using Xcode.
Is Xcode making on-the-fly changes to system routines related to text
editing, and failing to remove them when I switch to another
application?
What's going on?
The first issue could certainly be a general Cocoa issue. That wouldn't
surprise me. But the second issue should certainly only be happening in
Xcode. If you see something similar in TextEdit then please file a new
bug for it - it can't be the known Xcode issue.
Dave
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.