Hi Brian
This is truly a good news, very glad that we have a replacement of old PB in 64bit . The question is how much do we have
to pay for this Beta product of yours , what's the asking minimum pricing per year  etc?

Brian

I would avoid to make twice the same error, using a compiler that is based on the work of a single man (Zale's syndrom).

Fortunatly if you know C/C++ yourself, then you will be able to find a paid job to make your living, and keep working on PluriBASIC in your spare time.

But obviously the first thing to figure out, is:
Does there is still a market for programmers using the PowerBASIC proprietary DDT syntax ?

If i remember well, you are young, while most DDTers are already too old or retired to make a living from them.

I am realy upset when i see a young talented programmer wasting time with beached whales.

 I would not get too excited about the c++ implementation. I only tested with MINGW and im
not sure if i will continue with it's implementation. It is very time consuming working in two
implementations.

I'd rather be exited because the Oxygen implementation supports some c++ directly. Almost nothing
stops you from using the statements that oxygen supports already. Im not ture but i think Oxygen
also supports c++ dlls. Thats why i might drop directly c++ implementation, because it is already
present in Oxygen.

Yes, i contacted Adam Drake, he's a good guy but he is very busy. He kindly granted permission to
promote and sell PluriBASIC in the PowerBASIC forums.

What C++, Visual Studio ?

Where are you living ?

Did you try to contact Drake ?

 Hello Patrice, The most advanced implementation is for OxygenBASIC, but it also supports C++.

It is not easy to work on both implementations though.

Brian

What is the current underlaying compiler used by PluriBASIC 64 ?

 After watching this thread, i thought i should try something. Please see this:

https://forum.powerbasic.com/forum/user-to-user-discussions/third-party-addons/pluribasic/788817-pluribasic-64bit-compilations

If you want to be able to compile PowerBASIC code and even mix it with some of the C++ code... please support.

Hello Everyone.

I dont know if what im about to write makes sense or if i am losing my mind, but please bear with me.

I have a Version of PluriBASIC that already can compile some of the PowerBASIC source code to 64bit
executables, and what is missing is nothing when compared to what i already did.

I already got permission to promote it in the PowerBASIC forums, but it is incomplete and i dont seem
to be able to get the time to finish it.

Here goes the crazy thing... i was wondering if there are enough people interested in the forums (or one
patron with enough funds) to raise a pre-sale and raise 2000 to 3000 USD. I would be charging $ 50.00 for
a yearly subscription to PluriBASIC. I am willing to quit job/ask a couple months off to get it to an acceptable
state, good enough to sell licenses. But for this i would need to get an alternate way to pay bills and survive
until done.

PluriBASIC already exists and works acceptably well. It is a shame that it is in the shelf because of my day
job. It has been almost ready for months. What is missing are just fractions of the core features. While it already
supports most of the DDT statements, not all of them will be supported (although at some point the engine may
upport the syntax so that everybody can write the core code to make them work).

The ideal thing is that with the same version of PluriBASIC everyone can compile PowerBASIC, Android and PHP
code (It already does for simple projects, but portions of code are still missing).

Also the idea is that, when ready, I would like to listen to the community to expand the language and add new
features (it already has extended features too). If i get enough support and see it is viable, i will put a link to purchase
what i already got. The supporters/purchasers (any of them) will have the option to be part of a beta team and
participate in a forum specially for this purpose. Not obligatory of course.

This may be too far fetched because i would need to sell around 60 presale licenses of a product that while it is not
terribly broken, is is not complete... so, i might not pull it off. But as i said, it is a shame the PluriBASIC is in the
shelf at the advanced state it is in, i i thought i should at least try to do it.

Please email me at pluribasic@hotmail.com and let me know if you can aquire a pre-sale license or donate to
the cause, after that i will evaluate if it is viable.

With all respect to everybody.
Brian Alvarez.

Sorry, but without documentation and examples I can't guess how to use this OCX.

Hello,
I'm new to this forum and maybe I'm posting in the wrong folder.

I use PowerBASIC and connecting the code to measurement equipment hardware. This often comes with ocx and dot-net libraries. I attach a bit of code, the inc file was written with the PowerBASIC com browser. Since weeks I struggle with calls to interfaces which are marked by "This Interface cannot be created directly it can only...".

The AIfeauture calls work, but not the IAnalogChannel.


I googled a lot but did not find a hint.

Thanks!


----  some lines of CODE --------------------
' Generated by: PowerBASIC COM Browser v.2.00.0087
' Date & Time : 15.01.2020 at 14:54
' Options:
' Always use an Interface Prefix : Off
' Interface Prefix               : Int_
' Prefix ProgIDs, ClassIDs...    : On
' Use ANSI Strings               : Off
' Use Singular Enumerations      : Off
' Generate Dispatch Interfaces   : Off
' Include Parameter Names        : On
' Use Property Get/Set statements: On
' ------------------------------------------------
' Library Name: BDaqOcxLib
' Library File: C:\WINDOWS\SysWow64\BDaqOcx.dll
' Description : Advantech DAQNavi Device ActiveX Controls
' GUID : {1752FF26-D6C9-4BC8-BFE9-7D0CA26DED89}
' LCID : 0
' Version : 1.0

' Version Dependent ProgIDs
$PROGID_BDaqOcxLib_InstantAiCtrl1 = "BDaqOcx.InstantAiCtrl.1"

....
.........  some CODE ........


' Interface Name  : IAiFeatures
' Description     : Interface IAiFeatures
' This Interface cannot be created directly it can only
' be returned by a Method or Property in this library.
INTERFACE IAiFeatures $IID_BDaqOcxLib_IAiFeatures
    INHERIT IDISPATCH

    PROPERTY GET Resolution <1> () AS LONG
    PROPERTY GET DataSize <2> () AS LONG
    PROPERTY GET DataMask <3> () AS LONG
    PROPERTY GET ChannelCountMax <4> () AS LONG
    PROPERTY GET ChannelType <5> () AS LONG
    PROPERTY GET OverallValueRange <6> () AS INTEGER
    PROPERTY GET ValueRanges <7> () AS DWORD
    PROPERTY GET BurnoutDetectSupported <8> () AS INTEGER
    PROPERTY GET BurnoutReturnTypes <9> () AS DWORD
    PROPERTY GET ThermoSupported <10> () AS INTEGER
    PROPERTY GET CjcChannels <11> () AS DWORD
    PROPERTY GET BufferedAiSupported <12> () AS INTEGER
    PROPERTY GET SamplingMethod <13> () AS LONG
    PROPERTY GET ChannelStartBase <14> () AS LONG
    PROPERTY GET ChannelCountBase <15> () AS LONG
    PROPERTY GET ConvertClockSources <16> () AS DWORD
    PROPERTY GET ConvertClockRange <17> () AS MathInterval
    PROPERTY GET BurstScanSupported <18> () AS INTEGER
    PROPERTY GET ScanClockSources <19> () AS DWORD
    PROPERTY GET ScanClockRange <20> () AS MathInterval
    PROPERTY GET ScanCountMax <21> () AS LONG
    PROPERTY GET TriggerSupported <22> () AS INTEGER
    PROPERTY GET TriggerSources <23> () AS DWORD
    PROPERTY GET TriggerActions <24> () AS DWORD
    PROPERTY GET TriggerDelayRange <25> () AS MathInterval
    PROPERTY GET Trigger1Supported <26> () AS INTEGER
    PROPERTY GET Trigger1Sources <27> () AS DWORD
    PROPERTY GET Trigger1Actions <28> () AS DWORD
    PROPERTY GET Trigger1DelayRange <29> () AS MathInterval
END INTERFACE

' Interface Name  : IAnalogChannel
' Description     : Interface IAnalogChannel
' This Interface cannot be created directly it can only
' be returned by a Method or Property in this library.
INTERFACE IAnalogChannel $IID_BDaqOcxLib_IAnalogChannel
    INHERIT IDISPATCH

    PROPERTY GET Channel <1> () AS LONG
    PROPERTY GET ValueRange <2> () AS LONG
    PROPERTY SET ValueRange <2> (BYVAL pVal AS LONG)
END INTERFACE

' Interface Name  : IAnalogInputChannel
' Description     : Interface IAnalogInputChannel
' This Interface cannot be created directly it can only
' be returned by a Method or Property in this library.
INTERFACE IAnalogInputChannel $IID_BDaqOcxLib_IAnalogInputChannel
    INHERIT IDISPATCH

    PROPERTY GET Channel <1> () AS LONG
    PROPERTY GET ValueRange <2> () AS LONG
    PROPERTY SET ValueRange <2> (BYVAL pVal AS LONG)
    PROPERTY GET SignalType <3> () AS LONG
    PROPERTY SET SignalType <3> (BYVAL pVal AS LONG)
    PROPERTY GET BurnoutRetType <4> () AS LONG
    PROPERTY SET BurnoutRetType <4> (BYVAL pVal AS LONG)
    PROPERTY GET BurnoutRetValue <5> () AS DOUBLE
    PROPERTY SET BurnoutRetValue <5> (BYVAL pVal AS DOUBLE)
END INTERFACE


.........

.....

' calling program

' some code...


    GLOBAL myOb  AS IInstantAiCtrl
    GLOBAL AnalogChannel() AS IAnalogInputChannel


'-------------------------------------------------------------------------------------------
CALLBACK FUNCTION Test_Callback () AS LONG
    LOCAL SendText AS ASCIIZ * 1024
    LOCAL Result AS LONG
    LOCAL ic AS LONG
    LOCAL hListBox AS DWORD
    LOCAL i AS LONG

    IF CB.MSG = %WM_COMMAND AND CB.CTLMSG = %BN_CLICKED THEN

    irun=1

    DO
       CONTROL SET TEXT CB.HNDL ,%IDC_dumplabel, "Los"
    ChaNo=1
        ercode= myOb.ReadChannel(0,Datx)
        CONTROL SET TEXT CB.HNDL ,%IDC_Ch0, STR$(Datx)
    END IF
....

END FUNCTION

....

'some code .................

    LET myOb = NEWCOM  $PROGID_BDaqOcxLib_InstantAiCtrl

    devMode1= myOb.ProductId
    ? "Product ID " & STR$(devMode1)


' more code.............