Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: Interfacing Windows SDK HelloWin

  1. #11
    Super Moderator Petr Schreiber's Avatar
    Join Date
    Aug 2005
    Location
    Brno - Czech Republic
    Posts
    7,129
    Rep Power
    732

    Re: Interfacing Windows SDK HelloWin

    This is fantastic example Charles,
    hardcore work - but still well structured.


    Petr
    Learn 3D graphics with ThinBASIC, learn TBGL!
    Windows 10 64bit - Intel Core i5-3350P @ 3.1GHz - 16 GB RAM - NVIDIA GeForce GTX 1050 Ti 4GB

  2. #12
    thinBasic author ErosOlmi's Avatar
    Join Date
    Sep 2004
    Location
    Milan - Italy
    Age
    57
    Posts
    8,793
    Rep Power
    10

    Re: Interfacing Windows SDK HelloWin

    Well, bundled exe will delete all exploded files if flag for deletion is on. So if you include "o2asm.data" file, it will be deleted.

    I still prefer one of my suggestions (or any other that will not create extenal dependancies) because this creates very few confusion to users both for testing and for script distribution. But how to go with module is up to you.

    Ciao
    Eros
    www.thinbasic.com | www.thinbasic.com/community/ | help.thinbasic.com
    Windows 10 Pro for Workstations 64bit - 32 GB - Intel(R) Xeon(R) W-10855M CPU @ 2.80GHz - NVIDIA Quadro RTX 3000

  3. #13

    Re: Interfacing Windows SDK HelloWin


    Yes Eros, I agree, from the modular point of view it makes sense to reduce external bits and pieces, so I will incorporate the soft coded instructions back into the Oxygen Module - after all the full source code is provided - easy to mod, so my conscience is clear

    I think it is unlikely that anyone will need to customise the op codes for a particular application .- they have to be industry standard.

    Should be ready later today.


  4. #14
    thinBasic author ErosOlmi's Avatar
    Join Date
    Sep 2004
    Location
    Milan - Italy
    Age
    57
    Posts
    8,793
    Rep Power
    10

    Re: Interfacing Windows SDK HelloWin

    Quote Originally Posted by Charles Pegge
    ... so my conscience is clear
    Well, your conscience will be always clear.
    You have provided a so great module with full source code (repeat, full source code ! ) and functionalities that you've got credits for at least 10 years!


    www.thinbasic.com | www.thinbasic.com/community/ | help.thinbasic.com
    Windows 10 Pro for Workstations 64bit - 32 GB - Intel(R) Xeon(R) W-10855M CPU @ 2.80GHz - NVIDIA Quadro RTX 3000

  5. #15

    Re: Interfacing Windows SDK HelloWin

    Phew! that wasn't too bad. No more o2asm.data. Updated in time for your next release I hope.

    There's a substantial amount of test material now which really helps with quickly verifying software mods.

    Eros if you flatter me too much my head will no longer fit my hat and I will have to get a new head!

  6. #16
    thinBasic MVPs
    Join Date
    May 2007
    Location
    UK
    Posts
    1,427
    Rep Power
    160

    Re: Interfacing Windows SDK HelloWin

    Here is some old stuff I found which you might be interested in looking at Charles.
    Home Desktop : Windows 7 - Intel Pentium (D) - 3.0 Ghz - 2GB - Geforce 6800GS
    Home Laptop : WinXP Pro SP3 - Intel Centrino Duo - 1.73 Ghz - 2 GB - Intel GMA 950
    Home Laptop : Windows 10 - Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 2401 Mhz, 2 Core(s), 4 Logical Processor(s) - 4 GB - Intel HD 4400
    Work Desktop : Windows 10 - Intel I7 - 4 Ghz - 8GB - Quadro Fx 370

  7. #17

    Re: Interfacing Windows SDK HelloWin

    Thanks Abraxas. It's mostly 16 bit DOS but there is a windows 95 32 bit demo in the 'companion disk' folder, using TASM with macros and prototypes.

Page 2 of 2 FirstFirst 12

Members who have read this thread: 0

There are no members to list at the moment.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •