Hi Frank, Alle 08:54, martedì 16 maggio 2006, Frank Schönheit - Sun Microsystems Germany ha scritto: > Hi Paolo, > > > In spite of this, reading the IDL description it seems that all should > > happen automatically, without listeners or event binding, infact: > > > > css.awt.UnoControlScrollBarModel > > ------------------------------- > > boolean LiveScroll; > > Description > > specifies the scrolling behaviour of the control. > > true means, that when the user moves the slider in the scroll bar, the > > content of the window is updated immediately. false means, that the > > window is only updated after the user has released the mouse button. > > Since > > OpenOffice 2.0.0 > > As I said elsewhere in the thread, the documentation is misleading here. > In fact, the property controls how events are fired. Reactions on those > events are up to the client code. > (You can use scrollbars for more than > for scrolling windows. For instance, you can bind them to spreadsheet > cells :)
Yes yes!! but as you can see, I sent this post Sunday night, before to read your first answer. Unfortunately the post was delivered only today. (I don't know why!) > > >>i would expect attach a dialog window or frame to it ? > >>how would you > >>implement both horizontal and vertical slides > > > > Perhaps this should e matter of an RFE > > Currently the css.awt.ScrollBarOrientation constant group offers only: > > HORIZONTAL and VERTICAL > > the "BOTH" option is missing. > > Hmm? How would you expect such a scrollbar to look like? How would you > expect a user to operate it? In effect the best would be to have a specialized "scroll-panel" beside the existing scrollbar control for general purposes. For example in GAMBAS (a RAD for KDE that uses the QT toolkit - I love it ;-) there is a ScrollBar control for general purposes that is very similar to UnoScrollBarControl, and, must be managed manually. In addition, there is also a specialized control called "Scrollview" that is a panel where you can put other control as children. The scrollview control manages automatically the position of its children In order to manage the appearance of the scrollbars you can set the property ScrollBar that takes the following const values: 0 -> None 1 -> Horizontal 2 -> Vertical 3 -> Both > > In all "widget programming" I ever did, the model is more or less like > this: > > +--------------------------------------------------+ +-+ > > | (1) | |^| (2) > | > | | |v| > > +--------------------------------------------------+ +-+ > +--------------------------------------------------+ > > |<| (3) |>| > > +--------------------------------------------------+ > > A main window (1) which contains the to-be-scrolled content, a vertical > scrollbar (2), and a hortizontal scrollbar (3) - all three having the > same parent, instead of being children of each other. Very intersting. IMHO there is a lack of examples/documentation/best practice/etc. reagarding AWT, so, thank you very much for information and for the nice ASCII illustration :-) > There are toolkits which allow you to knit (2) and (3) with (1) so that > scrolling happens automatically. But currently, AWT, OpenOffice.org's > UNO-based toolkit, does not belong into this group. Yes I see. Anyway I think that it would be possible (and perhaps not so difficult) to make an "UnoScrollViewControl" that works like the one in GAMBAS. At the end it's only matter to put some already existing components together and to add some glue code (I think). Perhaps this could even be done in Python ? Furthermore, If there would be a way to integrate new uno-controls in the DialogDesigner via uno-packages it would be really a nice challenge... :-) > > > The hope would be that the developer that have implemented this thing is > > reading us. > > The "LiveScroll" property was implemented by me :) So you won another big thank you for taking the time :-) > > Ciao > Frank ciao Paolo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
