On 10/27/2013 01:49 AM, Allan Sandfeld Jensen wrote:
> On Friday 25 October 2013, Thiago Macieira wrote:
>> On sexta-feira, 25 de outubro de 2013 16:01:11, Allan Sandfeld Jensen wrote:
>>> I think it is a bit too small to make into a qtlinuxextras library, and
>>> could we even depend on extras? I
It looks like only the home and temp dir paths are worth caching, their
window$ implementation is ~ 30-40 lines of code
if counting QDir's subcalls to QFileSystemEngine.
For these two QDir functions to stay one liners and lock-less (while thread
safe), I'm caching the paths in QDirPrivate
(QTSRC/q
On Friday 25 October 2013, Thiago Macieira wrote:
> On sexta-feira, 25 de outubro de 2013 16:01:11, Allan Sandfeld Jensen wrote:
> > I think it is a bit too small to make into a qtlinuxextras library, and
> > could we even depend on extras? I think qudev would fit best in qtbase
> > because udev i
On sábado, 26 de outubro de 2013 21:58:10, Jiergir Ogoerg wrote:
> That is, it calls other (sub)functions to perform search, copy and cleaning
> up the string which makes me
> wonder if it's OK for Qt caching the home dir path as long as the Qt
> library runs?
Yes, caching is fine, since the user
Hi,
I noticed that internally QDir::homePath() does quite some extra work:
1) It returns a copy of the home path string (not a const QString&)
2) Each time QDir::homePath() calls QFileSystemEngine::homePath() which
does this:
//START
QString home = QFile::decodeName(qgetenv("HOME"));
if (home.isEm
Hello all,
I have a small application which use QGraphicsProxyWidget to display
QWidget-based
controls over an instance of QGLWidget, defined as the viewport of a
QGraphicsView.
A subclassed QGraphicsScene overrides the drawBackground() method to render the
OpenGL scene.
This works quite well
