Aaron,
Glad to hear, because often in VB I'll use API calls rather than adding
the extra baggage involved in loading in a new VB control. For example,
I wrote a program I called mini-MIDI player (contrary to its name, it
also plays MP3 files) which did not require me to use a Visual Basic
MediaPlayer control, but let me access the Windows Media Player which is
built into Windows. I'm hoping that I can port that program over to
REALbasic.
That program was a small-footprint "always-on-top" application which -
after you did something with it (such as change a song) - immediated
restored the focus back to whatever program you were using before you
accessed the mini-MIDI-program, so that's another feature I hope I can
bring over.
Apologies in advance to Mac and Linux users if some of my programs work
only with Windows. In this particular situation, the VB runtime file (a
large file needed to run _any_ VP program) is a very strong inducement
to use API calls (rather than otherwise needed VB controls) or to use
other (perhaps Windows-specific) techniques to cut down the size of the
final program. (With VB, a very small program wastes an amazing amount
of space.)
Barry Traver
_______________________________________________
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|