Here you go guys: http://thief.miranda-im.org.ua/advsplashscreen.zip
Now everything seem to work perfectly with your AdvSplashScreen.dll v.0.1.2.0 [17 May 2007] - Splash Screen and Miranda build 28
I have copied AdvSplashScreen.dll into Plugins while Miranda running and in Options, go to "Plugins" to check that DLL recognized... and Miranda crashes instantly.
Also, one bugreport: "preview" shows splash only first time I press that button. Any sequential actions on that button just send Options page off from focus.
Also, there's a StartupSound plugin.
I think it is a good idea to merge it into Your code. And forget about "was too buggy" MP3 support completely ;)
Oops... *confused* no tabstops on config screen?
Also... (idea only) how about to reorder display/fade options to more solid state?
Just keep enough space between checkbox and input field for translators.Code:[x] Fade in, steps [___] Display time [_____] msec [x] Fade out, steps [___]
Last edited by ANR Daemon; 21 May 2007 at 11:16 AM.
 and yes, options dialog needs some love.
Last edited by Thief; 21 May 2007 at 11:22 AM.
It is actually startup for me even if I use dbx_3x, which starts incredible slow with my 50mb+ DB. Just made a test. With dbx_mmap sound starts playing when splash screen stop fading in. About 1-1.5 sec after miranda start. With dbx_3x it was a bit later. Like 3 sec. Which is not a big deal for me (I have fadein:20 delay:5000 fadeout:3)I've looked into the code of that plugin and its not gonna work because uses Miranda services. So sound is not really "startup", my plugin uses the same code as Miranda service just it fires on plugin run. What about mp3 though?
So I think it is not a real difference, when and how sound playing.
As a user, I see only one common difference.
It configurable in common place and use common technique to produce result.
I mean - it adds standard entry to Sounds tree and emit event when it loaded by Miranda Core.
It not dependent to any external service like AdvSplashScreen so it "just work".
It even require some updates as code changes, so it not independent... Anyway it was just a suggestion.
I think that shold be better choice for users, but it is Your plugin, so... :)
I'll wait for that debug build You announced in previous posts.
It may be just minor problem, or it may be core problem too.. So I think that investigation of this crash is required.