GNOME.org
 

Gtkmm-forge digest, Vol 1 #1072 - 4 msgs

Send Gtkmm-forge mailing list submissions to
	gtkmm-forge lists sourceforge net

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
or, via email, send a message with subject or body 'help' to
	gtkmm-forge-request lists sourceforge net

You can reach the person managing the list at
	gtkmm-forge-admin lists sourceforge net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gtkmm-forge digest..."


gtkmm-forge is the mailing list that receives gtkmm bug reports from bugzilla.  A daily digest is sent to gtkmm-main, to encourage people to help fixing the bugs. Do not try to unsubscribe gtkmm-forge from gtkmm-list.


Today's Topics:

   1. [Bug 332446] API additions (gtkmm (bugzilla.gnome.org))
   2. [Bug 332506] gtkmm incompatible with std::wstring (gtkmm (bugzilla.gnome.org))
   3. [Bug 332506] gtkmm incompatible with std::wstring (gtkmm (bugzilla.gnome.org))
   4. [Bug 332438] Glib::ustring problems on Win32/MSVC (glibmm (bugzilla.gnome.org))

--__--__--

Message: 1
To: gtkmm-forge lists sourceforge net
From: "gtkmm (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
Date: Sun, 26 Feb 2006 05:30:17 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 332446] API additions

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D332446
 gtkmm | general | Ver: 2.8.x





------- Comment #4 from Maxim Udushlivy  2006-02-26 10:30 UTC -------
Surrendered to whom? The documentation for Managed Widgets says "you can =
let a
widget's container control when the widget is destroyed". I understand
"destroyed" here as: 1) destroyed by gtk_object_destroy and 2) freed by
operator delete when refcounter drops to zero. This means that the manage=
d
widget's lifetime (partly) depends on normal GTK+ refcounting. gtkmm trie=
s to
hide this and I think it is right, but...

The need to use RefPtr's with widgets arises in a situation when an appli=
cation
has to manage Gtk::Object's and Glib::Object's in some unified way. This =
is
tricky, because a widget may be destroyed and not freed if refcounter sti=
ll >
0; and Gtk::Window's must be finalized differently.

Ok, I revoke request for RefPtr::get() function.


Please do not close this entry, may be someone (me in some future) will p=
rovide
patches: new bugzilla entries should be opened for each case except 2)


--=20
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=3Demail
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


--__--__--

Message: 2
To: gtkmm-forge lists sourceforge net
From: "gtkmm (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
Date: Sun, 26 Feb 2006 13:25:07 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 332506] gtkmm incompatible with std::wstring

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D332506
 gtkmm | general | Ver: 2.8.x


chris cvine freeserve co uk changed:

           What    |Removed                     |Added
-------------------------------------------------------------------------=
---
                 CC|                            |chris cvine freeserve co=
.uk




------- Comment #5 from chris cvine freeserve co uk  2006-02-26 18:25 UTC=
 -------
The problem with implementing any conversion functions for std::wstring i=
s that
(unlike char) in the C and C++ standards the size of wchar_t is implement=
ation
defined.  On most Unixes it is 4, on Windows it is (I believe) 2.  Window=
s
either uses UCS-2 or UTF-16 and Unix-like systems generally use UCS-4.

Glib gets round this by not providing any conversion functions for charac=
ters
of size wchar_t.  It provides conversion functions for Unicode with chara=
cters
of size 2 (using gunichar2 which is guint16) and 4 (using gunichar which =
is
guint32).

In short, if you use std::wstring you are writing non-portable code and y=
ou
must accept the limitations that imposes.

Chris


--=20
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=3Demail
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


--__--__--

Message: 3
To: gtkmm-forge lists sourceforge net
From: "gtkmm (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
Date: Sun, 26 Feb 2006 15:41:39 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 332506] gtkmm incompatible with std::wstring

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D332506
 gtkmm | general | Ver: 2.8.x





------- Comment #6 from Real name  2006-02-26 20:41 UTC -------
Sorry, I thought no wstring because americans don't think about it. I edi=
t
ustring code myself, not too difficult to go from UCS-4 to UTF-8 and I on=
ly two
compilers. Had same problem with Microsoft and CString, but library shoul=
d not
decide how to program and make it difficult to change compiler. The wstri=
ng and
L"..." works with Thai. Again sorry for reporting problem in wrong place,=
 I
understand this will not be changed. Thank you for your time replying and=
 for
making gtkmm very good.


--=20
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=3Demail
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


--__--__--

Message: 4
To: gtkmm-forge lists sourceforge net
From: "glibmm (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
Date: Sun, 26 Feb 2006 15:49:12 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 332438] Glib::ustring problems on Win32/MSVC

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D332438
 glibmm | strings | Ver: 2.8.x


Cedric Gustin changed:

           What    |Removed                     |Added
-------------------------------------------------------------------------=
---
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1




------- Comment #4 from Cedric Gustin  2006-02-26 20:49 UTC -------

Quick fix :

Edit ustring.h in the gtkmm-devel distribution, and replace

//The IRIX MipsPro compiler says "The indicated constant value is not kno=
wn",
//so we need to initalize the static member data elsewhere.
static const size_type npos;

with

//The IRIX MipsPro compiler says "The indicated constant value is not kno=
wn",
//so we need to initalize the static member data elsewhere.
static GLIBMM_API const size_type npos;

The only difference is the GLIBMM_API tag. Rebuild your code and test.

Will commit to CVS as soon as possible


--=20
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=3Demail
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.



--__--__--

_______________________________________________
Gtkmm-forge mailing list
Gtkmm-forge lists sourceforge net
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge


End of Gtkmm-forge Digest
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]