Subject | Re: Can't see buttons on TIB_UpdateBar |
---|---|
Author | jmartine3 |
Post date | 2004-07-12T06:42:06Z |
I still don't have a solution on this problem. This is causing usage
problems for my customers, as they now can't see the update bar.
Does anyone here use BCB 4 and IBO 4.3Aa, who can verify that this is
a problem with this build of IBO? As I said, it worked fine on my old
machine, which was using IBO 4.2 Gc, so I'm not sure if it's an issue
with version of IBO, or with the new machine, though I sort of doubt
the latter.
Help please!
-Joe
problems for my customers, as they now can't see the update bar.
Does anyone here use BCB 4 and IBO 4.3Aa, who can verify that this is
a problem with this build of IBO? As I said, it worked fine on my old
machine, which was using IBO 4.2 Gc, so I'm not sure if it's an issue
with version of IBO, or with the new machine, though I sort of doubt
the latter.
Help please!
-Joe
--- In IBObjects@yahoogroups.com, "jmartine3" <joe@j...> wrote:
> I'm having a problem with the TIB_UpdateBar component. The glyphs on
> the buttons are invisible. I am NOT using custom glyphs.
>
> Everything was fine before, when compiled on my old dev machine, using
> IBO 4.2 Gc. On my new dev machine, I installed IBO 4.3Aa, and now I
> have the problem with the executable when compiled here.
>
> The problem is definitely in the executable (not just at design time).
> I'm also using TIB_NavigationBar, with the exact same appearance
> settings, and it works just fine.
>
> Although I can't be certain, I'm assuming that it's the version of
> IBO, and not something else on my dev machine, since the difference is
> in the executable.
>
> Here is my environment:
>
> Windows XP
> Borland C++ Builder 4
> IBO 4.3Aa
> Firebird 1.0
>
> Appearance settings in the TIB_UpdateBar:
>
> Color: cl3DDkShadow
> Ctl3DL: true
> CustomGlyphs: {null}
> Flat: true
> ParentColor: false
> ParentCtl3D: false
> Visible: true
> VisibleButtons: ubEdit,ubInsert,ubDelete,ubPost,ubCancel
>
> I have also tried it with the default values that it comes with when
> you first drop it on the form, and I have the same problem that way
> too.
>
> Help!!!!!
>
> -Joe