Bug 184390 - Events not being correctly handled
Summary: Events not being correctly handled
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: mono
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-08 14:04 UTC by Paul F. Johnson
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-03-09 09:37:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Example source which shows the problem when run (7.10 KB, text/plain)
2006-03-08 14:04 UTC, Paul F. Johnson
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Ximian Software (Novell) 77732 0 None None None Never

Description Paul F. Johnson 2006-03-08 14:04:17 UTC
Description of problem:
Attached is a small source code which demonstrates the problem. If you
compile it and run, select "other" from the drop down box, you are able to
type text into the number boxes, despite an event being raised. It seems
that while the event is happening, it's being ignored or incorrectly handled.

Version-Release number of selected component (if applicable):
mono-winforms-1.1.13.2-2

How reproducible:
Always

Steps to Reproduce:
1. Compile the attached source and run
2. Select "other" from the drop down
3. Type letters into the boxes
  
Actual Results:
Letters appear

Expected Results:
Nothing but numbers appear

Additional info:
Reported upstream BZ #77732

Comment 1 Paul F. Johnson 2006-03-08 14:04:18 UTC
Created attachment 125798 [details]
Example source which shows the problem when run

Comment 2 Alexander Larsson 2006-03-09 09:37:56 UTC
Please file actual mono bugs that are not packaging issues (or mega-blockers)
upstream. 

We do no development on mono and will not be able and wont have time to fix
issues such as these. Having a bug in the redhat bugtracker will not help you
get the bug fixed.




Note You need to log in before you can comment on or make changes to this bug.