Re: Xcode 4.2 - compliments for C++ development -- and some wonders
Re: Xcode 4.2 - compliments for C++ development -- and some wonders
- Subject: Re: Xcode 4.2 - compliments for C++ development -- and some wonders
- From: Joar Wingfors <email@hidden>
- Date: Sun, 25 Dec 2011 23:19:58 -0800
On 2 dec 2011, at 23:55, Ruslan Zasukhin wrote:
> I will be happy collaborate with you if that's okay in nearest weeks to
> provide more feedback. Or may be do bug reports...
>
> We all want xcode be best of the best!
> I personally very want, because I am tithed to hear from our Windows guys,
> Xcode cannot do this or that (auto-completion glitches v3.x, debugger) ...
> Although even they for years told, IDE itself looks ideal.
>
> If some points better discuss off list - please let me know.
Our goals are perfectly aligned - We also want to see Xcode be the best of the best! :-)
Anything that's of general interest can be discussed here on the mailing list. Anything that's related to pre-release software need to be directed to the web based forums at <http://devforums.apple.com/>. In addition to that, please remember that the only way to make sure that your bug reports / enhancement requests will end up being considered for upcoming releases of Xcode, is to file formal bug reports:
<http://developer.apple.com/bugreporter/>
<snip>
> At least you must be able see also
> A) RAM is not very good cleaned after indexing. We need quite xcode to make
> things better.
> B) few crashes was right after indexing.
While you should typically expect that we already have bug reports for anything that you encounter in our products, please make sure that you file bug reports as well. You never know when you'll be the first to report some issue that may be specific to your particular configuration, or when you happen to be the one to provide that key bit of information that allows us to finally track down and fix some more common problem. The more bug reports we get, the easier it is for us to make Xcode great and to best suite your needs.
On 3 dec 2011, at 02:18, Ruslan Zasukhin wrote:
>>> 2) Schemas ...
>>>
>>> Idea itself is good made ... Just not clear to me, why we see schemas also
>>> from sub-projects?
>>>
>>> Yes, we do not use WorkSpaces, we have just converted 15-20 our existed
>>> XCODE 3.x projects. And most projects contains one or few other.
>>>
>>> I just set DO NOT SHOW for all schema of sub-projects...
>>> I have try delete them, but this delete the in sub-project itself.
>>>
>>> May be we need change mind ... But so far looks strange.
>>
>>
>> The idea with showing schemes from referenced projects is that you may want to
>> get access to them without having to open the referenced projects separately.
>> This is perhaps most obvious for projects that are referenced from a
>> workspace, but I think that the idea holds up in general. You can use the
>> scheme management sheet to configure which schemes that you want to see in
>> your project / workspace.
>
> And on this way also problem.
>
> If in Workspace A, I set NOT VISIBLE for some targets of project P1,
>
> Then Workspace B also will change visibility of this targets. Oops.
That sounds like a legitimate problem. Per-workspace control over the visibility of schemes sounds desirable for certain workflows. Please file a bug report!
Thanks,
Joar
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden