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 570943 - Windows: GtkEntry can't input when toggling visibility twice
Windows: GtkEntry can't input when toggling visibility twice
Status: RESOLVED INVALID
Product: gtk+
Classification: Platform
Component: Backend: Win32
unspecified
Other Windows
: Normal normal
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2009-02-08 10:40 UTC by anheibb03dlj
Modified: 2013-10-28 14:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
a program wirtten with gtk C API to test the bug (3.50 KB, application/x-compressed-tar)
2009-03-03 05:39 UTC, anheibb03dlj
Details

Description anheibb03dlj 2009-02-08 10:40:47 UTC
Please describe the problem:
i have downloaded the gtkmm-2.4 example source. In the "gtkmm-2-4-docs\examples\book\entry\simple" sample,compile it and run,
when i toggled the "Visible" check button twice ( set_visibility(false) -> set_visibility(true) ), the entry can't input!

Steps to reproduce:
1. compile and run the "gtkmm-2-4-docs\examples\book\entry\simple" sample
2. toggle the "Visible" check button twice
3. 

Actual results:
the entry can't input


Expected results:
the entry can input

Does this happen every time?
always

Other information:
i have tested the sample with gtkmm-2.4 using mingw32 compiler in windows platform , and using gtk+2.0 has the same result.
Then i tested it in Ubuntu 8.10 ,the entry still can't input.
Comment 1 Murray Cumming 2009-02-21 13:25:03 UTC
I can't reproduce this on Ubuntu Linux 8.10. Are you sure that you are not clicking the "editable" check box?
Comment 2 anheibb03dlj 2009-02-24 03:52:10 UTC
sorry,maybe i am wrong,
In Unbuntu 8.10,the entry works well.
Comment 3 Murray Cumming 2009-02-24 09:21:28 UTC
Could you please double-check it on Windows too?
Comment 4 anheibb03dlj 2009-02-28 04:21:40 UTC
(In reply to comment #3)
> Could you please double-check it on Windows too?


Sorry for taking a long time to reply you. 

i have tested it again, the entry still couldn't input. my computer os is windows xp professional sp3, then i also have tested it on xp sp2, it has the same result.

my compile environment: 
    windows xp professional sp3
    tdm mingw 4.3.2
    gtkmm 2.4

My english is poor, sorry for any inconvenience.
Comment 5 Murray Cumming 2009-03-01 12:54:00 UTC
CCing Armin, who can at least try to reproduce this.
Comment 6 Armin Burgmeier 2009-03-02 12:44:36 UTC
I tried to reproduce, but it works for me, on Windows XP Professional SP3.

I think you mean mingw (gcc) 3.4.2, not 4.3.2, right? I am using 3.4.5, with which I also built the gtkmm binaries. I don't know how this could make a difference, but can you maybe try 3.4.5 nevertheless?
Comment 7 Murray Cumming 2009-03-02 12:50:16 UTC
anheibb03dlj, you should also try this with the C API to help identify where the problem is.
Comment 8 anheibb03dlj 2009-03-03 05:37:07 UTC
As your required, i wrote a program with gtk C API with a little change on GTK's "HelloWorld" example ( i have uploaded a attachment), and compiled it with
mingw 3.4.5 on Windows XP Professional SP3, with which i also built the gtkmm binaries. Unfortunately, the entry still couldn't input.

Maybe the reason came form my computer, not gtk or gtkmm APIs.

Thanks for all your replies and help.

At last, i want to ask that how could i close this bug if it was proved not a bug? Thanks.
Comment 9 anheibb03dlj 2009-03-03 05:39:50 UTC
Created attachment 129921 [details]
a program wirtten with gtk C API to test the bug
Comment 10 Murray Cumming 2009-03-03 09:33:00 UTC
You have proved that there is a problem with GTK+ rather than with gktmm. Why would you want to close the bug report. Reassigning to GTK+.

It does seem strange Armin can't reproduce this.
Comment 11 Armin Burgmeier 2009-03-03 10:21:58 UTC
Just for the record, I can't reproduce the problem with the C testcase either.
Comment 12 Cody Russell 2013-10-28 14:32:43 UTC
I compiled the test program and was also unable to reproduce this.