Qt-interest Archive, May 2008
Qt 4.4 Designer Problems (Win32 and OS X)
Pages: Prev | 1 | 2 | Next
Message 1 in thread
I've just built a fresh Win32 build of Qt 4.4 (commercial version).
Designer seems "flakey". Many of my existing forms crash designer on
load. When I create a new form, I cannot drag a list box widget to the
form. If I create a group box, then drag the list widget to the group
box, designer crashes. On a new form, if I try to drag the buttons
after resizing the form, the buttons are "shadowed" to the upper left,
then they refuse to move and revert to their original location when I
release the mouse. Restarting Designer and reopening the form file at
least fixes this problem.
Yeah... flakey.
Anyone else having similar troubles? I'm running on XP, and building
statically (before I get flamed, I've been building and using Qt
statically for four years without incident).
Even if your not having trouble, could a couple of other Windows
people chime in so that I know "for sure" that it is some
configuration quirk.
If it's helpful, here's my build procedure.
Modify mkspec file, change -MD to -MT and -MTd to -MTd, remove the
manifest lines from Config (otherwise you can't build against static C-
Runtime).
configure -debug-and-release -static -qt-gif -qt-libjpeg -qt-libpng -
qt-sql-sqlite -no-exceptions -no-qt3support -no-phonon
I'm also having problems on OS X builds with Designer making form
files that Qt won't compile. Compiler stops on qitemdelegate.h:103
QRect check(const QStyleOptionViewItem &option, const QRect &bounding,
const QVariant &variant) const;
Error message reads "error: macro "check" passed 3 arguments, but
takes just 1"
On OS X, I'm building Qt the same way, but with -no-framework and -
universal, and building against 10.4 sdk.
Richard
Message 2 in thread
I am using the 4.4 commercial on XP too (using the VC2003 build from TT),
and I am having issues with the Designer as well.
For example, when dragging "Views" (QTreeView for instance) widgets to a
form, Designer crashes. Also, when opening a form that includes that widget,
it crashes too.
It happened to me with the RC1 as well, but thought it was only a bug on my
machine since I had 2 concurrent Qt installs (now I only have 4.4)...
Pierre-Étienne
On Thu, May 1, 2008 at 11:44 AM, Richard S. Wright Jr. <
rwright@xxxxxxxxxxxxxxxxxxxxx> wrote:
> I've just built a fresh Win32 build of Qt 4.4 (commercial version).
> Designer seems "flakey". Many of my existing forms crash designer on load.
> When I create a new form, I cannot drag a list box widget to the form. If I
> create a group box, then drag the list widget to the group box, designer
> crashes. On a new form, if I try to drag the buttons after resizing the
> form, the buttons are "shadowed" to the upper left, then they refuse to move
> and revert to their original location when I release the mouse. Restarting
> Designer and reopening the form file at least fixes this problem.
>
> Yeah... flakey.
>
> Anyone else having similar troubles? I'm running on XP, and building
> statically (before I get flamed, I've been building and using Qt statically
> for four years without incident).
>
> Even if your not having trouble, could a couple of other Windows people
> chime in so that I know "for sure" that it is some configuration quirk.
>
> If it's helpful, here's my build procedure.
>
> Modify mkspec file, change -MD to -MT and -MTd to -MTd, remove the
> manifest lines from Config (otherwise you can't build against static
> C-Runtime).
>
> configure -debug-and-release -static -qt-gif -qt-libjpeg -qt-libpng
> -qt-sql-sqlite -no-exceptions -no-qt3support -no-phonon
>
> I'm also having problems on OS X builds with Designer making form files
> that Qt won't compile. Compiler stops on qitemdelegate.h:103
>
> QRect check(const QStyleOptionViewItem &option, const QRect &bounding,
> const QVariant &variant) const;
>
> Error message reads "error: macro "check" passed 3 arguments, but takes
> just 1"
>
> On OS X, I'm building Qt the same way, but with -no-framework and
> -universal, and building against 10.4 sdk.
>
> Richard
>
>
>
--
[ signature omitted ]
Message 3 in thread
Ditto, I am also getting that exact same behavior. I'm using VC2005 to
build the binaries.
Richard
On May 1, 2008, at 1:14 PM, Pierre-Étienne Messier wrote:
> I am using the 4.4 commercial on XP too (using the VC2003 build from
> TT), and I am having issues with the Designer as well.
>
> For example, when dragging "Views" (QTreeView for instance) widgets
> to a form, Designer crashes. Also, when opening a form that includes
> that widget, it crashes too.
>
> It happened to me with the RC1 as well, but thought it was only a
> bug on my machine since I had 2 concurrent Qt installs (now I only
> have 4.4)...
>
> Pierre-Étienne
>
>
> On Thu, May 1, 2008 at 11:44 AM, Richard S. Wright Jr. <rwright@xxxxxxxxxxxxxxxxxxxxx
> > wrote:
> I've just built a fresh Win32 build of Qt 4.4 (commercial version).
>
> Designer seems "flakey". Many of my existing forms crash designer on
> load. When I create a new form, I cannot drag a list box widget to
> the form. If I create a group box, then drag the list widget to the
> group box, designer crashes. On a new form, if I try to drag the
> buttons after resizing the form, the buttons are "shadowed" to the
> upper left, then they refuse to move and revert to their original
> location when I release the mouse. Restarting Designer and reopening
> the form file at least fixes this problem.
>
> Yeah... flakey.
>
> Anyone else having similar troubles? I'm running on XP, and building
> statically (before I get flamed, I've been building and using Qt
> statically for four years without incident).
>
> Even if your not having trouble, could a couple of other Windows
> people chime in so that I know "for sure" that it is some
> configuration quirk.
>
> If it's helpful, here's my build procedure.
>
> Modify mkspec file, change -MD to -MT and -MTd to -MTd, remove the
> manifest lines from Config (otherwise you can't build against static
> C-Runtime).
>
> configure -debug-and-release -static -qt-gif -qt-libjpeg -qt-libpng -
> qt-sql-sqlite -no-exceptions -no-qt3support -no-phonon
>
> I'm also having problems on OS X builds with Designer making form
> files that Qt won't compile. Compiler stops on qitemdelegate.h:103
>
> QRect check(const QStyleOptionViewItem &option, const QRect
> &bounding,
> const QVariant &variant) const;
>
> Error message reads "error: macro "check" passed 3 arguments, but
> takes just 1"
>
> On OS X, I'm building Qt the same way, but with -no-framework and -
> universal, and building against 10.4 sdk.
>
> Richard
>
>
>
>
>
> --
> Pierre-Étienne Messier
> Courriel : pierre.etienne.messier@xxxxxxxxx
> OpenPGP ID : 1024D/9BDBDDF6
> Web : http://pemessier.hexpresso.org/
> Jabber : SiLiZiUMM@xxxxxxxxxx
Message 4 in thread
On 1 maj 2008, at 17.44, Richard S. Wright Jr. wrote:
> ...snip
> I'm also having problems on OS X builds with Designer making form
> files that Qt won't compile. Compiler stops on qitemdelegate.h:103
>
> QRect check(const QStyleOptionViewItem &option, const QRect
> &bounding,
> const QVariant &variant) const;
>
> Error message reads "error: macro "check" passed 3 arguments, but
> takes just 1"
>
> On OS X, I'm building Qt the same way, but with -no-framework and -
> universal, and building against 10.4 sdk.
>
> Richard
>
>
This is easy. You are using the name of a macro for the name of a
method. Find and resolve the conflict.
------
What is a woman that you forsake her, and the hearth fire and the home
acre,
to go with the old grey Widow Maker. --Kipling, harp song of the Dane
women
Tommy Nordgren
tommy.nordgren@xxxxxxxxx
--
[ signature omitted ]
Message 5 in thread
On 1 maj 2008, at 19.29, Tommy Nordgren wrote:
>
> On 1 maj 2008, at 17.44, Richard S. Wright Jr. wrote:
>
>> ...snip
>
>> I'm also having problems on OS X builds with Designer making form
>> files that Qt won't compile. Compiler stops on qitemdelegate.h:103
>>
>> QRect check(const QStyleOptionViewItem &option, const QRect
>> &bounding,
>> const QVariant &variant) const;
>>
>> Error message reads "error: macro "check" passed 3 arguments, but
>> takes just 1"
>>
>> On OS X, I'm building Qt the same way, but with -no-framework and -
>> universal, and building against 10.4 sdk.
>>
>> Richard
>>
>>
> This is easy. You are using the name of a macro for the name of a
> method. Find and resolve the conflict.
By the way, the macro check is defined in '/usr/include/
Assertmacros.h' on Mac OS X
>
> ------
> What is a woman that you forsake her, and the hearth fire and the
> home acre,
> to go with the old grey Widow Maker. --Kipling, harp song of the
> Dane women
> Tommy Nordgren
> tommy.nordgren@xxxxxxxxx
-----------------------------------
See the amazing new SF reel: Invasion of the man eating cucumbers from
outer space.
On congratulations for a fantastic parody, the producer replies :
"What parody?"
Tommy Nordgren
tommy.nordgren@xxxxxxxxx
--
[ signature omitted ]
Message 6 in thread
A bit odd don't you think that I can no longer use a standard C/C++
feature... removing #include<assert.h>, and using Q_ASSERT instead of
assert() fixed the problem.
I know it's a bit subjective to call it a bug, but I've never had to
re-engineer working vanilla C/C++ code to work in a Qt project before
4.4.
I knew when I saw this that it was an errant macro... but I thought it
was in Qt's designer generated/included code, not from the standard C
library.
Richard
On May 1, 2008, at 1:44 PM, Tommy Nordgren wrote:
>
> On 1 maj 2008, at 19.29, Tommy Nordgren wrote:
>
>>
>> On 1 maj 2008, at 17.44, Richard S. Wright Jr. wrote:
>>
>>> ...snip
>>
>>> I'm also having problems on OS X builds with Designer making form
>>> files that Qt won't compile. Compiler stops on qitemdelegate.h:103
>>>
>>> QRect check(const QStyleOptionViewItem &option, const QRect
>>> &bounding,
>>> const QVariant &variant) const;
>>>
>>> Error message reads "error: macro "check" passed 3 arguments, but
>>> takes just 1"
>>>
>>> On OS X, I'm building Qt the same way, but with -no-framework and -
>>> universal, and building against 10.4 sdk.
>>>
>>> Richard
>>>
>>>
>> This is easy. You are using the name of a macro for the name of a
>> method. Find and resolve the conflict.
>
> By the way, the macro check is defined in '/usr/include/
> Assertmacros.h' on Mac OS X
>>
>> ------
>> What is a woman that you forsake her, and the hearth fire and the
>> home acre,
>> to go with the old grey Widow Maker. --Kipling, harp song of the
>> Dane women
>> Tommy Nordgren
>> tommy.nordgren@xxxxxxxxx
>
> -----------------------------------
> See the amazing new SF reel: Invasion of the man eating cucumbers
> from outer space.
> On congratulations for a fantastic parody, the producer replies :
> "What parody?"
>
> Tommy Nordgren
> tommy.nordgren@xxxxxxxxx
>
>
>
> --
> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx
> with "unsubscribe" in the subject or the body.
> List archive and information: http://lists.trolltech.com/qt-interest/
>
--
[ signature omitted ]
Message 7 in thread
Hi,
> A bit odd don't you think that I can no longer use a standard C/C++
> feature... removing #include<assert.h>, and using Q_ASSERT instead of
> assert() fixed the problem.
>
> I know it's a bit subjective to call it a bug, but I've never had to
> re-engineer working vanilla C/C++ code to work in a Qt project before 4.4.
It happens from time to time that a (system) header file defines a macro that
breaks header files included after it. For example this problem is very severe
with X11.
Fix this by including <assert.h> and other system header files last, or at
least after Qt header files.
One could argue that adding a "check" macro to <assert.h> is a bug, since
"check" is not in the C or POSIX standard. However on all platforms, system
headers always end up defining macros and symbols that do not fall in the
strict C or POSIX standard. It's usually possible to define a macro to switch
between:
* conformance to (some version of) ISO C
* conformance to (some version of) POSIX / Single Unix Specification
* additional vendor extensions
* ...
Therefore I don't think it's worth reporting to Apple. At least you should
first check whether "check" can be disabled by defining some macro.
--
[ signature omitted ]
Message 8 in thread
Dimitri,
Thanks, I guess I've just gotten lucky so far :-) This make sense,
it's a wonder this is the first time I've encountered this. A little
wiser now, thanks.
Richard
On May 2, 2008, at 2:36 AM, Dimitri wrote:
> Hi,
>
>> A bit odd don't you think that I can no longer use a standard C/C++
>> feature... removing #include<assert.h>, and using Q_ASSERT instead
>> of assert() fixed the problem.
>> I know it's a bit subjective to call it a bug, but I've never had
>> to re-engineer working vanilla C/C++ code to work in a Qt project
>> before 4.4.
>
> It happens from time to time that a (system) header file defines a
> macro that breaks header files included after it. For example this
> problem is very severe with X11.
>
> Fix this by including <assert.h> and other system header files last,
> or at least after Qt header files.
>
> One could argue that adding a "check" macro to <assert.h> is a bug,
> since "check" is not in the C or POSIX standard. However on all
> platforms, system headers always end up defining macros and symbols
> that do not fall in the strict C or POSIX standard. It's usually
> possible to define a macro to switch between:
> * conformance to (some version of) ISO C
> * conformance to (some version of) POSIX / Single Unix Specification
> * additional vendor extensions
> * ...
> Therefore I don't think it's worth reporting to Apple. At least you
> should first check whether "check" can be disabled by defining some
> macro.
>
> --
> Dimitri
>
> --
> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx
> with "unsubscribe" in the subject or the body.
> List archive and information: http://lists.trolltech.com/qt-interest/
>
--
[ signature omitted ]
Message 9 in thread
Richard S. Wright Jr. wrote:
> I've just built a fresh Win32 build of Qt 4.4 (commercial version).
>
> Designer seems "flakey". Many of my existing forms crash designer on
> load. When I create a new form, I cannot drag a list box widget to the
> form. If I create a group box, then drag the list widget to the group
> box, designer crashes. On a new form, if I try to drag the buttons
> after resizing the form, the buttons are "shadowed" to the upper left,
> then they refuse to move and revert to their original location when I
> release the mouse. Restarting Designer and reopening the form file at
> least fixes this problem.
>
> Yeah... flakey.
>
> Anyone else having similar troubles? I'm running on XP, and building
> statically (before I get flamed, I've been building and using Qt
> statically for four years without incident).
>
> Even if your not having trouble, could a couple of other Windows
> people chime in so that I know "for sure" that it is some
> configuration quirk.
> [SNIP]
I could reproduce neither your problems, nor the problems of
Pierre-Étienne Messier. I ran designer both from the precompiled
(vs2003) package, and compiled with your configure switches (Visual
Studio 2005, Vista).
This is what I tested:
- Create Dialog with Buttons Right
- Drag Tree Widget into the dialog
- Drag Group Box into the dialog
- Drag Tree Widget into the Group Box
- Resize form
- Move Buttons around
Please make sure that you don't have any stale files lying around. Also
try to delete the Trolltech files in your Documents and Settings folder.
Maybe you can even compile designer in debugging mode, and get a stack
trace for the crashes?
Kai Koehne
--
[ signature omitted ]
Message 10 in thread
Hello,
I installed 4.4 (qt-win-commercial-4.4.0-vs2003.exe) on a PC that never had
Qt installed before. The problem does not appear on this computer (I can
drag View widgets within the form).
The only Trolltech files I had lying in my Documents and Settings folder
were for Assistant. Deleting them didn't help.
P-É
On Fri, May 2, 2008 at 6:40 AM, Kai Koehne <kai.koehne@xxxxxxxxxxxxx> wrote:
> Richard S. Wright Jr. wrote:
>
> > I've just built a fresh Win32 build of Qt 4.4 (commercial version).
> >
> > Designer seems "flakey". Many of my existing forms crash designer on
> > load. When I create a new form, I cannot drag a list box widget to the form.
> > If I create a group box, then drag the list widget to the group box,
> > designer crashes. On a new form, if I try to drag the buttons after resizing
> > the form, the buttons are "shadowed" to the upper left, then they refuse to
> > move and revert to their original location when I release the mouse.
> > Restarting Designer and reopening the form file at least fixes this problem.
> >
> > Yeah... flakey.
> >
> > Anyone else having similar troubles? I'm running on XP, and building
> > statically (before I get flamed, I've been building and using Qt statically
> > for four years without incident).
> >
> > Even if your not having trouble, could a couple of other Windows people
> > chime in so that I know "for sure" that it is some configuration quirk.
> > [SNIP]
> >
> I could reproduce neither your problems, nor the problems of
> Pierre-Étienne Messier. I ran designer both from the precompiled (vs2003)
> package, and compiled with your configure switches (Visual Studio 2005,
> Vista).
>
> This is what I tested:
> - Create Dialog with Buttons Right
> - Drag Tree Widget into the dialog
> - Drag Group Box into the dialog
> - Drag Tree Widget into the Group Box
> - Resize form
> - Move Buttons around
>
> Please make sure that you don't have any stale files lying around. Also
> try to delete the Trolltech files in your Documents and Settings folder.
> Maybe you can even compile designer in debugging mode, and get a stack trace
> for the crashes?
>
> Kai Koehne
>
--
[ signature omitted ]
Message 11 in thread
Pierre-Étienne Messier wrote:
> Hello,
>
> I installed 4.4 (qt-win-commercial-4.4.0-vs2003.exe) on a PC that
> never had Qt installed before. The problem does not appear on this
> computer (I can drag View widgets within the form).
>
> The only Trolltech files I had lying in my Documents and Settings
> folder were for Assistant. Deleting them didn't help.
>
> P-É
Hi,
Here are some things you can try out:
- Empty the plugin cache - delete registry keys under
HKEY_CURRENT_USER\Software\Trolltech\OrganizationDefaults
- Disable alien: Do "set QT_USE_NATIVE_WINDOWS=1" on the command line
and start designer from within this shell
- Close all other programs running in the background.
Qt-4.4 seems to have sometimes problems with programs that access the MS
Accessibility interface ... Popular programs using this interface are
Microsoft Narrator and Notepad++. This will soon be published on the
known-issues page.
Regards
Kai Koehne
--
[ signature omitted ]
Message 12 in thread
Ah ha!
- Empty the plugin cache: didn't help.
- Disable alien: works
- Closing Notepad++ : WORKS. Why is that? Is there a workaround (except
disabling alien)? And will my programs compiled with 4.4 will interfere with
this interface?
Thanks again,
P-É
On Fri, May 2, 2008 at 10:27 AM, Kai Koehne <kai.koehne@xxxxxxxxxxxxx>
wrote:
> Pierre-Étienne Messier wrote:
>
> > Hello,
> >
> > I installed 4.4 (qt-win-commercial-4.4.0-vs2003.exe) on a PC that never
> > had Qt installed before. The problem does not appear on this computer (I can
> > drag View widgets within the form).
> >
> > The only Trolltech files I had lying in my Documents and Settings folder
> > were for Assistant. Deleting them didn't help.
> >
> > P-É
> >
> Hi,
>
> Here are some things you can try out:
>
> - Empty the plugin cache - delete registry keys under
> HKEY_CURRENT_USER\Software\Trolltech\OrganizationDefaults
> - Disable alien: Do "set QT_USE_NATIVE_WINDOWS=1" on the command line and
> start designer from within this shell
> - Close all other programs running in the background.
>
> Qt-4.4 seems to have sometimes problems with programs that access the MS
> Accessibility interface ... Popular programs using this interface are
> Microsoft Narrator and Notepad++. This will soon be published on the
> known-issues page.
>
> Regards
>
> Kai Koehne
>
--
[ signature omitted ]
Message 13 in thread
Pierre-Étienne Messier wrote:
> - Empty the plugin cache: didn't help.
> - Disable alien: works
> - Closing Notepad++ : WORKS. Why is that? Is there a workaround (except
> disabling alien)? And will my programs compiled with 4.4 will interfere
> with this interface?
The latest version of Notepad++ doesn't use Accessibility, so the
problem won't appear in this case.
Right now the only workaround is to disable alien. This problem has
already been fixed for 4.4.1, which is available in snapshots.
Yes, your programs running with 4.4.0 libraries might have some problems
with widgets that are based on QAbstractScrollArea. The problem is rare
though and right now occurs in Designer and Assistant only.
--
[ signature omitted ]
Message 14 in thread
Just to be clear... Closing Notepad++, but _not_ disabling Alien
_does_ work? I don't have Notepad++, but I do have a bunch of
"corporate crap" put on my laptop "for me". If there are some
accessibility interactions, this could be it.
Richard
On May 2, 2008, at 11:07 AM, Pierre-Étienne Messier wrote:
> Ah ha!
>
> - Empty the plugin cache: didn't help.
> - Disable alien: works
> - Closing Notepad++ : WORKS. Why is that? Is there a workaround
> (except disabling alien)? And will my programs compiled with 4.4
> will interfere with this interface?
>
> Thanks again,
>
> P-É
>
> On Fri, May 2, 2008 at 10:27 AM, Kai Koehne
> <kai.koehne@xxxxxxxxxxxxx> wrote:
> Pierre-Étienne Messier wrote:
> Hello,
>
> I installed 4.4 (qt-win-commercial-4.4.0-vs2003.exe) on a PC that
> never had Qt installed before. The problem does not appear on this
> computer (I can drag View widgets within the form).
>
> The only Trolltech files I had lying in my Documents and Settings
> folder were for Assistant. Deleting them didn't help.
>
> P-É
> Hi,
>
> Here are some things you can try out:
>
> - Empty the plugin cache - delete registry keys under
> HKEY_CURRENT_USER\Software\Trolltech\OrganizationDefaults
> - Disable alien: Do "set QT_USE_NATIVE_WINDOWS=1" on the command
> line and start designer from within this shell
> - Close all other programs running in the background.
>
> Qt-4.4 seems to have sometimes problems with programs that access
> the MS Accessibility interface ... Popular programs using this
> interface are Microsoft Narrator and Notepad++. This will soon be
> published on the known-issues page.
>
> Regards
>
> Kai Koehne
>
>
>
> --
> Pierre-Étienne Messier
> Courriel : pierre.etienne.messier@xxxxxxxxx
> OpenPGP ID : 1024D/9BDBDDF6
> Web : http://pemessier.hexpresso.org/
> Jabber : SiLiZiUMM@xxxxxxxxxx
Message 15 in thread
Yes that's it, closing Notepad++ and not disabling Alien works. In fact,
when re-opening NP++ I noticed the update and downloaded it. Now Designer
works fine with the latest NP++ version :)
That's a very weird bug indeed!
P-É
On Fri, May 2, 2008 at 11:20 AM, Richard S. Wright Jr. <
rwright@xxxxxxxxxxxxxxxxxxxxx> wrote:
> Just to be clear... Closing Notepad++, but _not_ disabling Alien _does_
> work? I don't have Notepad++, but I do have a bunch of "corporate crap" put
> on my laptop "for me". If there are some accessibility interactions, this
> could be it.
> Richard
>
> On May 2, 2008, at 11:07 AM, Pierre-Étienne Messier wrote:
>
> Ah ha!
>
> - Empty the plugin cache: didn't help.
> - Disable alien: works
> - Closing Notepad++ : WORKS. Why is that? Is there a workaround (except
> disabling alien)? And will my programs compiled with 4.4 will interfere with
> this interface?
>
> Thanks again,
>
> P-É
>
> On Fri, May 2, 2008 at 10:27 AM, Kai Koehne <kai.koehne@xxxxxxxxxxxxx>
> wrote:
>
> > Pierre-Étienne Messier wrote:
> >
> > > Hello,
> > >
> > > I installed 4.4 (qt-win-commercial-4.4.0-vs2003.exe) on a PC that
> > > never had Qt installed before. The problem does not appear on this computer
> > > (I can drag View widgets within the form).
> > >
> > > The only Trolltech files I had lying in my Documents and Settings
> > > folder were for Assistant. Deleting them didn't help.
> > >
> > > P-É
> > >
> > Hi,
> >
> > Here are some things you can try out:
> >
> > - Empty the plugin cache - delete registry keys under
> > HKEY_CURRENT_USER\Software\Trolltech\OrganizationDefaults
> > - Disable alien: Do "set QT_USE_NATIVE_WINDOWS=1" on the command line
> > and start designer from within this shell
> > - Close all other programs running in the background.
> >
> > Qt-4.4 seems to have sometimes problems with programs that access the MS
> > Accessibility interface ... Popular programs using this interface are
> > Microsoft Narrator and Notepad++. This will soon be published on the
> > known-issues page.
> >
> > Regards
> >
> > Kai Koehne
> >
>
>
>
> --
> Pierre-Étienne Messier
> Courriel : pierre.etienne.messier@xxxxxxxxx
> OpenPGP ID : 1024D/9BDBDDF6
> Web : http://pemessier.hexpresso.org/
> Jabber : SiLiZiUMM@xxxxxxxxxx
>
>
>
--
[ signature omitted ]
Pages: Prev | 1 | 2 | Next
