COM and Printer

BackupUser · Post by **BackupUser** » Sat Feb 09, 2002 5:21 pm

Restored from previous forum. Originally posted by Kanati.

Thought you said we were gonna see this in 2.90. What's the new ETA?

Kanati

BackupUser · Post by **BackupUser** » Mon Feb 11, 2002 8:07 am

Restored from previous forum. Originally posted by Rings.

COM is supported, bur not fully.This is the point while there is no example for it.The New Command is OpenComPort.Handle it like a file.

NR=1
Result=OpenComPort(NR,"COM2:")
If Result
MessageRequester("Info","SERTEST",0)
UseFile(NR)
WriteString("Test")
CloseFile(NR)
EndIf

For Printer, no native PureBasic-commands yet.Have to use Windows-Api's

Getting better with a little help from my friends....thx Siggi

BackupUser · Post by **BackupUser** » Mon Feb 11, 2002 11:21 am

Restored from previous forum. Originally posted by Danilo.

I thought by "COM" the ActiveX-stuff is meant here... !?

cya,
...Danilo

(registered PureBasic user)

BackupUser · Post by **BackupUser** » Mon Feb 11, 2002 8:13 pm

Restored from previous forum. Originally posted by Kanati.

exactly... COM... not COMM.

ActiveX, OCX, ActiveX DLLs (especially these since it opens up VB dlls for PB use).

Kanati

BackupUser · Post by **BackupUser** » Mon Feb 11, 2002 11:02 pm

Restored from previous forum. Originally posted by TronDoc.

hmmmm..... COM has always refered to COM port
as in serial port as in PC computer serial port...
...just because somebody has come up with a new
usage for the name doesn't change the fact that
we need to be able to program to access our COM ports -jb

BackupUser · Post by **BackupUser** » Tue Feb 12, 2002 12:09 am

Restored from previous forum. Originally posted by Danilo.

Using VisualBasic DLLÂ´s with PureBasic ??

Ummmm... there is something wrong

cya,
...Danilo

(registered PureBasic user)

BackupUser · Post by **BackupUser** » Tue Feb 12, 2002 2:52 am

Restored from previous forum. Originally posted by PB.

> Using VisualBasic DLLÂ´s with PureBasic ??
> Ummmm... there is something wrong

I know where you're coming from, but calling a VB OCX is, in reality, no different
to calling a normal C++ DLL from PureBasic. They are both just third-party files
for calling... and I need to access a VB OCX quite badly!

PB - Registered PureBasic Coder

BackupUser · Post by **BackupUser** » Tue Feb 12, 2002 4:29 am

Restored from previous forum. Originally posted by Kanati.

I don't NEED to access VB dll's or OCXs, but it would sure simplify things. I don't want to have to relearn some things I do naturally in VB, in C++. COM objects are quick to program, and easy to use.

Kanati