🚀 go-pugleaf

In article <1992Dec30.191610.3685@pony.Ingres.COM> bonobo@Ingres.COM (David Victor) writes:
>Has anyone out there had much experience with QuickC for Windows?  I was
>just wondering if I could get an opinion as to its usefulness.  Are there
>other CASE tools which blow away QuickCase:W?
>
I use QCWIN for prototyping prior to full build under MSC/C++ 7.0, and have
upgraded the QuickCase:W to the full product.  There is no better prototyping
setup I've found.  There are CASE tools which are less expensive than Case:W,
but none better, or, IMNSHO, even as good.  The Borland crowd will, of course,
disagree.  That is their mission, and I respect it, if not their opinions, to
which they are entitled.

Actually, though, dollar for dollar, you won't get a better deal than QC with
QC:W, no matter how hard you try.

Bill Whedon   whedon@netcom.com

-- 
-- If I ain't programmin' I ain't awake! --

In article <1992Dec30.191610.3685@pony.Ingres.COM>, bonobo@Ingres.COM (David Victor) writes:
|> Has anyone out there had much experience with QuickC for Windows?  I was
|> just wondering if I could get an opinion as to its usefulness.  Are there
|> other CASE tools which blow away QuickCase:W?
|> 
|> Thanks!
|> 
|> -David Victor

For what its worth,  I like it since it provides a rudimentary but effective
integrated environment.  I just wish they would release an update of it from the
original 1.0.  (I particularly like the debuggin environment which seems to do a
good job of protecting you from  protection faults).
-- 

Regards.
 
Don Rolph  a722756@pan.mc.ti.com WD3 MS10-13 (508)-699-1263

I was thinking the other day:

Is this possible?  I would like to create a custom message and call it
from within my program.  i.e.

#define WM_MYNEWMESSAGE <integer value>

// ...later in the windows procedure:
long FAR PASCAL _export WndProc(HWND hwnd, UINT message, UINT wParam, 
                                LONG lParam)
{
  int counter=10;
  switch (message)
  {
    case WM_MYNEWMESSAGE:
      // This case statement is basically the body of a simple for loop.
      // The body of this statement is executed counter number of times.
   
      // Print a message to screen
      --count;
      if ( count != 0 )
        SendMessage(hwnd,WM_MYNEWMESSAGE,0,0L);
      return 0;
    default:  // Pass message to DefWindowProc
  }
}

I figured that this technique would be usefull in performing long loops
without tying up Windows in one program...  Other programs get to run and
the loop still executes.

Is this even possible?

--
/---------------------------------------------------------------------------\
| Rick Ekle | rekle@loligo.cc.fsu.edu | Birth, School, Work, Death.         |
|---------------------------------------------------------------------------|
| "I survived Hurricane Andrew." | This Space For Rent | FSU #1!!!          |
\---------------------------------------------------------------------------/

Even as i could not really find out what's the purpose of this
'loop' thing, i would suggest to look at 
WM_USER
and
RegisterWindowMessage()
in your programmers reference manual.
These are two possibilities that shoul exactly fit into your need.

Hopeithelps,
Walter.

In article <1993Jan7.040719.11710@mailer.cc.fsu.edu> rekle@loligo.cc.fsu.edu (Rick Ekle (CompSci)) writes:
>I was thinking the other day:
>
>Is this possible?  I would like to create a custom message and call it
>from within my program.  i.e.
>
>#define WM_MYNEWMESSAGE <integer value>

	Yes, they have provided for it, by reserving a block for your
	use.  Look up WM_USER (start of block you can use).
-- 
John A. Grant						jagrant@emr1.emr.ca
Airborne Geophysics
Geological Survey of Canada, Ottawa