On 23 Nov 2004, at 12:15, Alain Pastor wrote: > bernie wrote: >> Couple of things... >> I've seen 'The Crossman Wobble' (!)... In QuiXample, for instance, >> click on a row and hit the down arrow key until it reaches the bottom >> of the browser. Then, for every down arrow key press, all displayed >> rows move up or down by a pixel or two. As Finder windows also suffer >> from this, I wouldn't have thought there's an easy fix. > > I'm trying hard but I can't see that with my QuiXample plug-in at my > side. Ahhh, Monsieur, how you say in La France?... " ne peut pas voir le bois pour les arbres*"... " l'arbre qui cache la forêt "... :) *translation courtesy Sherlock To see it more clearly, try this... Open a FB project that has lots of files. In the project window, position the vertical scroll button to the top and resize the window so that the bottom of the browser (top of the horiz scroll bar) is lined up with the bottom of a file icon. Select the filename at the bottom of the list and hit the down arrow key. Notice how all the icons move up with the first key press and then down with the next. Hopefully, what you will see is the phenomenon now known as 'The Crossman Wobble'. >> AFAIK, the UpdateDataBrowser function (which Wave told *me* about, >> btw) only updates the display of the rows in the specified container >> (second param, 0 = root). So, if we have an hierarchical browser, it >> looks like the function will need to be called for each open >> container. > > Perhaps, this is here an opportunity for using the > ForEachDataBrowserItem function. I'll take a look at that. Thanks. BTW, talking of data browsers, I noticed this in Apple's HIView documentation: "Note: The following controls do not support compositing and therefore cannot not be used as views: the (non-Unicode) editable text control, the list box control, the scrolling text field control, and (currently) the data browser." BTBTW, I think the double negative is a typo. Bernie -- To unsubscribe, send ANY message to: futurebasic-unsubscribe@...