On Monday 08 September 2008, Emanuel Rumpf wrote: > Note: > Where QProgressBar is/was a member of QProgressDialog, > we pabably don't need it at all, because QProgressDialog has all > necessary properties. > > So instead of QProgressDialog->QProgressBar.value() , > use QProgressDialog.value() directly. > > That's my current understanding at least.
Quite possibly so, but we also used KProgress, I think it was, directly. This becomes QProgressBar, but it's some work to adapt from one to the other, because the new one is totally different. I have a couple nuggets of information I hope to use to accomplish this later tonight, but it's all really uncertain, and prime stuff to look at in the field after we have a field to look at. I'm sure I can get something working, but whether it will behave as expected is another matter entirely. -- D. Michael McIntyre ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
