On Tue, Mar 11, 2008 at 03:19:42PM -0400, rgheck wrote:
Can I ask a very silly question? OK. How do you compile something simple
like this? All my work has been on projects that already have Makefile
stuff installed.
Well, 'g++ -I/path/to/Qt/includes main.cpp' gives a binary called a.out.
On Tue, Mar 11, 2008 at 03:19:42PM -0400, rgheck wrote:
>
> Can I ask a very silly question? OK. How do you compile something simple
> like this? All my work has been on projects that already have Makefile
> stuff installed.
Well, 'g++ -I/path/to/Qt/includes main.cpp' gives a binary called
On Fri, Mar 07, 2008 at 09:56:44PM +0100, Stefan Schimanski wrote:
Don't whether QComboBox supports tree models.
It does. You can plug in any QAbstractItemModel.
And then it makes what out of it? A QTreeView popup? A chained popup menu?
Well, whatever view you put in.
#include
Can I ask a very silly question? OK. How do you compile something simple
like this? All my work has been on projects that already have Makefile
stuff installed.
rh
Well, whatever view you put in.
#include QtCore/QtCore
#include QtGui/QtGui
int main(int argc, char *argv[])
{
Can I ask a very silly question? OK. How do you compile something simple
like this? All my work has been on projects that already have Makefile
stuff installed.
g++ -I/usr/include/qt4 -L/usr/lib/qt4 -lQtCore -lQtGui file.cc -o file
On Fri, Mar 07, 2008 at 09:56:44PM +0100, Stefan Schimanski wrote:
>>> Don't whether QComboBox supports tree models.
>>
>> It does. You can plug in any QAbstractItemModel.
>
> And then it makes what out of it? A QTreeView popup? A chained popup menu?
Well, whatever view you put in.
#include
Can I ask a very silly question? OK. How do you compile something simple
like this? All my work has been on projects that already have Makefile
stuff installed.
rh
Well, whatever view you put in.
#include
#include
int main(int argc, char *argv[])
{
QApplication app(argc, argv);
> Can I ask a very silly question? OK. How do you compile something simple
> like this? All my work has been on projects that already have Makefile
> stuff installed.
g++ -I/usr/include/qt4 -L/usr/lib/qt4 -lQtCore -lQtGui file.cc -o file
Here is the patch for the grouped layout.
The whole thing would be so much easier if QComboBox supported non-
uniform-sized items in the popup. It just takes the first item and
multiplies it with the item number to calculate the popup size. Hence
I spent most time to find a way to avoid the
Here is the patch for the grouped layout.
The whole thing would be so much easier if QComboBox supported non-
uniform-sized items in the popup. It just takes the first item and
multiplies it with the item number to calculate the popup size. Hence
I spent most time to find a way to avoid the
Am 06.03.2008 um 07:23 schrieb rgheck:
This is in. See 23501-3.
You want Layout::category().
inline: Bild 3.png
Stefan
nice.
would unnumbered not be better than starred?
Edwin Leuven [EMAIL PROTECTED] writes:
nice.
would unnumbered not be better than starred?
Unnumbered sections, even.
And is it possible (optionally?), to show that as a hierarchical menu?
Or a double-column think like the mac file selector?
JMarc
Am 07.03.2008 um 16:21 schrieb Jean-Marc Lasgouttes:
Edwin Leuven [EMAIL PROTECTED] writes:
nice.
would unnumbered not be better than starred?
Unnumbered sections, even.
And is it possible (optionally?), to show that as a hierarchical menu?
Or a double-column think like the mac file
Am 07.03.2008 um 16:14 schrieb Edwin Leuven:
nice.
would unnumbered not be better than starred?
Should we put a translation step in between the TextClass and the
layout list? If yes, how? Just a big case distinction, mapping
TextClass categories to visible category names?
Stefan
Stefan Schimanski [EMAIL PROTECTED] writes:
Should we put a translation step in between the TextClass and the
layout list? If yes, how? Just a big case distinction, mapping
TextClass categories to visible category names?
You mean translation by gettext? Sure.
But I am not sure this is what
Stefan Schimanski [EMAIL PROTECTED] writes:
And is it possible (optionally?), to show that as a hierarchical menu?
Or a double-column think like the mac file selector?
Don't whether QComboBox supports tree models. One has to check. I can
easily provide a model to it with a tree structure.
A
Am 07.03.2008 um 16:49 schrieb Jean-Marc Lasgouttes:
Stefan Schimanski [EMAIL PROTECTED] writes:
Should we put a translation step in between the TextClass and the
layout list? If yes, how? Just a big case distinction, mapping
TextClass categories to visible category names?
You mean
Stefan Schimanski [EMAIL PROTECTED] writes:
Ok, that's what I meant. So the category there is supposed to be the
string shown in the list.
Yes.
JMarc
On Fri, Mar 07, 2008 at 04:34:25PM +0100, Stefan Schimanski wrote:
Am 07.03.2008 um 16:21 schrieb Jean-Marc Lasgouttes:
Edwin Leuven [EMAIL PROTECTED] writes:
nice.
would unnumbered not be better than starred?
Unnumbered sections, even.
And is it possible (optionally?), to show that as
Am 07.03.2008 um 19:40 schrieb Andre Poenitz:
On Fri, Mar 07, 2008 at 04:34:25PM +0100, Stefan Schimanski wrote:
Am 07.03.2008 um 16:21 schrieb Jean-Marc Lasgouttes:
Edwin Leuven [EMAIL PROTECTED] writes:
nice.
would unnumbered not be better than starred?
Unnumbered sections, even.
Am 06.03.2008 um 07:23 schrieb rgheck:
This is in. See 23501-3.
You want Layout::category().
<>
Stefan
nice.
would "unnumbered" not be better than "starred"?
Edwin Leuven <[EMAIL PROTECTED]> writes:
> nice.
>
> would "unnumbered" not be better than "starred"?
"Unnumbered sections", even.
And is it possible (optionally?), to show that as a hierarchical menu?
Or a double-column think like the mac file selector?
JMarc
Am 07.03.2008 um 16:21 schrieb Jean-Marc Lasgouttes:
Edwin Leuven <[EMAIL PROTECTED]> writes:
nice.
would "unnumbered" not be better than "starred"?
"Unnumbered sections", even.
And is it possible (optionally?), to show that as a hierarchical menu?
Or a double-column think like the mac
Am 07.03.2008 um 16:14 schrieb Edwin Leuven:
nice.
would "unnumbered" not be better than "starred"?
Should we put a translation step in between the TextClass and the
layout list? If yes, how? Just a big case distinction, mapping
TextClass categories to visible category names?
Stefan
Stefan Schimanski <[EMAIL PROTECTED]> writes:
> Should we put a translation step in between the TextClass and the
> layout list? If yes, how? Just a big case distinction, mapping
> TextClass categories to visible category names?
You mean translation by gettext? Sure.
But I am not sure this is
Stefan Schimanski <[EMAIL PROTECTED]> writes:
>> And is it possible (optionally?), to show that as a hierarchical menu?
>> Or a double-column think like the mac file selector?
>
> Don't whether QComboBox supports tree models. One has to check. I can
> easily provide a model to it with a tree
Am 07.03.2008 um 16:49 schrieb Jean-Marc Lasgouttes:
Stefan Schimanski <[EMAIL PROTECTED]> writes:
Should we put a translation step in between the TextClass and the
layout list? If yes, how? Just a big case distinction, mapping
TextClass categories to visible category names?
You mean
Stefan Schimanski <[EMAIL PROTECTED]> writes:
> Ok, that's what I meant. So the category there is supposed to be the
> string shown in the list.
Yes.
JMarc
On Fri, Mar 07, 2008 at 04:34:25PM +0100, Stefan Schimanski wrote:
>
> Am 07.03.2008 um 16:21 schrieb Jean-Marc Lasgouttes:
>
>> Edwin Leuven <[EMAIL PROTECTED]> writes:
>>
>>> nice.
>>>
>>> would "unnumbered" not be better than "starred"?
>>
>> "Unnumbered sections", even.
>>
>> And is it
Am 07.03.2008 um 19:40 schrieb Andre Poenitz:
On Fri, Mar 07, 2008 at 04:34:25PM +0100, Stefan Schimanski wrote:
Am 07.03.2008 um 16:21 schrieb Jean-Marc Lasgouttes:
Edwin Leuven <[EMAIL PROTECTED]> writes:
nice.
would "unnumbered" not be better than "starred"?
"Unnumbered sections",
32 matches
Mail list logo
