RE: win32lib: Progress bar enhancement
- Posted by jordah ferguson <jorfergie03 at yahoo.com> Jul 08, 2002
- 391 views
How about setting some pointers, to hold 'BOOl' if certain suspicious controls are declared such as Rebars. With this addition win32lib will be compatible with win95 and will also support new and good controls such as Pagers , SysLinks. Implementing the IF DEF stuff in win32lib is all we need, but it will mean a whole lot more code. Meanwhile Derek, Keep this in your todo list, and lets all do some debugging to stabilize win32lib. I'm trying to get MDI support,nice and clean but i keep getting dirty and lost. Derek, if you don't mind could you write a small documentation of how you implement the setHandler on onXXX. i can understand what is going on but some values such as kReturn and funcs like invoke handler confuse me. Jordah Sir LoJiK Derek Parnell wrote: > This is a tough one. It seems that there are many ancient Win95 systems > out > there and I'm being told that Win32lib must support them too. I'm > setting up > a scheme so that InitCommonCtl can support them. > > Maybe a different way to implement what you want is to use either > PBM_SETRANGE or PBM_SETRANGE32 depending on the actual values passed in > the > parameters. I'll try that solution out first. > > ----- Original Message ----- > From: "jordah ferguson" <jorfergie03 at yahoo.com> > To: "EUforum" <EUforum at topica.com> > Sent: Friday, July 05, 2002 9:13 PM > Subject: win32lib: Progress bar enhancement > > > > Hi Derek, > > > > When some one decides to use win32lib on his computer and win32lib > > works. It would > > automatically mean that the end user has either comctl32.dll ver 4.71 or > > above, right? > > Otherwise initcommonctl() would fail. > > > > I was tired of facing, the problem with SetScrollRange() for > > progressbars. > > Using PBM_SETRANGE would mean the mininum range is 0 and highest is > > #FFFF(65535) > > since the min and max values are expressed as unsigned integers. Windows > > API, in > > comctl32.dll ver 4.7 and later provide PBM_SETRANGE32, what's good about > > it is that > > the values can be expressed as 32bit signed integers giving a range of > > -2147483647 to +2147483647. > > >