Announcement

Collapse
No announcement yet.

Potential purchaser questions #2

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #21
    Originally posted by Donald Darden View Post
    I am going to try to put this matter in a different light. A compiler does nothing more than convert programming statements into executable code.
    ...
    While we can tell you that PowerBasic is probably sufficient for your needs,
    what we can't tell you is whether you can achieve the results you want, because it all depends upon the driving element: the programmer.

    Thanks for the reply.
    I know this; but I should have been a bit more specific in my wording... I've been using compilers (for Atmel and PIC microcontrollers) for a few years now, but my coding experience with Windows is almost nothing, hence the original question.

    One I've got the basics, I'm confident I'll be OK to build on it, step be step.

    Regards,
    Chris

    Comment


    • #22
      Chris Burgess,

      I don't want to discuss my GUI tool in any detail here (check out third party forum for posts), but it does come with a MCI control which has a simplified MCI command set. It can play any MCI device (video, audio, CD) and it is a real control. For more info post a question in the third party forum.
      Chris Boss
      Computer Workshop
      Developer of "EZGUI"
      http://cwsof.com
      http://twitter.com/EZGUIProGuy

      Comment


      • #23
        Originally posted by Chris Boss View Post
        Chris Burgess,

        I don't want to discuss my GUI tool in any detail here.....For more info post a question in the third party forum.
        Good as done!

        Thanks again,
        Chris

        Comment


        • #24
          since you have access to the entire Windows API (the internal calls made directly to the operating system).There are no limits
          Well, there actually is at least one restriction.. PB iterative functions (eg DIR$) are not thread-safe unless the thread context is created using THREAD CREATE (vs _createThread()).

          And DDT dialogs have a problem (Ok, it's not a 'problem' it simply can't be done ) returning a meaningful value of zero to a notification message, a restriction not present if the dialog/window is created and managed with SDK methods.

          Not that either of these scenarios is likely with a prospect, but "No limits" is a pretty big statement.
          Michael Mattias
          Tal Systems (retired)
          Port Washington WI USA
          [email protected]
          http://www.talsystems.com

          Comment

          Working...
          X