Fabio Sgamma

> I'm not sure if it is an expected behavior. If something could not be added or removed I think it should be an error. Otherwise it is difficult to...

Hi, i think this feature could be implemented more easily when the new glutin backend arrives since it already have on WindowBuilder struct the function `pub fn with_fullscreen(self, monitor: Option)...

Hi, i made some other tests today and maybe i found a solution that need to add only 3 lines to /crate/api/src/properties/mod.rs (still testing, but should work): ``` impl IntoPropertySource...

> Maybe you could accept the Into trait in the conversion function: > https://doc.rust-lang.org/std/convert/trait.Into.html Yes, that's surely a better way to do this, with Into trait there is no need...

> About your unset suggestion I have to think. Obviously it is a forcing and I would prefer to use another method. I'm still trying to undestand what cause that...

> If you are ready and want to show it to others I'm interested in seeing what you are doing Sure, it's not a secret, simply i'm developing part by...

Hi, i think i have found what cause that error: basically every `IntoPropertySource` implementations are generated by `into_property_source!(type)` macro and it will implement all the needed `IntoPropertySource` for the passed...

Hi, i've been testing the fix on the previous post for a while and seems to work correctly and don't cause issues on widgets. I have also noticed that, for...

> This issue is duplicated check #129. It is planned for the 0.3.1-alpha5 release. Oh, sorry for that, i have looked for a similar issue but i have found none....

Sure, would you like to implement it as a replacement of the current popup or as a separate widget? Also before push i would like to understand why the popup...