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 743260 - Popover atached to Gtk::CellEditable (cast to Gtk::Entry) not load properly
Popover atached to Gtk::CellEditable (cast to Gtk::Entry) not load properly
Status: RESOLVED OBSOLETE
Product: gtkmm
Classification: Bindings
Component: TreeView
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: gtkmm-forge
gtkmm-forge
Depends on: 743437
Blocks:
 
 
Reported: 2015-01-20 17:46 UTC by Alfredo Pons Menargues
Modified: 2018-05-22 12:13 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Example to reproduce bug (3.25 KB, application/x-xz)
2015-01-21 12:34 UTC, Alfredo Pons Menargues 		Details
extracted/concatenated test case (8.40 KB, text/plain)
2017-10-12 11:45 UTC, Daniel Boles 		Details

Description Alfredo Pons Menargues 2015-01-20 17:46:29 UTC 
Popover atached to Gtk::CellEditable (cast to Gtk::Entry) not load properly.

The PopOvers apears 1 second atached to TreeView. After disappears and reappears atached to CellEditable.

Gtk::Popover m_pop;

// Handler Cell Edit
void
MyClass::cellrenderer_validated_on_editing_started_value (Gtk::CellEditable* cell_editable, const Glib::ustring& path)
{

  Gtk::Entry* pEntry = dynamic_cast<Gtk::Entry*> (celleditable_validated);

  if (pEntry)
    {
          m_pop.set_relative_to (*pEntry);
          m_pop.set_position (Gtk::POS_RIGHT);
          .
          .
          .  
    }
}
Comment 1 Kjell Ahlstedt 2015-01-21 11:53:57 UTC 
I added a Gtk::Popover to the example program at
https://git.gnome.org/browse/gtkmm-documentation/tree/examples/book/treeview/editable_cells
but it didn't behave the way you describe. Can you please attach a complete
(but preferably short) program that can be compiled and tested.
Comment 2 Alfredo Pons Menargues 2015-01-21 12:34:45 UTC 
Created attachment 295089 [details]
Example to reproduce bug
Comment 3 Alfredo Pons Menargues 2015-01-21 12:36:01 UTC 
I used the tags (FIXME - END FIXME) to differentiate the code that I added.
Comment 4 Alfredo Pons Menargues 2015-01-21 12:36:31 UTC 
Comment on attachment 295089 [details]
Example to reproduce bug

I used the tags (FIXME - END FIXME) to differentiate the code that I added.
Comment 5 Kjell Ahlstedt 2015-01-24 09:41:56 UTC 
I have filed the gtk+ bug 743437.
Comment 6 Daniel Boles 2017-10-12 11:45:49 UTC 
Created attachment 361414 [details]
extracted/concatenated test case

Isn't this really just a duplicate of the GTK+ one?

Though in this case, with the entry editable, it does show another symptom, which may or may not be directly related: the popover sometimes briefly appears at the right place, with transition, then jumps back to the top-left of the 2nd column.

Also, there is a problem with the test case; it adds the button more than once, so it piles up these warnings:

(a.exe:7636): Gtk-WARNING **: Attempting to add a widget with type gtkmm__GtkButton to a container of type gtkmm__GtkPopover, but the widget is already inside a container of type gtkmm__GtkPopover, please remove the widget from its existing container first.
Comment 7 GNOME Infrastructure Team 2018-05-22 12:13:39 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtkmm/issues/9.