REVSOFT: spr# is DCAO3R4T2V (OpenInsight Specific)
At 12 APR 1999 12:15:17PM Steve C. wrote:
Can anyone at RevSoft tell me the status of the above
spr# is DCAO3R4T2V. This is about the problem that the
default "enable button bar" on forms does not display the
bitmaps in WinNT 4.0.
Steve C.
At 12 APR 1999 10:04PM Don Bakke wrote:
Steve,
No, I don't have a response for you. I do, however, have a question. Why do you really want this to work? You can create your own button bar fairly easily with a much better appearance and it will work under every environment.
dbakke@srpcs.com
At 13 APR 1999 03:38AM Oystein Reigem wrote:
Don,
… Why do you really want this to work? You can create your own button bar fairly easily with a much better appearance and it will work under every environment.
I am waiting for the button bar too (or my clients running NT are). My reasons for not developing my own are:
(1) Easy it may be, but it still takes some time to develop, and to implement in all the windows that need it.
(2) The psychological factor: I feel RevSoft has an obligation to fix it. And I'm certain if I make my own button bar, they will get around to fix it.
(3) But crucial for me is that several of my windows have hit the maximum number of controls limit, and I have no easy way of redesigning them with less controls.
- Oystein -
At 13 APR 1999 08:54AM Mr C wrote:
And I'm certain if I make my own button bar, they will get around to fix it.
Then you should write your own and do the rest of the community a great service
At 13 APR 1999 09:00AM Don Bakke wrote:
Oystein,
1) Easy it may be, but it still takes some time to develop, and to implement in all the windows that need it.
Most of our develop is done within a main MDI Frame, so we don't face this situation that often. However, if I needed to add a button bar to all my data windows then I would create one button bar, associate it with some generic/window-independent code, then cut and paste to all my windows. Voila!
The only real time consumer in my experience is creating BMP's for the buttons. But OI comes with many of these BMP's already or someone would probably be willing to donate theirs (I know I would).
(2) The psychological factor: I feel RevSoft has an obligation to fix it. And I'm certain if I make my own button bar, they will get around to fix it.
In pure principle alone, I agree with you. However, since this toolbar in my mind is so low on a priority list I can forgive them if they don't. The bottom line is that we can work around this with relative ease.
dbakke@srpcs.com
At 13 APR 1999 09:08AM Oystein Reigem wrote:
Steve,
Then you should write your own and do the rest of the community a great service
I thought Don had one finished already
- Oystein -
At 13 APR 1999 09:29AM Steve C. wrote:
Oystein:
I'm not "Mr. C".
I have created a pretty good button bar that I currently use for all
new forms. But I have numerous old forms that I just don't have time
to update and my agency is moving more swiftly from WFWG 3.11 to
WinNT. It would just be nice for more simple forms to add the
default button bar than do the extra event coding for my own.
Sorry I can't help you on your DDE problem. If I come across anything
I'll let you know.
From sunny and warm Austin, Texas.
Steve C.
At 13 APR 1999 03:32PM Cameron Revelation wrote:
Hi Steve,
Several NT issues are scheduled for the 3.8 release. The button bar is one that, if fixed in 3.8, will get converted from the C code (BBAR.DLL or something like that) to BASIC+ code that we will release. However, I can't guarantee what release it will be in.
I can explain though what it does: It is simply a set of buttons that send the same events that the corresponding menu items do, so it can be done with no code (using QuickEvents).
Cameron Purdy
Revelation Software
At 14 APR 1999 06:31AM Oystein Reigem wrote:
Cameron,
Several NT issues are scheduled for the 3.8 release. The button bar is one that, if fixed in 3.8, will get converted from the C code (BBAR.DLL or something like that) to BASIC+ code that we will release. However, I can't guarantee what release it will be in.
I can explain though what it does: It is simply a set of buttons that send the same events that the corresponding menu items do, so it can be done with no code (using QuickEvents).
I'm not certain what you say here but I hope your solution doesn't mean we will have to put an additional dozen buttons in our forms. I have several forms that have reached the infamous 115 controls limit.
- Oystein -