I’ve entered with BetaBugs Duckling Compressor and RoughDraftAudio PanGloss, and theres another 39 entries to try (if you have a mac as well :))
Download fest now, voting starts next week 🙂
My main test host was, of course, Podium 😉 Altho’ it must be said, Frits, that Podium doesn’t like being run from a debugger, which is a nuisance! I understand why it’s the case, but it means I have to use a whole bunch of Assertions when there are problems…
Podium doesn’t like being run from a debugger, which is a nuisance! I understand why it’s the case
I haven’t put in any code that should block debugging. What is the problem/case?
Sorry to have taken so long to get back to you on this, Frits..
If I set Podium to be the ‘host’ application in the delphi IDE, and hit run, I get a message box hidden behind the logo, before the logo has had chance to paint itself.
Debugger Fault Notification
Project C:Program FilesZynewavePodiumPodium.exe faulted with message: ‘access violation at 0x7c901010: read of address 0x00000618’. Process Stopped. Use Step or Run to continue.
The CPU view in the debugger is highlighting ntdll.RtlEnterCriticalSection; sadly I can’t get a stack trace to say what functions were being called.
It’d be really handy to have debugging back, I can’t remember when it stopped working, but I seem to recall it being a build earlier this year, maybe Easter time, but I could be wrong…
I remember something changed in my debugging as well back when I added support for dragging files from plugins/file explorer onto tracks. I implemented the IDropTarget interface, which has had the effect that my debugger halts when I drag a file over Podium. Maybe that is the cause for your Delphi debugger problem too.
I happen to have my old laptop set up as a VM on my new laptop. I tried the debugging on that, using v1.70 that is installed on it – worked a treat.
So, it would seem that the interfacing might be the problem..
a quick google reveals nothing much – hooray!! can the implementation of the class be delayed.. I guess not, since it’s part of the form itself, isn’t it.. unless the parts of the constructor can be wrapped in a try/catch block.. i dunno!