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 591076 - Property "name" is not exposed in the interface
Property "name" is not exposed in the interface
Status: RESOLVED FIXED
Product: glade
Classification: Applications
Component: general
3.6.x
Other All
: Normal critical
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
: 614782 648170 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-08-07 17:00 UTC by Alexey Kurochkin
Modified: 2013-05-20 12:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Alexey Kurochkin 2009-08-07 17:00:26 UTC
Please describe the problem:
Property "name" and the object id should be editable independently from each other.

Steps to reproduce:
1. Define a custom GObject with a property called "name"
2. Add the object to a catalog
3. Open Glade with that catalog and create an object


Actual results:
Property "name" does not appear in the property editor. The object ID entry appears as "Name" in the property editor, but does not affect the "name" property.

Expected results:
Entry "Name" should be called ID, and the property "name" should appear as a separate entry if it exists for the object being edited.

Does this happen every time?
Yes.

Other information:
Comment 1 Alexey Kurochkin 2009-08-07 17:42:32 UTC
I've also filed related Bug 591085 against GtkBuilder.
Comment 2 Alexey Kurochkin 2009-10-21 17:32:36 UTC
Just stumbled upon another one: "style" property is also hidden. And it's likely the whole bunch of GtkWidget related properties are handled this way. It probably does not make sense to open a separate bug for each of them.
Comment 3 Tristan Van Berkom 2009-10-21 18:21:24 UTC
No these are separate issues and will be adressed at
different times with different factors to consider:

  a.) widget names, always worked like this, question is
      old hacks now break because GtkBuilder doesnt allow
      for non-unique widget names throughout the glade file ?

  b.) style properties, Glade never edited these, it was always
      a priority on the "cool" list - first it was never done,
      mostly because GTK+ doesnt export good api to interact
      with what the theme engine is going to do to your interface
      (the theme still seems to be gray area in terms of API, maybe
      new CSS magick might open some doors for application authors, 
      this remains to be seen though).
Comment 4 Alexey Kurochkin 2009-10-21 18:59:30 UTC
(In reply to comment #3)
>   b.) style properties, Glade never edited these, it was always
>       a priority on the "cool" list - first it was never done,
>       mostly because GTK+ doesnt export good api to interact
>       with what the theme engine is going to do to your interface

I think you misunderstood me. I'm talking about my custom GObject instance which is not a GtkWidget having a property named "style" which has nothing to do with GtkStyle and themes. To my understanding it should be fixable with some construct similar to this:

if (GTK_IS_WIDGET (myobject))
{
  /* Handle properties "name", "style", etc. the old way */
}
else
{
  /* Handle properties "name", "style", etc. just like any other "foo" property */
}

And themes, yeah, it is of course completely separate issue.
Comment 5 Tristan Van Berkom 2009-10-21 20:16:57 UTC
Hmmm, and the style property does not conflict with a property name
already installed ?

The "name" property is explicitly disabled because of a policy,
which must ofcourse change in GtkBuilder before we could think
to leverage it.

If your custom property is not showing up in the property editor,
and we are loading it successfully via in the Glade run time,
then it should simply appear somewhere in the general tab.
(in which case Id also prefer a separate bug, since this one is really
closely related to the GTK+ policy).

Most property types are just going to have default editors, not
boxed types though.
Comment 6 Tristan Van Berkom 2011-02-01 13:21:12 UTC
   Historically the widget name in libglade was the name of the object,
   now we're still stuck with this inside Glade, ideally Glade should
   allow naming of widgets and setting the builder id separately
   (currently setting the "name" property in Glade only effects the
   builder object id and the <property id="name"> is never written).
Comment 7 Tristan Van Berkom 2011-10-12 08:30:07 UTC
*** Bug 614782 has been marked as a duplicate of this bug. ***
Comment 8 Tristan Van Berkom 2011-10-12 08:30:18 UTC
*** Bug 648170 has been marked as a duplicate of this bug. ***
Comment 9 Tristan Van Berkom 2011-10-12 08:39:26 UTC
Making this critical, because it's a popular bug and important feature
Comment 10 Tristan Van Berkom 2013-05-20 12:31:17 UTC
The "name" property is now available in the "Common" tab right beside
the style class list editor.