Digital Workshop

I wanted to create a window, with several tabs interface in it. Does opus have any tab object? I couldnt find one.

I think you'll have to make this yourself. This is a fairly simple process of creating your tabs on a few successive pages & simply linking the pages via clicks on their tabs -- not a big deal to do. I'm not surprised it isn't "hard-wired" into Opus, as there are so many possible variations on what users need to do with tabs (how the tabs look, how many are needed, their horizontal/vertical orientation, etc.) -- and yet for all of this variation, outside of Help files the "Tab approach" is not used all that frequently in most screen navigation. (BTW: If memory serves, wasn't there -- at one time, long ago -- an example of a tabbed screen?)

There are now so many object options in Opus that, until this thread, I had thought it was starting to look as if there is an object-creation button for every imaginable object in the familiar PC universe.

Thanks for reply! Yes i Agree, opus already has a lot of objects ....just that if it has tab object..how good it will be. I mean, at least it make life easier for us, who need that.

Oh btw...I have another question to ask, is there a drop down list (not the same as list box) in opus? I think that is missing from opus. Drop down list box is a common stuff in many application..it should not be a missing feature

We designed Opus to be as versatile as possible so that you can design exactly what you need and are not necessarily constrained by Microsoft's design for list boxes etc and can design your own scrollbars and list boxes.

All you need do is design what you need once and then save it as a component. You can then use it over and over again as though we had included it (only it meets your requirements exactly rather than a generic compromise). With the new Default Object options in XE you can even assign these custom components to the relevant toolbar button.

If you want somewhere to start there should be a tabbed folder component included in the resources.

Hope this helps.

Paul Harris

Even a drop-down list would have so many possible variations that a generic "generate drop-down list" function would probably be nearly meaningless. It would contribute to "program bloat" without providing a payoff in terms of improved functionality.

If all drop-down lists followed identical styles, behaved the same way in terms of how they revealed choices, etc. -- you could probably make a good argument for including this kind of automated authoring component. And if you're making a web site, nearly all of the popular authoring tools provide standard web-like drop-down list box tools. That's because HTML has some standardized functions built in.

hi,

i just had to make some tabs myself for a publication , i avoided the multiple page option as that creates unnecessary resources. instead i just used a multiframe, with a row of radio buttons which selected the correct frame in the multiframe.

works well, just remember to enable "Stop mouse clicks passing though" for each frame and insert your content into each multiframe.

I think it would although be useful to have the standard Microsoft designs ready to use in Opus. If one has to build a windows standard application this could help to avoid a lot of work. Some of my customers insist on applications that are conform to the Microsoft GUI guidelines so I would appreciate some standard controls like buttons, tabs, listboxes etc.

Currently I use VB to create the controls, take screenshots, work them over with photoshop and then put them into Opus. This is doable but not my favourite workflow

T.