Problem:
This is a bit of an old issue I had a long time ago, but I thought it could save you some time. At the time I was using PDT 1.0.0, a decent performer I must admit, with a lot of external files on remote Samba shares mapped as virtual drives. Some of them were outside of the project scope. A lot of debugging hours were spent to pinpoint the root of the problem – occasionally changes in the remote files were not saved at all. Probably when working with standalone files (not within the project tree) and only with .php editor, I didn’t have the occasion to successfully reproduce it on a 100% basis, so it’s more of a guess or maybe just a sheer coincidence – I’m not sure about it.
Workaround:
For a time a no-brainer solution was to either use Aptana editor or limit editing to local files.
Solution:
Some half a year later (I had a break with PDT for quite a time), the same system configuration and stuff – the only thing changed is Eclipse and PDT updated to their latest, greatest versions – not a problem any more. I’ve rechecked the changelogs – couldn’t find any corresponding bug within fixed issues list. Seemingly, it either got fixed with some other commit or it could have been some more complex issue – maybe involving platform internals – who knows? What’s important - it works! Thank you for the Eclipse team.
Summaries:
Problemy z dźwiękiem w GRAW2 często można rozwiązać przez zmianę trybu renderowania audio na "Generic Software".
Problem:
At times when playing GRAW2 the dialogues get lost and there’s no sound being played at all, though environmental FX are still OK. And it’s not the case of the “tank sound bug” known from the GRAW1. My audio card is a good, old Sound Blaster Live! Value.
Solution:
GRAW1/2 always had some problems with EAX support or general audio glitches (at least with my configuration, yep I know – not a top-notch audiophile sound hardware, but it’s sufficient for all my daily needs). But this time enabling EAX allowed me to hear the dialogues properly, though only for a while. Then the issue recurred. However switching to “Generic Software” audio renderer resolved the problem completely. Anyway, why the heck couldn’t they provide a subtitling option? Dunno.
Summaries:
Usunięcie konta Google Analytics nie jest takie proste, jak by się mogło wydawać. Należy się skontaktować bezpośrednio z działem supportu Google. Na szybko można jednak zmienić nazwę dezaktywowanego konta na przykładowo [WYŁĄCZONY]example.com, co pozwala uniknąć wyświetlania go jako domyślnego konta w profilu.
Update:
Zmieniony został schemat sortowania stosowany przez Google. Zamierzony efekt można uzyskać przez użycie prefiksów [A]example.com dla aktywnych kont, [D]example.com dla kont nieaktywnych lub poprzez dopisanie ciągu typu 'ZZZ' przed nazwą nieaktywnego konta.
Drugi update:
W końcu sprawa została rozwiązana przez zespół Google poprzez wprowadzenie odpowiedniej opcji w ustawieniach konta.
Problem:
I had some problems recently with my Google Analytics account not gathering data from one of my websites, though the tracking code seemed all right. I’ve even checked for possible conflicts with 3rd party scripts, but to no avail. I thought I would recreate the account. In fact it helped, but I was left with a cluttered Google profile as I couldn’t find any mean to delete the old one (and I have my websites held in separate accounts).
Solution:
A quick look into the Google Analytics Help Center revealed it’s not that straightforward, but possible. Just check those articles: “How do I delete my Analytics account?“or “I would like to cancel my Google Analytics account“. It seems you can disable tracking and then file a removal request to the Google support team. Lazy as I am at times, I wanted some instant fix without the burden of contacting Google on such a trifling matter. You could say I should just remove my profile from the users in the Access Manager, but being the only administrator would involve transferring the account to some bogus profile, which is just an unnecessary waste of time.
Workaround:
For the time being it looks like changing the account’s name to [DISABLED]example.com does the job. Dirty, but quick. Google appears to load the first account in lexicographical order as default. Till the moment it gets too messy, I can live with that. And maybe then will I try hounding the poor guys from Google.
Update:
As of July Google changed the lexicographical order processing. No longer do [DISABLED] tags work as desired. All non alphanumeric characters seem to be sorted in precedence. So the way to go now is either prefixing good accounts with some dots or the like (f.e. [A]example.com for active, [D]example.com for old accounts) or adding some ‘ZZZ’ prefixes to the undesired accounts’ names.
2nd update:
This issue has finally been fixed by Google team.
Recent Comments