🚀 go-pugleaf

In article <1992Sep25.222416.19318@microsoft.com> fredf@microsoft.com (Fred Freeland) writes:
> Obviously it cannot be totally code compatible with Visual Basic for Windows
> because it runs in a totally different environment and things are handled
> differently between the two environments. Sorry, this is a fact of life.

	How come ? There are windows, that can very well be drawn without
	MS Windows. VB doesn't multitask, so that is not a problem either.

> You have very obviously misunderstood what this product is. It is not the
> programming package for DOS that's going to let you write DOS apps that
> simply look like they are Windows apps.

	Put that in you adverizements.

> DOS is a character-based medium.

	DOS is NOT a character-based medium. DOS has lousy segments, but
	it can use the mouse and graphical screens. 

> True, there
> are custom graphical packages that run under DOS, but VB/DOS is not one
> of them, and is was never advertised as such.

	Visual Basic for DOS. So Visual means character based graphics ?
	^^^^^^

> >  (2) You cannot put graphics on forms. This is a BIG, BAD thing as
> >      far as I am concerned.
>
> It's true, you cannot, but that's because the forms ARE NOT graphic. You
> cannot simply plop down a graphic on a text-based screen where the standard
> unit of measure is a character-width. 

	If you accept screen, line, pset, etc... You should accept
	graphical forms too. BTW, even AmigaBASIC written 1985 by MicroSoft
	can handle multiple windows (Forms).

/robin