Better check all your file paths in Sonar preferences and CCC settings.

Doktor Avalanche
Better check all your file paths in Sonar preferences and CCC settings.

They all look as they should.
I was wondering if this is caused by the problem with start menu not finding the correct path to my projects. So checking this out I selected a project that didn't have a tick in the path or the name. I opened it from Existing Projects and saved it. Then closed it. When the start menu appeared I reopened it with out a problem. I then pinned it. I closed Sonar down and reopened it and I was able to unpin the project.
But the icon is still just black.
End result, the problem with the path not found also seems to be causing the unpin problem on those projects. 

Doktor Avalanche

Notecrusher
You shouldn't have to read the ezine to learn how to not get something that wasn't there before. I had the previous start screen toggled off. I had it toggled off via the checkbox that was right on the old start screen itself, which is standard. Lots of s/w has start screens.

Don't take this wrong. I've read the above a few times and I really can't get a grip on what you are trying to get across. Ultimately though if you are saying people shouldn't need to read the ezines or documentation for whatever reason then you are plain wrong.. Sorry :)

You don't get it. If someone said "I shouldn't have to read the ezine to learn how to use a new feature", that would be wrong. That's not what I said. I said I had an existing feature toggled off. That feature was updated. The new start screen was FORCED ON. Not only forced on, but the standard mechanism for turning it off was removed, a standard mechanism which is used in s/w products across the spectrum (checkbox right on the screen). No one should have to read the ezine to find out that to make things AS THEY WERE you have to go into advanced settings. 
 
Hope that clears things up. 

You aren't using Gloucester or earlier any more.

The actual expected behaviour is in the documentation regardless of what your expectations may be. That's why they document stuff. Cheers..

Doktor Avalanche

The actual expected behaviour is in the documentation regardless of what your expectations may be. That's why they document stuff. Cheers..

The EXPECTED behavior is what I outlined above. It's when s/w DOESN'T behave as expected that one must turn to the documentation (or to learn something new, not the case here). GUI standards have a purpose. User friendly is desirable. 

Notecrusher
The EXPECTED behavior is what I outlined above.

 
I guess you know far better than the documentation you didn't read then. You win .

Doktor Avalanche

Notecrusher
The EXPECTED behavior is what I outlined above.

 
I guess you know far better than the documentation you didn't read then. 

You cut the salient point out of my post so you could troll like you always do.
 
IT'S A GUI STANDARD. Start screens, which boatloads of s/w feature, universally have a checkbox right on the screen to disable them. In fact Cakewalk have followed that same standard until a couple of days ago. 
 

Doktor Avalanche
You win .

 
This is meant to sound like you're leaving but you'll be back to troll me again. And again. And again. It's what you do. 
1. Troll me w/ insulting post.
2. Insist you've been nothing but fair and consiliatory and reasonable but I'm "not having any of it".
3. Promise that you're leaving.
Repeat until mod closes thread.

" It's when s/w DOESN'T behave as expected that one must turn to the documentation"
 
You seem to think it's your job to decide what is expected not Cakewalk. I suggest you go and apply straight away for the design and documentation team then.
 
BTW it might be what you think is "expected" and I'm sorry don't agree with you, I actually think Cake's done that bit right. But it neither matters what any of us think here, it is documented by the designers. So please stop arguing irrelevant points, it's documented so it's not down to what we think. If you think it should change, log an enhancement.
 
Please do me a favor, calm down and go read something. I said "you win" simply because it is clear you are not the sort to back down on the point, so much so you wind yourself up so much, you will then accuse others of trolling (clearly) and being "insulting". Don't be so silly.
 
Give it up... I have.

Doktor Avalanche
" It's when s/w DOESN'T behave as expected that one must turn to the documentation"
 
You seem to think it's your job to decide what is expected not Cakewalk. I suggest you go and apply straight away for the design and documentation team then.
 

Once again cutting out the same salient point from my post so you can troll me, for the THIRD TIME NOW. That is really extraordinary. But it's no accident. You can't answer so you must obscure. Must depict me as saying something that I'm not. GUI STANDARD Troll. GUI STANDARD.
 

Doktor Avalanche
 
Please do me a favor, calm down and go read something. I said "you win" simply because it is clear you are not the sort to back down on the point, so much so you wind yourself up so much, you will then accuse others of trolling (clearly) and being "insulting". Don't be so silly.
 
Give it up... I have.

 
mmm hmmm.
1. Troll me w/ insulting post.
2. Insist you've been nothing but fair and consiliatory and reasonable but I'm "not having any of it".
3. Promise that you're leaving.
Repeat until mod closes thread.
 
 
 

rwheeler

Anderton
 
I wish more people would read the release eZine, many of the questions posed in the forum after release are answered in there.

Although I had looked at the update summary page, I realized this is not the same as the "release eZine." But it was quite the adventure trying to find the eZine. Searching knowledge base for "eZine" yields links to some for earlier release eZines but not the most recent one (yet). The link on the summary page is disguised as "based on" a pdf file, but no mention of the term "eZine" there.
 
The eZines have great information. I suggest having someone make an easy-to-find page with direct links to all the eZines, or else have a sticky link near the top of the forum with the collection of those links.
 
Over time it might be advantageous to add an annual summary eZine that lists all the improvements made from January through December. Could be a useful marketing tool as well as a useful bit of reference information.

It's awkward to say, but I'm not even sure what the eZine is. Is that the announcement that comes with the release when a monthly release goes live? If so, I'm reading that each time. If it's some other reference page I don't know about it. In either case, if The bakers would like us to learn from the "eZine" it would be helpful if more obvious links or references to it showed up.