Hi, And/Blair.
In DX6.0.1's View Composer, I can't select PushButton view behind of BasicImage view. I have worked following: 1) Drop PushButton to the ShellView. 2) Drop Basic Image on PushBUtton. 3) Check View Hierarcy. Certainly, PushButton is positioned in fron of Basic Image. 4) Click to select the PushButton, it doesn't work properly. I can't select PushBUtton on Basic Image. When I assign some command(#exit, #close etc.) to that button, it is actavated and I can select it. Why can't I select disalbed button __on__ BasicImage? Please tell me. Regards. |
Hi,
> In DX6.0.1's View Composer, I can't select PushButton view behind of > BasicImage view. > I have worked following: > > 1) Drop PushButton to the ShellView. > 2) Drop Basic Image on PushBUtton. > 3) Check View Hierarcy. Certainly, PushButton is positioned in fron of > Basic Image. > 4) Click to select the PushButton, it doesn't work properly. I can't > select PushBUtton on Basic Image. > > When I assign some command(#exit, #close etc.) to that button, it is > actavated and I can select it. > > Why can't I select disalbed button on BasicImage? > Please tell me. This is caused by an oddity in Windows which you have to bear in mind when you place one view on top of another. Basically, Windows appears to draw the objects "backwards", i.e. when the visual order appears correct the actual z-order is the reverse. You can try this with any of the Windows controls - not just buttons and images. In cases where you have one object that obscures another you must use the view hierarchy pane to make selection easier/possible. Best regards, -- Andy Bower Dolphin Support www.object-arts.com |
Andy Bower wirte:
> Hi, > > > In DX6.0.1's View Composer, I can't select PushButton view behind of > > BasicImage view. > > I have worked following: > > > > 1) Drop PushButton to the ShellView. > > 2) Drop Basic Image on PushBUtton. > > 3) Check View Hierarcy. Certainly, PushButton is positioned in fron of > > Basic Image. > > 4) Click to select the PushButton, it doesn't work properly. I can't > > select PushBUtton on Basic Image. > > > > When I assign some command(#exit, #close etc.) to that button, it is > > actavated and I can select it. > > > > Why can't I select disalbed button on BasicImage? > > Please tell me. > > This is caused by an oddity in Windows which you have to bear in mind > when you place one view on top of another. Basically, Windows appears > to draw the objects "backwards", i.e. when the visual order appears > correct the actual z-order is the reverse. You can try this with any of > the Windows controls - not just buttons and images. When I put BasicImage to back away, I should be able to select another objects on that image because image is positioned background, not cover another objects. Certainly, I had put "Send to back" command to BasicImage, and I could select PushButton which is enalbed. So theese oddly behavior of the View Composer should corect like other GUI Builder--like Delphi or VB. > > In cases where you have one object that obscures another you must use > the view hierarchy pane to make selection easier/possible. As you know, view hierarchy hasn't multiple-selecting ability, so I can't slect many button to apply command. How can I select __multiple__ object with View Hierarchy? > > Best regards, > Thanks for your replying. > -- > Andy Bower > Dolphin Support > www.object-arts.com p.s.: Folks, please tell me. Have you ever met theese situation on DX6.0.1? Is it just my problem? |
Please refer following image:
http://pub.paran.com/andrea92/oddly_vc.jpg In above image, bottom-left button is enabled and selectable, which has #close command. However, another button is not selectable and disable. As you see, background image is positioned backward certainly. |
Free forum by Nabble | Edit this page |