After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 572271 - 'Invisible character' for GtkEntry is not saved in .glade
'Invisible character' for GtkEntry is not saved in .glade
Status: RESOLVED FIXED
Product: glade
Classification: Applications
Component: general
3.5.x
Other All
: Normal normal
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-02-18 13:28 UTC by John
Modified: 2009-02-18 18:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description John 2009-02-18 13:28:57 UTC 
Please describe the problem:
After installing gtk+ 2.15.4, I noticed (it's hard not to) that
someone decided to replace the default 'Invisible character' for
entering passwords to a bullit (unicode 2022?). In some character
sets this is just horrible.

The thing is, I _had_ actually defined the asterisk as the character to use
in the Glade interface, and it didn't show. So I checked the .glade
code generated, and there is no corresponding property for the 
defined character.

Steps to reproduce:
1. Use a GtkEntry,
2. Set Invisible character to anything
3. Try it out (or check the .glade file


Actual results:
The default bullit appears (yuch)

Expected results:
I'd like to see my choice respected

Does this happen every time?
Yes

Other information:
Comment 1 John 2009-02-18 14:18:26 UTC 
Sorry - the 'Invisible character' is omitted from the glade file, only if
the character '*' is set in Glade3. Any other character _is_ saved.

Baseline: this means I cannot set the asterisk as invisible character now. Maybe I have to recompile Glade to get things synced again?

John
Comment 2 Tristan Van Berkom 2009-02-18 17:03:10 UTC 
ok great to know its only not saving cause its the default
value - technically we see it as a bug in gtk+ unless its overridden
by a style property, either way we can mark that baby
as save-always in our catalog.

Sorry I havent had much time for Glade lately, I do appriciate
all the bug reports and I will try to make a final sprint and
fix the uglier ones before GNOME 2.26 release time.
Comment 3 John 2009-02-18 18:02:57 UTC 
Hi Tristan - and I thought I had scared you off ;-)

The problem is that the default isn't '*' anymore. Since I installed GTK 2.15.4,
the default is unicode 2022 (a big black bullit). Glade however, still considered the '*' default, and didn't let me define it.

Anyway, I just recompiled Glade 3.5.7, and the default from GTK now propagated into Glade. Maybe this should be a run-time thing (determining which is the default) instead of compile-time.

Ok on missing time. I did some reading into the Glade code, hoping to fix some issues myself, but I am missing very basic knowledge to start working. Eg., do you access hidden widget/object properties to construct all the items in the property editor? Are those defined somewhere outside Glade?

John