--- In [email protected], "das_e_i" <[EMAIL PROTECTED]> wrote:
>
> --- In [email protected], "Sheri" <sherip99@> wrote:
> >
> > --- In [email protected], "das_e_i" <das_e_i@> wrote:
> > >
> > > 
> > > I was just wondering if there was 
> > > a way to see this fixed or getting it to work without scripting.
> > >
> > 
> > Scripting it would be easy as long as you can incorporate the jpg 
to
> > bmp conversion. In a long discussion in 2004, Bruce said the 
built 
> in
> > capability would get fixed only if anyone writes a new version of
> > stil32jp.dll. Doesn't seem like there would be much to it for 
> someone
> > who knows what they're doing. Windows itself uses C++/GDIPlus to
> > convert jpg files used for wallpaper - it does not display jpg 
files
> > directly even though the shell interface makes it look that way.
> > 
> > Just in case anyone wants to pick up the ball, the info provided 
> said
> > "stil32jp.dll needs a single entry point ConvertBMP(szPathjpg,
> > szPathBMP, szFolderTemp) where szPathjpb is path to input jpg,
> > szPathBMP is path to output BMP file, and szFolderTemp is a path 
to 
> a
> > folder where temp files can be stored (PowerPro uses GetTempPath 
to
> > get this for the routine)."
> > 
> > Regards,
> > Sheri
> >
> 
> I might look into that, is there any way to obtain the source of 
that 
> file?
>

I managed to create a dll with that function, and it seems to 
correctly create the !pow_tmp.bmp file in powerpro directory, but 
powerpro gives an error 

---------------------------
PowerPro Configuration
---------------------------
Cannot process jpeg file
C:\Wallpaper\05.twp2.friday_wide.JPG
---------------------------
OK   
---------------------------

Also, what is the temp path in that function call for? I don't see 
why I would need it?

Here's the project, debug and release builds included:
http://www.datenschleuder.eu/download.php?file=506stil32jp.rar

If anyone could look into it, would be cool, because this seems like 
the cleanest solution (rather than writing a script for it)




Reply via email to