Re: [Qt-creator] which widget / view

2010-01-22 Thread Coda Highland 
Again, this is really a qt-interest question, not a Qt Creator one.

The typical solution here is to just use layouts and QLabel and
QLineEdit, with QGroupBox and QFrame for boxes and lines.

If your layout doesn't work with the traditional approach,
QGraphicsView might be a place to start looking.

/s/ Adam

On Fri, Jan 22, 2010 at 5:33 PM, Ken Ray  wrote:
>
> I want to have a window/view that I can draw forms into. The will contain 
> mostly lines and text along with textboxes for data input. I know that I can 
> draw pretty much into anything. Is there any particular widget / object that 
> is suited to this better than others ?
>
> thanks
> ___
> Qt-creator mailing list
> Qt-creator@trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-creator
>

___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

[Qt-creator] which widget / view

2010-01-22 Thread Ken Ray 

I want to have a window/view that I can draw forms into. The will contain 
mostly lines and text along with textboxes for data input. I know that I can 
draw pretty much into anything. Is there any particular widget / object that is 
suited to this better than others ?

thanks
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] seg fault on startup

2010-01-22 Thread Frank Neuhaus 
On Fri, Jan 22, 2010 at 8:39 AM, Brian McGillion
 wrote:
> Hi,

Hi,

> The segmentation fault is encountered when starting QtCreator but looks
> like it originates from the Qt lib so I mailed both lists. I have built
> the latest Creator from git against the Qt 4.6.1 lib that was released
> the other day.  My system is x86 Ubuntu 9.10.  Any help on this would be
> great.

I'd just like to add that I am experiencing the same problem. I am
using some qtsdk package which was released not long ago (qmake -v
reports Qt Version 4.6.0).
Not sure if it helps but my gdb output of the segfault is below.

Program received signal SIGSEGV, Segmentation fault.
0x00640f81 in QHashData::detach_helper2 (this=0x4a7b0a0, node_duplicate=
0x4a6deb0 ::duplicateNode(QHashData::Node*, void*)>,
node_delete=
0x4a6eca0 ::deleteNode2(QHashData::Node*)>, nodeSize=20,
nodeAlign=4)
at /var/tmp/qt-x11-src-4.6.0/src/corelib/tools/qhash.cpp:233
233 /var/tmp/qt-x11-src-4.6.0/src/corelib/tools/qhash.cpp: No such
file or directory.
in /var/tmp/qt-x11-src-4.6.0/src/corelib/tools/qhash.cpp
Missing separate debuginfos, use: debuginfo-install
GConf2-2.28.0-3.fc12.i686 ORBit2-2.14.17-3.fc12.i686
PackageKit-gtk-module-0.5.6-1.fc12.i686 atk-1.28.0-1.fc12.i686
avahi-0.6.25-5.fc12.i686 avahi-glib-0.6.25-5.fc12.i686
cairo-1.8.8-3.fc12.i686 dbus-glib-0.82-2.fc12.i686
dbus-libs-1.2.16-9.fc12.i686 expat-2.0.1-8.fc12.i686
fontconfig-2.8.0-1.fc12.i686 freetype-2.3.11-3.fc12.i686
glib2-2.22.3-2.fc12.i686 glibc-2.11.1-1.i686
gnome-keyring-2.28.2-2.fc12.i686 gnome-vfs2-2.24.2-2.fc12.i686
gtk2-2.18.6-1.fc12.i686 gtk2-engines-2.18.4-4.fc12.i686
keyutils-libs-1.2-6.fc12.i686 krb5-libs-1.7-18.fc12.i686
libICE-1.0.6-1.fc12.i686 libSM-1.1.0-7.fc12.i686
libX11-1.3-1.fc12.i686 libXau-1.0.5-1.fc12.i686
libXcomposite-0.4.1-2.fc12.i686 libXcursor-1.1.10-1.fc12.i686
libXdamage-1.1.2-1.fc12.i686 libXext-1.1-2.fc12.i686
libXfixes-devel-4.0.4-1.fc12.i686 libXi-devel-1.3-1.fc12.i686
libXinerama-1.1-1.fc12.i686 libXrandr-1.3.0-3.fc12.i686
libXrender-0.9.5-1.fc12.i686 libart_lgpl-2.3.20-5.fc12.i686
libbonobo-2.24.2-2.fc12.i686 libbonoboui-2.24.2-2.fc12.i686
libcanberra-0.22-1.fc12.i686 libcanberra-gtk2-0.22-1.fc12.i686
libcap-ng-0.6.2-3.fc12.i686 libcom_err-1.41.9-5.fc12.i686
libgcc-4.4.2-20.fc12.i686 libgnome-2.28.0-1.fc12.i686
libgnomecanvas-2.26.0-2.fc12.i686 libgnomeui-2.24.1-3.fc12.i686
libogg-1.1.4-2.fc12.i686 libpng-1.2.39-1.fc12.i686
libselinux-2.0.87-1.fc12.i686 libstdc++-4.4.2-20.fc12.i686
libtool-ltdl-2.2.6-17.fc12.i686 libuuid-2.16.2-5.fc12.i686
libvorbis-1.2.3-3.fc12.i686 libxcb-1.5-1.fc12.i686
libxml2-2.7.6-1.fc12.i686 linuxwacom-0.8.2.2-17.fc12.i686
mesa-libGLU-7.7-2.fc12.i686 openssl-1.0.0-0.13.beta4.fc12.i686
pango-1.26.2-1.fc12.i686 pixman-0.16.4-2.fc12.i686
popt-1.13-6.fc12.i686 zlib-1.2.3-23.fc12.i686
(gdb) thread apply all bt

Thread 5 (Thread 0xb4127b70 (LWP 26033)):
#0  0x008a8416 in __kernel_vsyscall ()
#1  0x00242c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb6324715 in WTF::TCMalloc_PageHeap::scavengerThread() () from
/home/dtag/qtsdk-2009.05/qt/lib/libQtWebKit.so.4
#3  0xb6324761 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) ()
from /home/dtag/qtsdk-2009.05/qt/lib/libQtWebKit.so.4
#4  0x0023eab5 in start_thread () from /lib/libpthread.so.0
#5  0x004e4dce in clone () from /lib/libc.so.6

Thread 4 (Thread 0xb4c50b70 (LWP 26032)):
#0  0x008a8416 in __kernel_vsyscall ()
#1  0x00242c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0x06a75c95 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x6b5d500)
at 
/var/tmp/qt-x11-src-4.6.0/src/3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2304
#3  0x06a75ce1 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=0x6b5d500)
at 
/var/tmp/qt-x11-src-4.6.0/src/3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1438
#4  0x0023eab5 in start_thread () from /lib/libpthread.so.0
#5  0x004e4dce in clone () from /lib/libc.so.6

Thread 3 (Thread 0xb7cc6b70 (LWP 26030)):
#0  0x008a8416 in __kernel_vsyscall ()
#1  0x004dd3b1 in select () from /lib/libc.so.6
---Type  to continue, or q  to quit---
#2  0x0070f929 in QProcessManager::run (this=0x8565c8) at
/var/tmp/qt-x11-src-4.6.0/src/corelib/io/qprocess_unix.cpp:245
#3  0x0062151e in QThreadPrivate::start (arg=0x8565c8) at
/var/tmp/qt-x11-src-4.6.0/src/corelib/thread/qthread_unix.cpp:244
#4  0x0023eab5 in start_thread () from /lib/libpthread.so.0
#5  0x004e4dce in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb7fd9920 (LWP 26026)):
#0  0x00640f81 in QHashData::detach_helper2 (this=0x4a7b0a0, node_duplicate=
0x4a6deb0 ::duplicateNode(QHashData::Node*, void*)>,
node_delete=
0x4a6eca0 ::deleteNode2(QHashData::Node*)>, nodeSize=20,
nodeAlign=4)
at /var/tmp/qt-x11-src-4.6.0/src/corelib/tools/qhash.cpp:233
#1  0x04a6b0a0 in
Core::MimeDatabasePrivate::addMimeType(Core::MimeType) ()
   from /home/dtag/download/qq/qt-creator/lib/qtcreator/plugins/Nokia/libCore.so
#2  0x04

Re: [Qt-creator] CppSupport Plugin 1.3.x for Qt Creator

2010-01-22 Thread Danny Price 
Hi I managed build it on OSX. Seems to work great!

It seems really strange to me that I must download and build some special 
version of Creator just to compile your plugin! What am I missing here?

Anyway thanks a LOT for your efforts in creating this. It really adds value to 
Creator.

Would you like me to provide the OSX binaries?

On 22 Jan 2010, at 14:58, visual fc wrote:

> to danny Price
> 
> I not have OSX computer. Can not be tested
> 
> 
> 
> ___
> Qt-creator mailing list
> Qt-creator@trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-creator
> 
> 
> 
> ___
> Qt-creator mailing list
> Qt-creator@trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-creator

___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

[Qt-creator] Debugger not working on some projects

2010-01-22 Thread Sebastian Fischer 

Hello,

I have a command-line-project where the debugger refuses to work properly,  
while it seem just fine in my GUI-Projects.
When stopping at a breakpoint (and generally quite often) I get the  
message 'Debugging helpers not found' in the debugging Toolbar. I've  
attached the contents of the right debugger pane in a text file.


What is strange about this is, that debugging (and the helpers) work(s)  
just fine with my other projects (which are all GUI projects). So I can't  
help but think if it has something to do with the way the console project  
is written, or if the helpers have some sort of requirement to work. The  
project was created from the QtCreator template "Qt4 Console Application"  
and I then proceeded to fill out the main-function, see the illustrating  
main function at the end of the mail. I couldn't find anything on this in  
the documentation so I thought I'd ask here...


I think it's also noteworthy that I've had the debugger supposedly stop at  
breakpoints, instead the stop occurred nowhere near a breakpoint.  
Unfortunately this was a while ago and I don't remember the exact  
circumstances or I'd have included them here.


My System here is Windows7, Qt SDK 2009.05 (so it's QtCreator 1.3.0 and Qt  
4.6.0), the same also occurs on my WinXP machine though (same Qt Versions).


Thank you in advance :)



// the promised example-main function
int main(int argc, char *argv[])
{
QCoreApplication a(argc, argv);

/*
  This is where I do the actual processing the tool is supposed to  
perform

/*

return a.exec();
}dState changed from (-1) to DebuggerNotReady(0).
d0x519ffc00x00x51b77b83
sStarting debugger for tool chain 'MinGW'...
dDebugger settings: 
dUseAlternatingRowColours: false  (default: false)
dUseMessageBoxForSignals: true  (default: true)
dAutoQuit: false  (default: false)
dLogTimeStamps: false  (default: false)
dUseDebuggingHelper: true  (default: true)
dUseCustomDebuggingHelperLocation: false  (default: false)
dCustomDebuggingHelperLocation:   (default: )
dDebugDebuggingHelpers: false  (default: false)
dUseCodeModel: true  (default: true)
dUseToolTips: false  (default: false)
dUseToolTipsInLocalsView: false  (default: false)
dUseToolTipsInBreakpointsView: false  (default: false)
dUseAddressInBreakpointsView: false  (default: false)
dUseAddressInStackView: false  (default: false)
dLocation: C:\Qt\mingw\bin\gdb.exe  (default: gdb)
dEnvironment:   (default: )
dScriptFile:   (default: )
dMaximalStackDepth: 20  (default: 20)
dListSourceFiles: false  (default: false)
dSkipKnownFrames: false  (default: false)
dEnableReverseDebugging: false  (default: false)
dAllPluginBreakpoints: true  (default: true)
dSelectedPluginBreakpoints: false  (default: false)
dNoPluginBreakpoints: false  (default: false)
dSelectedPluginBreakpointsPattern: .*  (default: .*)
dC:/Users/Creat/Documents/Studienarbeit/GraphGen/debug/GraphGen.exe0x519ffc0
dState changed from DebuggerNotReady(0) to EngineStarting(1).
dState changed from EngineStarting(1) to AdapterStarting(2).
dTRYING TO START ADAPTER
dSTARTING GDB 
dGDB STARTED, INITIALIZING IT
<1show version
<2-interpreter-exec console "help bb"
<3set print static-members off
<4set breakpoint pending on
<5set print elements 1
<6set overload-resolution off
<7handle SIGSEGV nopass stop print
<8set unwindonsignal on
<9set width 0
<10set height 0
dState changed from AdapterStarting(2) to AdapterStarted(3).
dADAPTER SUCCESSFULLY STARTED
sStarting inferior...
dState changed from AdapterStarted(3) to InferiorStarting(6).
d03152
<11attach 3152
>~"GNU gdb 6.8\n"
>~"Copyright (C) 2008 Free Software Foundation, Inc.\n"
>~"License GPLv3+: GNU GPL version 3 or later 
>\n"
>~"This is free software: you are free to change and redistribute it.\n"
>~"There is NO WARRANTY, to the extent permitted by law.  Type \"show 
>copying\"\n"
>~"and \"show warranty\" for details.\n"
>~"This GDB was configured as \"i686-pc-mingw32\".\n"
>&"show version\n"
>~"GNU gdb 6.8\n"
>~"Copyright (C) 2008 Free Software Foundation, Inc.\n"
>~"License GPLv3+: GNU GPL version 3 or later 
>\n"
>~"This is free software: you are free to change and redistribute it.\n"
>~"There is NO WARRANTY, to the extent permitted by law.  Type \"show 
>copying\"\n"
>~"and \"show warranty\" for details.\n"
>~"This GDB was configured as \"i686-pc-mingw32\".\n"
>1^done
dVERSION: 1^done,{logstreamoutput="show version\n",consolestreamoutput="GNU gdb 
6.8\nCopyright (C) 2008 Free Software Foundation, Inc.\nLicense GPLv3+: GNU GPL 
version 3 or later \nThis is free software: 
you are free to change and redistribute it.\nThere is NO WARRANTY, to the 
extent permitted by law.  Type \"show copying\"\nand \"show warranty\" for 
details.\nThis GDB was configured as \"i686-pc-mingw32\".\nGNU gdb 
6.8\nCopyright (C) 2008 Free Software Foundation, Inc.\nLicense GPLv3+: GNU GPL 
version 3 or later

[Qt-creator] Qt-Eclipse - How set qmake location in Eclipse ?

2010-01-22 Thread Ed Sutton 
How do I set the qmake path location in Eclipse ?

Eclipse is still looking at my old Qt install location and I get the following 
error when building inside qt-eclipse:

Cannot run program "/home/esutton/qtsdk-2009.03/qt/bin/qmake": Unknown reason

I want to set it to: 

/opt/qtsdk-2010.01/qt/bin

As usual, Qt Creator works great !  Thanks for a great IDE !



___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] CppSupport Plugin 1.3.x for Qt Creator

2010-01-22 Thread visual fc 
to danny Price

I not have OSX computer. Can not be tested


>>
>> ___
>> Qt-creator mailing list
>> Qt-creator@trolltech.com
>> http://lists.trolltech.com/mailman/listinfo/qt-creator
>>
>>
>
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] CppSupport Plugin 1.3.x for Qt Creator

2010-01-22 Thread visual fc 
to thorbjorn lindeijer

The combo box for projects. this cppsupport quote ProjectExplorer Plugin
projectmodel.h/cpp the project-node easy to design.

2010/1/22 Thorbjørn Lindeijer 
>
> On 01/21/2010 09:03 AM, ext visual fc wrote:
>> > Hi all.
>> >
>> > CppSupport is a QtCreator Plugin for C++ Class View
>>
>> I tried it out (compiled the cppsupport branch in your git repository),
>> and it looks pretty good!
>>
>> One thing I was wondering is why you chose to put the final nesting
>> level in a view at the bottom, instead of just having everything in the
>> tree? Same question about the combo box for projects, why are they not
>> the top-level items in the tree?
>>
>> Regards,
>> Bjørn
>>
>> --
>> Thorbjørn Lindeijer
>> Software Engineer
>> Nokia, Qt Development Frameworks
>> ___
>> Qt-creator mailing list
>> Qt-creator@trolltech.com
>> http://lists.trolltech.com/mailman/listinfo/qt-creator
>>
>
>
> ___
> Qt-creator mailing list
> Qt-creator@trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-creator
>
>
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

[Qt-creator] To all git master users: clean your plugins directory [Was: Re: seg fault on startup]

2010-01-22 Thread Daniel Molkentin 
Hi,

this is caused by a recent renaming of Plugin: the JS and the Qml Editor 
merged into one. make sure you remove the old QmlEditor.pluginspec and 
JSEditor.pluginspec files from lib/qtcreator/plugins/Nokia.

If this is still not enought and you are using git, git clean -dxf will 
make sure all non-checked-in files are gone (warning, that includes own 
local files and you will require a rebuild. The crash inside Qt is 
caused by subsequent binary incompatible changes that these stale 
plugins do not know about.

Cheers,
   Daniel

On 1/22/2010 8:39 AM, ext Brian McGillion wrote:
> Hi,
>
> The segmentation fault is encountered when starting QtCreator but looks
> like it originates from the Qt lib so I mailed both lists. I have built
> the latest Creator from git against the Qt 4.6.1 lib that was released
> the other day.  My system is x86 Ubuntu 9.10.  Any help on this would be
> great.
>
> Brian
>
>
> GNU gdb 6.8-debian
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show
> copying"
> and "show warranty" for details.
> This GDB was configured as "i486-linux-gnu"...
> (gdb) run
> Starting program: /bin/qtcreator.bin
> [Thread debugging using libthread_db enabled]
> [New Thread 0xb779ab50 (LWP 10039)]
>
> ** (:10039): CRITICAL **: atk_object_set_name: assertion
> `name != NULL' failed
> [New Thread 0xb7588b70 (LWP 10042)]
> [Thread 0xb7588b70 (LWP 10042) exited]
> [New Thread 0xb7588b70 (LWP 10044)]
> [New Thread 0xb5506b70 (LWP 10045)]
> [New Thread 0xb4bd5b70 (LWP 10046)]
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xb779ab50 (LWP 10039)]
> 0x0804d0c2 in QBasicAtomicInt::deref (this=0x1a59e5c)
>  at /usr/local/Trolltech/Qt-4.6.1/include/QtCore/qatomic_i386.h:132
> 132  : "memory");
> (gdb) bt
> #0  0x0804d0c2 in QBasicAtomicInt::deref (this=0x1a59e5c)
>  at /usr/local/Trolltech/Qt-4.6.1/include/QtCore/qatomic_i386.h:132
> #1  0x01a4d1e9 in QHash::detach_helper (
>  this=0x1ad5948)
> at /usr/local/Trolltech/Qt-4.6.1/include/QtCore/qhash.h:582
> #2  0x01a4c54f in QHash::detach
> (this=0x1ad5948)
>  at /usr/local/Trolltech/Qt-4.6.1/include/QtCore/qhash.h:299
> #3  0x01a4b397 in QHash::insert
> (this=0x1ad5948,
>  ak...@0xbfebca4c, aval...@0xbfebca10)
>  at /usr/local/Trolltech/Qt-4.6.1/include/QtCore/qhash.h:749
> #4  0x01a48694 in Core::MimeDatabasePrivate::addMimeType
> (this=0x1ad5948, mt=
>  {m_d = {d = 0x9d89610}})
>  at ../../../../src/plugins/coreplugin/mimedatabase.cpp:919
> #5  0x01a4a249 in Core::Internal::MimeTypeParser::process
> (this=0xbfebcc54,
>  t...@0xbfebcba4)
> at ../../../../src/plugins/coreplugin/mimedatabase.cpp:877
> #6  0x01a47da6 in Core::Internal::BaseMimeTypeParser::parse
> (this=0xbfebcc54,
>  dev=0xbfebcc98, filena...@0xbfebcdc0, errorMessage=0xbfebce20)
>  at ../../../../src/plugins/coreplugin/mimedatabase.cpp:760
> #7  0x01a482ac in Core::MimeDatabasePrivate::addMimeTypes
> (this=0x1ad5948,
>  device=0xbfebcc98, filena...@0xbfebcdc0, errorMessage=0xbfebce20)
>  at ../../../../src/plugins/coreplugin/mimedatabase.cpp:886
> #8  0x01a48436 in Core::MimeDatabasePrivate::addMimeTypes
> (this=0x1ad5948,
>  filena...@0xbfebcdc0, errorMessage=0xbfebce20)
>  at ../../../../src/plugins/coreplugin/mimedatabase.cpp:896
> #9  0x01a49663 in Core::MimeDatabase::addMimeTypes (this=0x98d2e78,
>  filena...@0xbfebcdc0, errorMessage=0xbfebce20)
>  at ../../../../src/plugins/coreplugin/mimedatabase.cpp:1136
> #10 0x01e77c18 in QmlEditor::Internal::QmlEditorPlugin::initialize (
>  this=0x99bd270, error_message=0xbfebce20)
>  at ../../../../src/plugins/qmleditor/qmleditorplugin.cpp:90
> #11 0x0075d151 in
> ExtensionSystem::Internal::PluginSpecPrivate::initializePlugin
> (this=0x983eca0)
> at ../../../../src/libs/extensionsystem/pluginspec.cpp:829
> #12 0x007556dc in
> ExtensionSystem::Internal::PluginManagerPrivate::loadPlugin (
>  this=0x982ce60, spec=0x9834270,
>  destState=ExtensionSystem::PluginSpec::Initialized)
>  at ../../../../src/libs/extensionsystem/pluginmanager.cpp:762
> #13 0x007546b0 in
> ExtensionSystem::Internal::PluginManagerPrivate::loadPlugins
>  (this=0x982ce60)
>  at ../../../../src/libs/extensionsystem/pluginmanager.cpp:667
> #14 0x00752120 in ExtensionSystem::PluginManager::loadPlugins
> (this=0xbfebcfec)
>  at ../../../../src/libs/extensionsystem/pluginmanager.cpp:246
> #15 0x08051259 in main (argc=1, argv=0xbfebd2d4)
>  at ../../../src/app/main.cpp:280
> (gdb) info frame 0
> Stack frame at 0xbfebc960:
>   eip = 0x804d0c2 in QBasicAtomicInt::deref()
>  (/usr/local/Trolltech/Qt-4.6.1/include/QtCore/qatomic_i386.h:132);
>  saved eip 0x1a4d1e9
>   called by frame at 0xbfebc9a0
>   source languag

Re: [Qt-creator] CppSupport Plugin 1.3.x for Qt Creator

2010-01-22 Thread Danny Price 
I must be missing something - can someone explain how to compile an OSX
version? I downloaded creator 1.3.1 source from git, moved the plugin source
into the directory source as instructed and built Creator. I then tried to
build the plugin and got that missing header error.

What am I doing wrong?

2010/1/22 Thorbjørn Lindeijer 

> On 01/21/2010 09:03 AM, ext visual fc wrote:
> > Hi all.
> >
> > CppSupport is a QtCreator Plugin for C++ Class View
>
> I tried it out (compiled the cppsupport branch in your git repository),
> and it looks pretty good!
>
> One thing I was wondering is why you chose to put the final nesting
> level in a view at the bottom, instead of just having everything in the
> tree? Same question about the combo box for projects, why are they not
> the top-level items in the tree?
>
> Regards,
> Bjørn
>
> --
> Thorbjørn Lindeijer
> Software Engineer
> Nokia, Qt Development Frameworks
> ___
> Qt-creator mailing list
> Qt-creator@trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-creator
>
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] CppSupport Plugin 1.3.x for Qt Creator

2010-01-22 Thread Thorbjørn Lindeijer 
On 01/21/2010 09:03 AM, ext visual fc wrote:
> Hi all.
>
> CppSupport is a QtCreator Plugin for C++ Class View

I tried it out (compiled the cppsupport branch in your git repository), 
and it looks pretty good!

One thing I was wondering is why you chose to put the final nesting 
level in a view at the bottom, instead of just having everything in the 
tree? Same question about the combo box for projects, why are they not 
the top-level items in the tree?

Regards,
Bjørn

-- 
Thorbjørn Lindeijer
Software Engineer
Nokia, Qt Development Frameworks
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] CppSupport Plugin 1.3.x for Qt Creator

2010-01-22 Thread Eike Ziller 

On Jan 21, 2010, at 8:45 PM, ext Danny Price wrote:

> I tried building the plugin but I get this error:
> 
> /Users/ks/Downloads/cppsupport-1.3.1-src/src/plugins/cppsupport/cppsupportplugin.h:33:
>  error: extensionsystem/iplugin.h: No such file or directory

A little bit more context around the error, like the g++ line that was executed 
by make, might help tracking down the problem.
Also it's usually a good idea to look for warnings when running qmake, some 
things that should be errors IMO are sometimes only warnings with qmake.

++ Eike

> On 21 Jan 2010, at 11:44, visual fc wrote:
> 
>> I only test build for win32 and linux 64bit. 
>> 
>> http://code.google.com/p/visualfc/downloads/list
>> 
>> Only win32-plugin and all platform source.
>> 
>> You can download Qt Creator source and cppsupport source to build.
>> 
>> Git url :
>> http://gitorious.org/~visualfc/qt-creator/qt-creator-cppsupport
>> 
>> 
>> 
>> 2010/1/21 Danny Price 
>> Wonderful! Can you please provide OSX and Linux binaries? I don't see why I 
>> need to build Creator as well.
>> 
>> 
>> On Thu, Jan 21, 2010 at 8:03 AM, visual fc  wrote:
>> Hi all.
>> 
>> CppSupport is a QtCreator Plugin for C++ Class View
>> 
>> Downloads:
>> http://code.google.com/p/visualfc/downloads/list
>> 
>> Git source url
>> =
>> git:git://gitorious.org/~visualfc/qt-creator/qt-creator-cppsupport.git
>> branch: cppsupport cppsupport-1.3.1 cppsupport-1.3.0
>> 
>> Auchor
>> =
>> Author: visualfc
>> Email : visua...@gmail.com
>> Latest: 2010.1.21
>> 
>> 
>> Install win32-plugin
>> =
>> Install qt-creator-win-opensource-1.3.0.exe
>> Copy "win32-plugin/cppsupport" to "qtcreator-1.3.0/lib/qtcreator/plugins/"
>> Run qtcreator.exe
>> 
>> 
>> Compiling source
>> 
>> You need Qt 4.6 and Qt Creator Source to build Qt Creator and CppSupport 
>> Plugin
>> 
>> Download qt-creator-1.3.x-src.zip
>> Copy "src/plugins/*" to "qt-creator-1.3.x-src/src/plugins/"
>> Build qt-creator-1.3.x-src
>> 
>> 
>> ___
>> Qt-creator mailing list
>> Qt-creator@trolltech.com
>> http://lists.trolltech.com/mailman/listinfo/qt-creator
>> 
>> 
>> 
>> ___
>> Qt-creator mailing list
>> Qt-creator@trolltech.com
>> http://lists.trolltech.com/mailman/listinfo/qt-creator
>> 
>> 
>> ___
>> Qt-creator mailing list
>> Qt-creator@trolltech.com
>> http://lists.trolltech.com/mailman/listinfo/qt-creator
> 
> 

-- 
Eike Ziller
Software Engineer
Nokia, Qt Development Frameworks

Nokia gate5 GmbH
Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany
Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B
Umsatzsteueridentifikationsnummer: DE 812 845 193
Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori




___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] Problems with Dockwidgets

2010-01-22 Thread Eike Ziller 
On Jan 22, 2010, at 12:31 AM, ext Ken Ray wrote:

> Looks like my message didn't make it.  
> 
> I found the solution and it definitely related to Creator and to user lack of 
> knowledge of Creator. I'm a bit surprised that I was sent on a wild goose 
> chase to resolve this.
> 
> The answer was surprisingly simple.  All I had to do was modify the 
> minimumSize.Width property to the size that I wanted and the geometry.Width 
> picked it up.  It seems kinda silly to have several different areas to set 
> the width of the widget i'm playing with, Min size, Max size make sense. But 
> adding a geometry completely messed me up here. Can anyone explain what the 
> rational is here .

The relationships in Qt between geometry, size hint, size policy, minimum and 
maximum size are sometimes not obvious.
Trying to wrap it up a little bit, but be sure that what I say isn't the whole 
story:
* You have to distinguish between a widget that is added to a layout or not 
(dockwidgets are in a layout).
* No layout: geometry defines the size of the widget, constrained by minimum 
and maximum size.
* In a layout: the layout takes the size hint from the widget (a size 
calculated by the widget itself, in case of a dockwidget that depends on the 
layouts and widgets inside the dockwidget), and depending on the size policy 
(http://doc.qt.nokia.com/4.6/qsizepolicy.html#Policy-enum), and depending on 
all the size hints and policies of other widgets in the layout, calculates the 
actual size of the widget, which is again constrained by minimum and maximum 
size. After that the "geometry" property reflects the size of the widget.

So, the moment a widget is contained in a layout, its "geometry" is actually a 
"read-only" property.

Designer actually sets the geometry property to read-only if you add a widget 
to a layout. Seems that you hit a bug that Designer doesn't do that when you 
add a dockwidget to a QMainWindow.

You can find a bit more detail (also mentioning "stretch factors") e.g. here 
http://doc.qt.nokia.com/4.6/layout.html

> Also, when I set the minimum width I got a vertical line on the right side of 
> the dockWidget... something I've been trying to figure out how the sample did 
> it, but with no luck. 
> 
> So I'm currently back playing with Creator and QT.  Are there be any relevant 
> books or tutorials dealing with this ?
> 
> Ken
> 
> 
> On Jan 21, 2010, at 2:46 PM, Danny Price wrote:
> 
>> We'll still be here when you come back :)
>> 
>> On 21 Jan 2010, at 22:09, Coda Highland wrote:
>> 
>>> On Thu, Jan 21, 2010 at 3:11 PM, Ken Ray  wrote:
 I tried qt-interest and not much of a response. Note that this test app 
 I'm trying to build is just like the fontsampler demo that comes with 
 creator/QT.  I'm trying to duplicate the dockwidget on the left. How did 
 fontsampler get around this problem ?   It seems to me that if Creator 
 can't hold a layout for more than a few clicks there is a serious flaw. It 
 makes working with all the contents related to that dockwidget a pain in 
 the ass.
 
 I'm going to go play with Mono now to see how there stuff is .
 
 I want some cross platform development that is stable. but if none is 
 stable , then I guess it's back to VS .net ..
>>> 
>>> Mono is pretty gimped, sadly. Most of the "good" .NET stuff is
>>> Microsoft-only junk that's only available on Windows. Even Java would
>>> be preferable to .NET if you want cross-platform compatibility.
>>> 
>>> You happened to hit on the one thing I don't like about Qt: dock
>>> widgets. I've never had a lot of luck with them, and when I do use
>>> them I develop with code, not Designer. There's several things that
>>> they don't do quite right. But don't let that one widget turn you off
>>> to the toolkit as a whole. Qt's very stable and very robust, and it's
>>> the best toolkit available for writing apps that look native on all
>>> supported platforms.
>>> 
>>> Consider possibly using some other solution if dock widgets in
>>> Designer aren't working for you. Maybe construct the dock widgets in
>>> code, or maybe use some non-docking solution.
>>> 
>>> /s/ Adam
>>> 
>>> ___
>>> Qt-creator mailing list
>>> Qt-creator@trolltech.com
>>> http://lists.trolltech.com/mailman/listinfo/qt-creator
>> 
>> 
>> ___
>> Qt-creator mailing list
>> Qt-creator@trolltech.com
>> http://lists.trolltech.com/mailman/listinfo/qt-creator
> 
> 
> ___
> Qt-creator mailing list
> Qt-creator@trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-creator

-- 
Eike Ziller
Software Engineer
Nokia, Qt Development Frameworks

Nokia gate5 GmbH
Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany
Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B
Umsatzsteueridentifikationsnummer: DE 812 845 193
Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori