ashbb / green_shoes

Green Shoes is one of the colorful Shoes written in pure Ruby.
Other
204 stars 37 forks source link

Event from alert button are (sometime) fired to the element behind alert() window! #48

Closed glurp closed 13 years ago

glurp commented 13 years ago

Hello, I do not want boring you, but, here is a old bug that can appeared furtively.

require 'green_shoes'

Shoes.app do
  flow { title "aaa" }.click { alert("aaa: move me, with the 'valid' button on the 'ccc' field, and click !") }
  flow { title "bbb" }.click { alert("bbb: move me, with the 'valid' button on the 'ccc' field, and click !") }
  flow { title "ccc" }.click { alert("You have clicked on 'ccc'") }
end

by

glurp commented 13 years ago

and same issue under Linux, same code. the alert of 'ccc' do not interfer with other title (aaa and bbb).

ashbb commented 13 years ago

Hi Regis,

Thank you for finding a bug! I confirmed and I didn't notice this strange behavior.

But coincidentally, GutenYe sent me pull requests a few days ago. His commits seem to solve this issue, too!

Try out to use alert() with :block => false option.

The default value of :block option is true for now to keep current behavior. But it may be better to reconsider again.

ashbb

ps. I notice that this issue will be happen for confirm(), ask(), etc. Need to more study for them.

glurp commented 13 years ago

Hello Ashbb

Ok for alert() , but what for ask_blabla() ? :

require 'green_shoes'

Shoes.app do
  flow { title "aaa" }.click { ask_open_file() }
  flow { title "bbb" }.click { alert("bbb: move me, with the 'valid' button
on the 'ccc' field, and click !") }
  flow { title "ccc" }.click { alert("You have clicked on 'ccc'") }
end

It is perhaps a gtk issue?

by

2011/8/25 ashbb < reply@reply.github.com>

Hi Regis,

Thank you for finding a bug! I confirmed and I didn't notice this strange behavior.

But coincidentally, GutenYe sent me pull requests a few days ago. His commits seem to solve this issue, too!

Try out to use alert with :block => false option.

The default value of :block option is true for now to keep current behavior. But it may be better to reconsider again.

ashbb

ps. I notice that this issue will be happen for confirm(), ask(), etc. Need to more study for them.

Reply to this email directly or view it on GitHub: https://github.com/ashbb/green_shoes/issues/48#issuecomment-1898823


_ . _ |) | / ` | /` | \ |_ > L| .__/

http://regisaubarede.posterous.com/


ashbb commented 13 years ago

Yeah, I intended that 'confirm(), ask(), etc.' included ask_blabla(). :-P

It is perhaps a gtk issue?

I'm not sure. But need to study how to use dialog.run.

ashbb commented 13 years ago

Hi raubarede,

Sorry, it's my fault. Ruby/GTK2 is innocent. Now fixed. Look at the commit.

ashbb

glurp commented 13 years ago

super, I will diffuse my p2p tools thes we...