|
From: | anonymous |
Subject: | [Octave-bug-tracker] [bug #44776] [Qt] Restore window button does not trigger a repaint event for its content |
Date: | Sat, 20 Aug 2016 11:39:48 +0000 (UTC) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 |
Follow-up Comment #23, bug #44776 (project octave): So I've found that there's a difference in behaviour with ./run-octave --no-gui and ./run-octave on QT5. I can't quite reproduce your problem but using the gui interface on QT5 for me means I do get the black screen (amongst other bugs which I guess I need to report.) I wonder if the issue you're facing is something to do with the opengl_renderer in gl-render.cc - I wouldn't be surprised if there was something in there that nvidia driver was barfing on. I am certain there are some bugs in there - for example if you take a window and resize it down to the smallest it can be and then, resize it up you'll get a complete mess. Now, as I can't reproduce your problem I guess we need to think about how to debug it on yours... I'd take a look at gl-render.cc - you could start with adding qDebug () or std::cout statements to each of the draw functions to see if they appear to be being double called or chase them back up the call-stack. I think it might be also worth looking at and wiring in: http://doc.qt.io/qt-5/qopengldebuglogger.html#details _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?44776> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |