Skip to content
  • 1 Votes
    18 Posts
    2k Views
    Marko StankeM

    Tried it on Qt 5.15, and it works perfectly

  • 0 Votes
    2 Posts
    1k Views
    Gojir4G

    Hi, it seems ConicalGradient has been removed from Qt 6. There is probably a new alternative for that. Anyway you can still accessing it using the Qt5Compat module.
    See details here: https://doc.qt.io/qt-6/qml-qt5compat-graphicaleffects-conicalgradient.html

    Note you'll probably need to install the Qt5Compat module corresponding to your Qt version from the Maintenance Tools if that's not already the case.

  • Progress bar updating

    Unsolved General and Desktop
    13
    0 Votes
    13 Posts
    3k Views
    D

    @mrjj okey

  • 0 Votes
    9 Posts
    1k Views
    D

    @SimonSchroeder I want to update my progress bar, if one of these values greater than 0. For example if the dizi[1] > 0, update.

    I dont want to see dizi[0]. Because of it i started from 1

  • 0 Votes
    8 Posts
    4k Views
    S

    @JonB said in "Progress MessageBox":

    OK. Forget about modeless for a moment, if you don't want to deal with threads. Take a look at http://doc.qt.io/qt-5/qdialog.html#open, and start from there instead of the normal QDialog::exec(). I'm thinking that may be all you are looking for.

    I still don't know what it is you think you are going to "show the progress against", but that's another issue.....

    Thanks for the recommendation. I will look into open(), etc. I will probably end up threading the heavy tasks, but I'm trying to avoid all the tedious synchronization for now.

    As for 'progress against': I realized why that may not have made sense. Individual time-consuming tasks will not be able to report on their progress mid-stream (no way to gauge how long to complete), but there is a series of them. Basically a chain of image processes--filters, denoising, etc. and each can take from 5 seconds to almost a minute. Awkward to just sit there looking at the barberpole progress bar, so I thought of setting up a timer in the progress dialog in order to monitor a 'status variable' back at the ranch. As each filter stage completes, the status variable would be updated. When the variable changes from "filter 1" to "filter 2", appropriate text could be displayed in the progress dialog. Or so I hope. :-)

  • 0 Votes
    2 Posts
    637 Views
    M

    @mjaga Just in case somebody wants to test this, here is a minimal example demonstrating the problem:

    #include <QApplication> #include <QProgressBar> int main(int argc, char *argv[]) { QApplication a(argc, argv); a.setStyle("plastique"); /* working... */ // a.setStyle("cleanlooks"); /* working... */ // a.setStyle("Windows"); /* working... */ // a.setStyle("Fusion"); /* working... */ // a.setStyle("gtk2"); /* NOT working! */ QProgressBar pb; pb.setMaximum(0); pb.setMinimum(0); pb.setValue(0); pb.show(); return a.exec(); }
  • Help with progressbar

    Solved General and Desktop
    6
    0 Votes
    6 Posts
    2k Views
    J

    This is weird, but I had applied a vertical layout to this dialog so it would resize a listbox properly. I removed the layout and the progress bar works properly. So solved, I guess...

  • 0 Votes
    12 Posts
    5k Views
    M

    @DougyDrumz said in Can't Cancel Progress Dialog.:

    OK. I found it. I was being dumb! I have two flavors of Progress Dialogs. One is inside an App, and the other is standalone, meant to be called form a script. I was looking at the one in the App when I should have been looking at the other one. The standalone one doesn't have have a cancel slot.

    Good !

  • 0 Votes
    6 Posts
    2k Views
    SGaistS

    The link provided by @Joel-Bodenmann is a good start.

  • 0 Votes
    11 Posts
    3k Views
    SGaistS

    Well, when buffersplit call setValue(buffersplit) on your progress bar.

    I'd recommend using a more descriptive variable name

  • 0 Votes
    23 Posts
    16k Views
    mrjjM

    @hamov

    well digging around, I also found
    m_list->viewport()->repaint();

    which works for WidgetList. Did not test with model/view yet.

    I think it is by design as it does redraw when data changes but we are not alone finding
    it strange working if one google it