Sorry for my late reply. Le mercredi 23 septembre 2009 00:45:01, Julie S a écrit : > Can we avoid using a popup? Is it really necessary? I don't see the use > of this unless there is a decision to be made. If the only option > presented is an button "ok" then there is no decision to be made.
Le mercredi 23 septembre 2009 01:01:46, Vladimir Savic a écrit : > More then valid view point. I agree 100%. Popup windows are to be > avoided my any mean! I dislike unwanted popups as much as you do. What I plan is to add a highly visible warning icon in the staff header when some inconsistent elements (clef, key or transposition) in superimposed segments make the staff unreadable. By clicking on that icon the user will get some written explanation on the current inconsistencies. Yes : I was thinking of a popup window here. But please note that this explanatory window will not pop up automatically : A beginner who doesn't understand what the warning icon means may click on it and get the needed explanations. An advanced user who immediately understands the meaning of that icon, will never click on it and will never get any unwanted popup. That said, I possibly misused the word popup. When yo click on the matrix or notation editor button, doesn't an editor window pop up ? Nevertheless this window is not called a popup ... Maybe the explanatory window I was talking of should neither be called a popup. Do you agree to such a feature ? Yves ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
