# Ruby-gnome2 + datamapper problem

**URL:** <https://www.ruby-forum.com/t/ruby-gnome2-datamapper-problem/172783>\
**Category:** Ruby-Gnome 2\
**Created:** [July 28, 2009, 1:24am UTC](https://www.ruby-forum.com/t/ruby-gnome2-datamapper-problem/172783 "2009-07-28T01:24:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![royw](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/e9bcb4/32.png) [@royw](https://www.ruby-forum.com/u/royw)\
**Post date:** [July 28, 2009, 1:24am UTC](https://www.ruby-forum.com/t/ruby-gnome2-datamapper-problem/172783/1 "2009-07-28T01:24:37Z")

</div>

Howdy,

I just upgraded my gentoo ~x86 system to use ruby-gnome2-0.19.0 and my  
apps that use datamapper are broken. Digging into it, it looks like if  
a datamapper model is accessed (either via auto\_upgrade! or just normal  
accessing), then the gtk window does not draw any children assigned to  
it.

Here’s a small demo that triggers the problem:

> <https://gist.github.com/royw/156815>

Change USE\_MODEL to be false to show the demo without the problem.

What I’m hoping is to find some advise on how to investigate this  
problem further. Also would be nice if anyone else with  
ruby-gnome2-0.19.0 and datamapper installed can run this test code to  
let me know if it’s an environment issue versus either one of the  
packages.

I’m also asking about this issue on the datamapper list.

Thank you,  
Roy

---

<div class="post-metadata">

**Author:** ![royw](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/e9bcb4/32.png) [@royw](https://www.ruby-forum.com/u/royw)\
**Post date:** [August 2, 2009, 5:24am UTC](https://www.ruby-forum.com/t/ruby-gnome2-datamapper-problem/172783/2 "2009-08-02T05:24:47Z")

</div>

Hi,

In [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
“[ruby-gnome2-devel-en] ruby-gnome2 + datamapper problem” on Tue, 28  
Jul 2009 01:24:37 +0200,  
Roy W. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> [gist:156815 · GitHub](http://gist.github.com/156815)
> 
> Change USE\_MODEL to be false to show the demo without the problem.
> 
> What I’m hoping is to find some advise on how to investigate this  
> problem further. Also would be nice if anyone else with  
> ruby-gnome2-0.19.0 and datamapper installed can run this test code to  
> let me know if it’s an environment issue versus either one of the  
> packages.
> 
> I’m also asking about this issue on the datamapper list.

It will relate to Thread.

You can find ‘Person.auto\_upgrade!’ creates a new  
thread. (FYI: Thread.list)

Could someone look into the problem? I don’t have time to  
look into the problem. :\<  
glib/src/rbglib\_maincontext.c will help you.

## Thanks,

kou

---

<div class="post-metadata">

**Author:** ![royw](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/e9bcb4/32.png) [@royw](https://www.ruby-forum.com/u/royw)\
**Post date:** [September 23, 2009, 1:41am UTC](https://www.ruby-forum.com/t/ruby-gnome2-datamapper-problem/172783/3 "2009-09-23T01:41:22Z")

</div>

Hi,

Sorry for my late work.

In [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
“Re: [ruby-gnome2-devel-en] ruby-gnome2 + datamapper problem” on Sun,  
02 Aug 2009 12:25:17 +0900 (JST),  
Kouhei S. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> > a datamapper model is accessed (either via auto\_upgrade! or just normal  
> > problem further. Also would be nice if anyone else with
> 
> Could someone look into the problem? I don’t have time to  
> look into the problem. :\<  
> glib/src/rbglib\_maincontext.c will help you.

I’ve fixed it in trunk.

## Thanks,

kou
