HDTenEightyP/NetNews huggingface dataset:
From: pjsmith@iastate.edu (Phil J Smith)
Subject: OWL an ListBoxes
Keywords: windows, OWL
Organization: Iowa State University, Ames IA
Date: Fri, 18 Dec 1992 05:15:58 GMT

I have a listbox in a dialog box that is supposed to display a directory list.
The problem is that I can't get it to display the directory until I click in
it.  I would like the directory to be displayed when the dialog box is opened.
I have tried SendDlgItemMsg(id,LBN_SETFOCUS,0,0) but that does not seem to 
work.  Any ideas?



Thanks,

Phil Smith
 

Newsgroups: comp.os.ms-windows.programmer.tools
From: simmons@cs.washington.edu (David Simmons)
Subject: FYI : Zortech c++ bundle deal
Summary: 2 prices both cheap
Organization: Computer Science & Engineering, U. of Washington, Seattle
Distribution: na
Date: Tue, 15 Dec 92 17:53:06 GMT

I just received 2 offers from Symantec for the following bundle:
 * Zortech c++ 3.1  dos / windows
   -  includes 16- and 32-bit dos extenders
 * MultiScope debugger 2.0
 * Whitewater Resource Toolkit 3.0

One offer was for $249, the other was for $169, so if you're interested
in the bundle you should demand the cheaper price :-)

The offer expires 1/31, and you can call:
1-800-421-8886 voice, or fax 303-727-4611 to order; 800-999-8846 for "pre 
sale tech support".

=sigh= I'd almost decided between BC++ and MSC7, now I have to consider
Zortech too.  Too many choices!  :-(

I have no connection with Symantec/Zortech.

---Dave
-- 

Dave Simmons            | "Quod erat demonstrandum, baby.
CS grad student         |                           (ooh you speak French)"
U of Washington Dept CS |  --Thomas Dolby "Airhead"
From: mills@athena.lkg.dec.com (George Mills)
Newsgroups: comp.os.ms-windows.programmer.tools
Subject: Re: OWL an ListBoxes
Keywords: windows, OWL
Date: 18 Dec 92 16:33:02 GMT

pjsmith@iastate.edu (Phil J Smith) writes:

>I have a listbox in a dialog box that is supposed to display a directory list.
>The problem is that I can't get it to display the directory until I click in
>it.  I would like the directory to be displayed when the dialog box is opened.
>I have tried SendDlgItemMsg(id,LBN_SETFOCUS,0,0) but that does not seem to 
>work.  Any ideas?

Create a virtual function for WM_INITDIALOG and initialize your box there.

>Thanks,

>Phil Smith
> 
Newsgroups: comp.os.ms-windows.programmer.tools
From: jonm@Ingres.COM (Don't Judge a book by your cover)
Subject: Re: VB option buttons inside frames?
Summary: 
News-Software: VAX/VMS VNEWS 1.41    
Keywords: VB, option buttons
Organization: University of Arizona MIS Department - Mosaic Group
Date: 16 Dec 92 16:44:37 GMT

In article <bsm.5.0@utrcv1.res.utc.com>, bsm@utrcv1.res.utc.com (Brian S. McCarthy) writes...
>Hi,
> 
>"Note  If you want to create more than one group of option buttons, you 
>must place some of them inside frames or picture boxes.  All the option 
>buttons inside any given frame constitute a separate group, as do all the 
>option buttons inside a picture box.  When creating a separate group this 
>way, always draw the frame or picture box first, then draw the option 
>buttons."

The reason is because only one option button may contain a value of '1' at
any time.  You can overcome this by grouping them in separate areas. 
Therefore each will have a value of 1 in its own area.

>I followed these instructions exactly.  When I try to click on any of the 
>option buttons inside my frames or picture boxes, nothing at all happens.

You may not be setting them to 1 to start with.  Try clicking on any one and 
click on anpther.  It should now change.  Each sub-frame will have its
own perception of which option is set.

> 
>What do I need to do to make two or more separate groups of option buttons 
>work?
> 
+---------------------------------------------------------------------------+
|Jon Machtynger (jonm@ingres.com)                                           |
|Ingres Technology Centre. Wharfedale Rd,                                   |
|Winnersh, Wokingham. Berks UK.   (0734)-496525                             |
+---------------------------------------------------------------------------+
| Ahhh Brisbane, people actually get paid to work there... in the sun with  |
| all that fresh air and cheap petrol.... Or so ledgend has it              |
+---------------------------------------------------------------------------+
Newsgroups: comp.os.ms-windows.programmer.tools
From: rryan@panix.com (Rob Ryan)
Subject: Re: MSC 7.0 windows debug mode and 'Cant read from device AUX'
Date: Wed, 16 Dec 1992 13:59:38 GMT
Distribution: comp.os.ms-windows.programmer.tools
Organization: Panix, NYC

In <1992Dec15.114345.8779@titan.inmos.co.uk> jeremy@cheetah.inmos.co.uk
(Jeremy Thorp) writes:

>I have NEVER got DebugOutput to work. TRACE (C++), and OutputDebugString
>work fine, but not DebugOutput. I am using DbWin.
>
>Could someone give me an example that is known to work (with configuration)?

The main thing is that you need a line in your .DEF file that says:

  IMPORTS		_DebugOutput=KERNEL._DebugOutput

Also, this is a Windows v3.1 routine, so it won't work if you have
Windows 3.0.  I'm not sure why this import is needed.  It is a documented
function of the Windows 3.1 API, so you really shouldn't need to do this,
but you do.  Also, the docs don't seem to reference to DBF_APPLICATION.
Perhaps they simply expect everyone to use TRACE().

-- 
 Rob Ryan
    rryan@panix.com
From: twbrown@PE-Nelson.COM (Tom W. Brown)
Newsgroups: comp.os.ms-windows.programmer.tools
Subject: Re: How to implement a Linked List
Date: 17 Dec 92 17:18:44 GMT
Organization: PE-Nelson

In article <1992Dec17.084558.9832@nuscc.nus.sg>, shah@cherry.NoSubdomain.NoDomain (Shahrin Abdullah) writes:
|> In article <724532588snz@chrism.demon.co.uk>, chris@chrism.demon.co.uk (Chris Marriott) writes:
|> |> 
|> |> If you're using Microsoft C7, you can implement a linked list in Windows
|> |> in exactly the same way you would for DOS - just use the standard run time
|> |> library "malloc" function.  If you use the large memory model (and there's
|> |> no reason not to, any more), "malloc" gets mapped onto calls to a pretty
|> |> good "sub-allocator".
|> |> 
|>  
|> The problem here is that malloc will map the memory allocation to the local
|> heap. Thus if the node dynamically grow too large the local heap won't be
|> able to handle that. So the question remain - how do U implement a linear 
|> linked list using the Global Heap? Thanks Chris.
|> 

I can't adequately speak for Microsoft C7, but I know Borland 3.1 uses a
sub-segment allocator with globally allocated memory if you compile in
large model.  I'd be very suprised if C7 did any different.  Note that
Chris specified large model in his reply -- this is definitely the key.

However, if I'm wrong and C7 still uses the local heap for large model
memory allocation then perhaps you should switch compilers :-)


----------------------------------------------------------------------------
Tom Brown               |  "She turned me into a newt...
PE Nelson Systems       |                                  ... I got better"
twbrown@pe-nelson.com   |                    Monty Python and the Holy Grail
----------------------------------------------------------------------------
Newsgroups: comp.os.ms-windows.programmer.tools
From: mwp@wam.umd.edu (Marty William Peck)
Subject: Re: Neat bitmapped trees?
Organization: University of Maryland, College Park
Date: Sun, 20 Dec 1992 04:37:59 GMT

I'd also like information on this. I need it for something
compleatly diferent, but with a simmeler look.
                                   Thanks
                                    Marty
From: alan@comp.lancs.ac.uk (Alan Phillips)
Newsgroups: comp.os.ms-windows.programmer.tools
Subject: Re: MSC 7.0 windows debug mode and 'Cant read from device AUX'
Date: 17 Dec 92 10:09:39 GMT
Organization: Department of Computing at Lancaster University, UK.

In article <70560005@hpcc01.corp.hp.com> azarian@hpcc01.corp.hp.com (Randy Azarian) writes:
>I do not agree that DBWIN is not useful in the standard kernel.  It is very
>useful to do OutputDebugStrings in my code as I am debugging.  Additionally,
>I have noticed that DBWIN does display quite a few "warning" messages in the
>standard kernel, albeit probaby insignificant, although I think it will report
>unfreed memory handles, and the like.

You might like to look at my TextView DLL, which is somewhere on
ftp.cica.indiana.edu. It basically manages a scrolling output window
for you, and you can write text with various options like timestamping
to it with a single API call. Other APIs allow you to clear it, etc, etc.

I wrote it originally as a real-time trace system for debugging, and there's
a sample app in the ZIP file that demonstrates it. I use it hugely for
buiding my PFE editor, and the ability to have a set of trace messages that
I can scroll back and examine at leisure is _very_ useful.

Alan
From: slo@otter.hpl.hp.com (Steve Loughran)
Date: Fri, 18 Dec 1992 09:58:18 GMT
Subject: Re: Re: MFC and Borland IDE
Organization: Hewlett-Packard Laboratories, Bristol, UK.
Newsgroups: comp.os.ms-windows.programmer.tools


I've been using both class libraries for a bit now, and find it hard to
rate one as clearly superior to another.

OWL
===
	-easy addition of callbacks via DDVTs -BCC only
	-nice high level classes for windows, dialog boxes
	-online help under BCW
	-a small manual
	-I don't know about other platforms as support in the UK is
	 a bit minimalist.
MFC
===
	-message maps are a bit tortuous (can compile under BCC)
	-some high level objects such as CWnd
	-lots of low level classes, especially for GDI
	-bigger manuals but they're better.
	-better debugging functions -VERIFY, Dump()
	-available now for winNT, win32s

I think OWL might be a good starting point for a new programmer on a
new program, although they'll end up learning most of the nitty gritty
windows stuff anyway. quite a lot of the MFC member functions are 
wrappers for windows api calls with the first HWND or HDC argument
inserted automatically. This makes it easier for an experienced 
programmer to migrate to the library.

One thing I do like about MFC is all the small classes for things like 
rectangles, regions, brushes, bitmaps and so on. With OWL you can have
a structured top down decomposition of all your windows callbacks, but
are then left reaching for volume #2 of the win SDK API reference when
you actually want to do anything in the callbacks. The low-level msoft
objects come in handy here, letting you create GDI objects then select 
them into DCs, add in a couple of regions to do your clipping and half
your work's done!

Even these are a bit limited- there's no support for DIBS, the brushes
and pens could easily be extended with a deselect function that selects
a stock object into the DC, saving all that business of remembering what
was there first. Still, I guess no-one is ever satisfied with someone
elses library.

Currently I only use OWL in the top level test harness of a DLL I'm doing.
I chose that one because I'm using BCC and the link to the online help saves
time reading manuals. For the main code I use neither library as this
would affect portability. Having realised how useful GDI classes would be
I just knocked up a set of my own which may not be complete yet but it
meets my needs. If anyone out there wants a copy of this then mail me
(allow 28 days for delivery)

	-Steve
From: hagelin@elixir.e.kth.se (Martin Hagelin)
Newsgroups: comp.os.ms-windows.programmer.tools
Subject: OWL & transfer to Combobox
Date: 14 Dec 92 13:10:29 GMT
Distribution: comp
Organization: School of EE, Royal Institute of Technology, Sweden



Hello everybody !

I have a problem with OWL and transfer to/from Comboboxes in a dialog.
I try to display a combobox in a dialog and fill it with information
but somehow the Gods aren't with me. I'm running BC++ v3.1 with OWL.



The code looks like this:


struct TMyTransferStruct {
  ...
  PTComboBoxData pcbxdata;
  ...
};


class TMyWindow : public TWindow
{
  ...
  TMyTransferStruct MyTransferStruct;
  ...
};


TMyWindow::DoTheBox()
{
  MyTransferStruct.pcbxdata = new TComboBoxData();

// Fill the list
  MyTransferStruct.pcbxdata->AddString("bla bla");
  ...

// Create the dialog and it's components
  PTDialog MyDialog = new TDialog(this, ID_MYDIALOG);
  ...
  new TComboBox(MyDialog, ID_MYCOMBOBOX);
  ...

// Set the TransferBuffer to my transferstruct
  MyDialog->SetTransferBuffer(&MyTransferStruct);

// Do the dialog
  if ( GetApplication()->ExecDialog(MyDialog) == MB_OK ) {
    strcpy(answer, MyTransferStruct.pcbxdata->Selection);
    ...
  }

// problem statement
  delete MyTransferStruct.pcbxdata;
}


Because I create a TComboBoxData with new, I must delete it
afterwards. But if I do this, everything crashes the second time I run
DoTheBox(), and if I omit the delete statement everything works fine
for maybe 10 or 20 times then it crashes (probably because more and
memory is taken by the TComboBoxData:s).

The manual is not very informative about transfering and especially
not to/from comboboxes. Am I doing this totally backwards ?

From what I believe (not that I havn't studied the manuals), manages
the ExecDialog() the deletion of the dialogbox and it's children when
the routine is finished.

I'd sure appriciate some help on this subject, or some other solutions
on how to get your transfer to/from dialog boxes to work. 


/Martin

--
--------
Martin Hagelin
hagelin@elixir.e.kth.se
From: cbs+@cs.cmu.edu (Clauss Strauch)
Newsgroups: comp.windows.ms.programmer,comp.os.ms-windows.programmer.tools
Subject: Best GUI development kits for MS Windows?
Date: 14 Dec 92 20:31:11 GMT
Article-I.D.: cs.Bz9no7.E8E.1
Organization: School of Computer Science, Carnegie Mellon


	Some folks here have asked me to look into what are the "best" GUI
development kits for MS Windows.  They are Windows novices who plan on porting
an application from Unix (X11) and would like to start off using a good set of
tools.  Since I'm also a Windows novice, any recommendations, warnings, etc. 
about such kits would be much appreciated.  I will post a summary of responses
to the net.
				Thanks,
					Clauss Strauch
					Engineering Design Research Center
					Carnegie Mellon University
                                        cbs+@edrc.cmu.edu

	
From: smythee@etcetc.fidonet.org (Ean Smythe)
Sender: uucp@etcetc.fidonet.org
Newsgroups: comp.os.ms-windows.programmer.tools
Subject: WinHelp Microsoft Advisor
Date: Fri, 11 Dec 1992 21:09:00 -0600

    Is Microsoft Advisor or the Run-Time Library Help files available
in WinHelp format?  It'd be nice to keep from switching between QuickHelp
and WinHelp.

E=-Ean=-
Internet: smythee@etcetc.fidonet.org
FidoNet : 1:170/106
From: jegm@cody.esd.sgi.com (Jim Morris)
Newsgroups: comp.os.ms-windows.programmer.tools
Subject: Re: FYI : Zortech c++ bundle deal
Date: 17 Dec 92 18:21:31 GMT
Reply-To: jegm@esd.sgi.com
Distribution: na
Organization: Silicon Graphics, Inc.
NNTP-Posting-Host: cody.esd.sgi.com

In article <1992Dec17.161000.27062@u.washington.edu>, ulbricht@carson.u.washington.edu (Craig Ulbricht) writes:
|> agallagh@slate.mines.colorado.edu (GALLAGHER ANDREA J ) writes:
|> 
|> >simmons@cs.washington.edu (David Simmons) writes:
|> >: I just received 2 offers from Symantec for the following bundle:
|> >:  * Zortech c++ 3.1  dos / windows
|> >:    -  includes 16- and 32-bit dos extenders
|> >:  * MultiScope debugger 2.0
|> >:  * Whitewater Resource Toolkit 3.0
|> >: 
|> >: One offer was for $249, the other was for $169, so if you're interested
|> >: in the bundle you should demand the cheaper price :-)
|> 
|> >The $169 is if you are already a registered Zortech user.
|> 
|> 
|> My offer was for $129.00.  It also included Whitewater Resource Toolkit

Mine was for $129 also.

I called the pre-support number and confirmed that you *CANNOT* debug
32 bit code with what is in the package! You have to buy a debugger from
another company (FlashTEk?). Unless the 32-bit code is excellent and the
compiler extremely stable I will probably return it, although I really
do need a 32-bit compiler whose code is compatible with VCPI & DPMI, and
Zortech is the best bet to date, I really wish Borland would hurry up
and get their 32 bit act together.
-- 
Jim Morris, Email: jegm@esd.sgi.com  Voice: (415) 390-5136
Newsgroups: comp.os.ms-windows.programmer.tools
From: avinogra@empire.cce.cornell.edu (Alex Vinogradov)
Subject: Re: MSC 7.0 windows debug mode and 'Cant read from device AUX'
Organization: Cornell Cooperative Extension
X-Newsreader: TIN [version 1.1 PL8]
Distribution: comp.os.ms-windows.programmer.tools
Date: Fri, 11 Dec 1992 18:32:37 GMT


In article <RHARMON.92Dec10144328@triton.uucp> you wrote:

: I got a System error: Can't read from device AUX'

Try setting AUX=NUL in your system.ini.  I do not remeber in which section of
system.ini it goes into off-hand, but I will check it out and e-mail you 
later.  Do not hesitate to remind me by e-mail if I forget!

: This happens if I try to resize the Solitate app.  The only other thing running
: is clock.

: Anyone know why Its got to read from AUX (when I didn;t ask it to).

I means that it's trying to dump some debugging info to AUX port (it does 
not mean that you have an error anywhere !).  Normally, you'd have a second
monitor attached to the computer, and it would serve as a AUX output device
for the debugging kernel, but since you don't have one and you haven't told
kernel that you don't, it is still trying to output the info to AUX and of
course fails to do so.  

I've had a lot of trouble with this problem myself -- that's why I did not use 
debugging kernel for almost a yeart, until I figured out what the problem
was.

If you do not want to buy a second monitor for debugging messages, you should be
using DBWin utility which comes with SDK.   DBWin shows all the info that 
was supposed to go to the secondary monitor in a window.  The only thing that
it does not do is show back-trace in case your app produces an error-msg --
for speed reasons this feature has been turned off by MMicrosoft.  All that
needs to be changed to get back-trace is three or four lines of code; you
can get this from Microsoft's CompuServe forum.

E-mail me if you have any other questions on this
---------------------------------------------------------
Alex Vinogradov
Cornell Cooperative Extension, Electronic Technology Group
avinogra@empire.cce.cornell.edu
(607)256-8129

-- 
---------------------------------------------------------
Alex Vinogradov
Cornell Cooperative Extension, Electronic Technology Group
avinogra@empire.cce.cornell.edu
From: azarian@hpcc01.corp.hp.com (Randy Azarian)
Date: Tue, 15 Dec 1992 23:06:54 GMT
Subject: Re: MSC 7.0 windows debug mode and 'Cant read from device AUX'
Organization: the HP Corporate notes server
Newsgroups: comp.os.ms-windows.programmer.tools

I do not agree that DBWIN is not useful in the standard kernel.  It is very
useful to do OutputDebugStrings in my code as I am debugging.  Additionally,
I have noticed that DBWIN does display quite a few "warning" messages in the
standard kernel, albeit probaby insignificant, although I think it will report
unfreed memory handles, and the like.

When running the debug kernel, placing DBWIN in the startup may not be 
sufficient to eliminate the 'Cannot write to AUX' message (as things that 
write to AUX may get loaded before DBWIN).  In this case, place a line in 
your system.ini file:

[Debug]
OutputTo=NUL

I have also noticed that (for some unknown reason) periodically DBWIN will 
turn itself off by sending its output to NONE.  When this happens, if the
OutputTo= is not set to NUL the machine will effectively hang until the
offending application trying to write to AUX is terminated (via Ctl-Alt-Del).
Newsgroups: comp.os.ms-windows.programmer.tools
From: curzon@trooa.enet.dec.com (Richard Curzon)
Subject: Re: Util for watching memory alloc and type?
Organization: Digital Equipment Corporation
Date: Wed, 16 Dec 1992 16:01:56 GMT


In article <724430999snz@chrism.demon.co.uk>, chris@chrism.demon.co.uk (Chris Marriott) writes...
>In article <1992Dec14.234027.4282@ucsu.Colorado.EDU> baileyc@ucsu.Colorado.EDU writes:
> 
>>
>>I was wondering if there was some utility for windows that watched what
>>program was allocating what memory, and of what type?  

> 
>Sure - that's what the SDK's "HeapWalker" program is for!  VERY useful.
>-- 

Or in the Borland world... Heapspy.  (At least in Borland Pascal 7.0).
From: ulbricht@carson.u.washington.edu (Craig Ulbricht)
Newsgroups: comp.os.ms-windows.programmer.tools
Subject: Re: FYI : Zortech c++ bundle deal
Date: 17 Dec 92 16:18:20 GMT
Article-I.D.: u.1992Dec17.161820.27226
Organization: University of Washington

rryan@panix.com (Rob Ryan) writes:

>For all of Zortech's (aka Symmantec's) weaknesses, they do have the cheapest
>32-bit DOS compiler that I've seen.  If you want big DOS programs, check it
>out.

>Incidentally, did anyone else notice the comment about ObjectWindows in the
>Zortech add?  Are they including it?  Isn't that odd since they supposedly
>licensed to use MFC at the Windows NT conference a few months ago.  I'm a
>little disappointed to see them go the OWL route if that's what they're 
>really doing.

>-- 

No, they are not shipping OWL with ZC++3.1.  Their Tech Support said
that ZC++3.1 is not compatible with OWL.  They did say that it was
compatible with Microsofts Windows class libraries.

Craig Ulbricht
Newsgroups: comp.os.ms-windows.programmer.tools
From: shah@cherry.NoSubdomain.NoDomain (Shahrin Abdullah)
Subject: Re: How to implement a Linked List 
Organization: Institute of Systems Science, NUS, Singapore
Date: Thu, 17 Dec 1992 08:45:58 GMT

In article <724532588snz@chrism.demon.co.uk>, chris@chrism.demon.co.uk (Chris Marriott) writes:
|> In article <1992Dec16.062628.3410@nuscc.nus.sg> shah@cherry.NoSubdomain.NoDomain writes:
|> 
|> >Hi there!
|> >Does anyone out there knows how to implement a linked list for Windows using
|> >MS C7. I know how to do it in C but in Windows it look tricky. I think I may
|> >need to use the global heap with the GMEM_MOVEABLE flag but I not too sure
|> >of going around  doing it. Can anyone gave me some pointer, please. Any 
|> >source code sample is also appreciated. 
|> >
|> >Shahrin 
|> >E-mail shah@iss.nus.sg
|> >
|> 
|> If you're using Microsoft C7, you can implement a linked list in Windows
|> in exactly the same way you would for DOS - just use the standard run time
|> library "malloc" function.  If you use the large memory model (and there's
|> no reason not to, any more), "malloc" gets mapped onto calls to a pretty
|> good "sub-allocator".
|> 
|> Chris
|> -- 
 
The problem here is that malloc will map the memory allocation to the local
heap. Thus if the node dynamically grow too large the local heap won't be
able to handle that. So the question remain - how do U implement a linear 
linked list using the Global Heap? Thanks Chris.

Cheers!
        Shahrin
        E-mail shah@iss.nus.sg

Newsgroups: comp.os.ms-windows.programmer.tools