Page 3 of 4
Posted: Tue May 04, 2004 5:16 pm
by Fred
I just tried it and it seems to work. Do you have a snippet where it fails ?
Posted: Tue May 04, 2004 7:20 pm
by GPI
PolyVector wrote:From the MSDN:
S_OK
The COM library was initialized successfully on this thread.
S_FALSE
The COM library is already initialized on this thread.
Maybe there's something I'm missing here?
BTW: Where is the problem:
#S_OK: Initalized successfull -> You can use it
#S_FALSE: Allready initalized -> You can use it
Or do i missunderstand something?
Posted: Tue May 04, 2004 10:01 pm
by PolyVector
@Fred/Everyone
I was wrong about it being PB... It was actually the EC OLE Image Plugin.... Which is very odd seeing as I was using this plugin long before this beta version...???
Code: Select all
UseEC_OLEImageDecoder()
Ret=CoInitialize_(0)
Select Ret
Case #S_OK
Debug "#S_OK"
Case #S_FALSE
Debug "#S_FALSE"
EndSelect
Try commenting out the UseEC_OLEImageDecoder() line to see what I mean...
@GPI
I did say I was using the code:
Code: Select all
if CoInitialize_(#NULL)=#S_OK
;/Do something
It's only a problem if it isn't documented that COM is already initialized...
Posted: Wed May 05, 2004 2:18 am
by Raven
Visual C++ support. This should come in very useful indeed.
I know it is a simple request (and yes i know someone will post the ASM work around), but is there a chance you could add the VOID type that C has. It is a sorely missed type, especially when dealing with C libraries.
Posted: Wed May 05, 2004 2:31 am
by El_Choni
That plugin initializes COM access at program start, because it needs it, and uninitializes it at program end. There shouldn't be any problem with it as long as your own CoInitialize has a corresponding CoUninitialize.
However, be sure to use the last version of the plugin (2.3)
Posted: Wed May 05, 2004 2:50 pm
by dell_jockey
Raven wrote:I know it is a simple request (and yes i know someone will post the ASM work around), but is there a chance you could add the VOID type that C has. It is a sorely missed type, especially when dealing with C libraries.
The VOID type would be very welcome indeed, especially so if we would also get
type casts.
Posted: Fri May 07, 2004 11:21 pm
by freak
Please no bugreports here, they will probably be overlooked.
moved here: =>
viewtopic.php?t=10789&highlight=
Timo
Posted: Sat May 08, 2004 12:09 pm
by Ralf
nice work fred!
Mac Osx Version
Posted: Mon May 10, 2004 10:10 am
by echnaton
Hi,
is there a beta Version for Mac OS X ?
Im a willing Betatester
)
Re: PureBasic 3.91 Beta 1
Posted: Sat May 15, 2004 6:31 am
by KarLKoX
Fred wrote:(Visual C++ lib are now accepted
They were allready accepted, at least, i get no problems to use them since i use purebasic (3.61 or so), but now it is official
Btw, PellesC can't compile my userlib written in C but lcc does, this compiler does strange things :roll:
Posted: Sat May 22, 2004 9:56 am
by Psychophanta
Hi to all PB team, and to all users PBadmirers & lovers.
Thanks again Fred
Posted: Sat May 29, 2004 1:11 am
by waffle
I wonder if the visual c++ thing is part of fred's plan to import a vc++ directx lib directly into PB .....
nuclearglory has a pretty good collision system, but its in vc++ and i'm not sure how to use it in PB. Perhaps all this will change in version PB4
Posted: Wed Jun 09, 2004 7:01 pm
by Beach
I was able to compile true color icons before this beta release. Is there something I need to do to turn this back on? Here is an example (posted in another thread)
Thanks!
Posted: Wed Jun 09, 2004 9:17 pm
by GPI
Beach wrote:I was able to compile true color icons before this beta release. Is there something I need to do to turn this back on? Here is an example (posted in another thread)
Thanks!
The problem is porc, which doesn't support 24-bit-Icons.
Posted: Fri Jun 11, 2004 1:44 pm
by Fred
Is it possible to get this icon or another one which fails ? The XP like icons we tried seems to be behave correctly. Thanks !