Path: utzoo!attcan!uunet!koosh!bob From: bob@omni.com (Bob Weissman) Newsgroups: comp.windows.misc Subject: Re: WIN device busy creating iconic SunView window Summary: Problem solved! Keywords: SunView, windows Message-ID: <839@borabora.omni.com> Date: 24 Aug 89 23:30:26 GMT References: <807@koosh.omni.com> Organization: OMNI Solutions, Mountain View, CA Lines: 33 In article <807@koosh.omni.com>, I wrote: > I'm writing a program which creates a window in SunView1 (on a 4/110 > running SunOS 4.0.3, if that matters). Everything works fine, except that > if I start the window iconic with -Wi, I always get > WIN ioctl number 20006703: Device busy > and then the icon appears perfectly and everything is fine. > > I've read all the documentation (over and over and over...) and can not > for the life of me figure out how to get rid of this message. I finally solved this problem by looking at other sources and applying some trial and error. It turns out that you must specify the FRAME_ARGC_PTR_ARGV parameter in the initial call to window_create(). If you specify it in a subsequent call to window_set(), you get the "device busy" message. That's all there is to it. Just make sure that FRAME_ARGC_PTR_ARGV comes after any defaults you set (e.g., WIN_WIDTH, WIN_HEIGHT) which the user may want to override, and before any defaults which you do not want to let the user override. This is one case where the ordering "set FRAME_* attributes, then WIN_* attributes" does not apply. This bug has been reported to Sun software support under the service order number 352219. -- Bob Weissman UUCP: ...!{amdahl,apple,pyramid,sgi,tekbspa,uunet}!koosh!bob Hofstadter's Law: It always takes longer than you expect, even when you take into account Hofstadter's Law.