Re: Win32Lib bug?
- Posted by Dan B Moyer <DANMOYER at prodigy.net> Nov 16, 2000
- 472 views
Brian, Well, I think it is a bug, but it may be intended as feature? :) And I think there is supposed to be a new command to re-set the style of a window, (Wolf says Derek mentioned them in a post earlier, & I think I do remember that, now), addStyle() and removeStyle(), but I couldn't find them, maybe they are upcoming; the best I could do was to hack Win32Lib as follows: in "procedure createWindow", after "if flags!=0 then" find "lFlags=or_bits(flags,lFlags)", and change it to: "lFlags= flags --or_bits(flags,lFlags)"; that will allow whatever *you* set as flags to be accepted and created, without regard for the default setting (which is what I *think* lFlags is or was), that is, without "or'ing" the default with the user specified styles(which amounts to adding all the styles together). However, I have *no* idea if this will make other problems or not!! Maybe there's a better way, but that's all I could find. Hopefully Derek will CHANGE THIS BACK, so the programmer can specify window styles easily?? Dan ----- Original Message ----- From: "Brian Broker" <bkb at CNW.COM> To: <EUPHORIA at LISTSERV.MUOHIO.EDU> Sent: Thursday, November 16, 2000 10:47 AM Subject: Re: Win32Lib bug? > On Wed, 15 Nov 2000 17:40:25 -0800, Dan B Moyer wrote: > > >Brian, > > > >This is the same kind of thing I was referring to in an earlier post! Glad > >someone else noticed it too. :) > > > >I said: > > > >"One possible problem to look out for with regard to style setting for > >windows, unless Derek has changed it in Win32Lib, is that as far as I > >understand, in (a) recent version, the default style setting does *not* get > >"over-ridden" by user specified style, the user spec just gets *added* to > >the default, so you can't be completely sure that you have "rolled your > >own" (window style) as you intended." > > Dan, > > Sorry I missed that post, but thanks for bringing it up again. But my > question still stands: Is this a bug or a feature? If this is a feature, > then how should I go about making a non-sizeable window? > > -- Brian