State-Changed-From-To: open-feedback State-Changed-By: Julian State-Changed-When: Wed Aug 25 08:53:09 PDT 2004 State-Changed-Why: Dear Eric, The issue with the pop up menu appearing while dropping in an EV_TEXT or EV_TEXT_FIELD is a bug and we believed that we had disabled this menu from appearing when completing a pick and drop to a textable widget. We just tested dropping on both an EV_TEXT an EV_TEXT_FIELD and the menu was not shown. Could you isolate this into a small test for us? Also, can you check that `allow_pick_and_drop' from EV_TEXT_COMPONENT_IMP actually calls `disable_default_processing' in the case where it fails. From: "Eric Bezault" To: "ISE Customer Support" Cc: Subject: RE: EiffelVision_2/3989 Date: Fri, 27 Aug 2004 10:10:15 -0700 > -----Original Message----- > From: ISE Customer Support [mailto:bugs@support.eiffel.com] > Sent: Wednesday, August 25, 2004 8:53 AM > To: Eric Bezault > Subject: EiffelVision_2/3989 popup menu when dropping in an EV_TEXT > > The issue with the pop up menu appearing while dropping in an > EV_TEXT or > EV_TEXT_FIELD is a bug and we believed that we had disabled > this menu from appearing when completing a pick and drop to a > textable widget. > > We just tested dropping on both an EV_TEXT an EV_TEXT_FIELD and the > menu was not shown. Could you isolate this into a small test for us? Unfortunately, I'm not even able to reproduce it on my real program. I'm currently working on my laptop and I experienced the problem on my desktop. Note that I already noticed weird things two days ago when deploying this program from my desktop (at home) to both my laptop and to computers at AXA Rosenberg. My program worked fine on my desktop, but on the other computers it ran into stack overflow. The stack overflow was due to a bug in my program: in a routine that I gave to `change_actions' of my text field I was calling `set_text' on that same text field. I had just forgotten to "block" the `change_actions' agents before calling `set_text'. I have no idea why it was working without falling into this bug when I was running the same exe on my desktop. So prehaps there is a problem with Windows on my desktop about the order in which it processes the queued messages or something like that. And perhaps the problem with the popup menu appearing when dropping a pebble is related. Would that make sense? Do you have any advice/suggestion for me to try in order to shed some light in this weird problem? Unfortunately I won't have access to my desktop until mid-september, so I won't be able to test anything on it before then. -- Eric Bezault From: "Eric Bezault" To: "ISE Customer Support" Cc: Subject: RE: EiffelVision_2/3989 Date: Fri, 10 Sep 2004 11:17:00 -0700 Hi Julian, This occurred again to me today, but on an PC at AXA Rosenberg this time. I think that I have identified a pattern. Could it be that when I drop the pebble I do some processing which will possibly call EV_APPLICATION.process_events in order to update my status bar during this processing? Perhaps the right-click is processed there, before the pick-and-drop mechanism had a chance to call `disable_default_processing'. Putting breakpoints does not show that `disable_default_processing' gets called. However when the window of my application is hidden by EiffelStudio I often get an exception in WEL_POINT.object_id called from WEL_POINT.window_of_item. There is a retry in that routine, but later on I get a precondition violation in `release_capture' ("has_capture") as soon as I try to continue using my application. So it's hard to debug the popup menu problem in such conditions. -- Eric Bezault > -----Original Message----- > From: Eric Bezault > Sent: Friday, August 27, 2004 10:10 AM > To: 'ISE Customer Support' > Subject: RE: EiffelVision_2/3989 popup menu when dropping in > an EV_TEXT > > > > -----Original Message----- > > From: ISE Customer Support [mailto:bugs@support.eiffel.com] > > Sent: Wednesday, August 25, 2004 8:53 AM > > To: Eric Bezault > > Subject: EiffelVision_2/3989 popup menu when dropping in an EV_TEXT > > > > The issue with the pop up menu appearing while dropping in an > > EV_TEXT or > > EV_TEXT_FIELD is a bug and we believed that we had disabled > > this menu from appearing when completing a pick and drop to a > > textable widget. > > > > We just tested dropping on both an EV_TEXT an EV_TEXT_FIELD and the > > menu was not shown. Could you isolate this into a small test for us? > > Unfortunately, I'm not even able to reproduce it on my > real program. I'm currently working on my laptop and > I experienced the problem on my desktop. Note that I > already noticed weird things two days ago when deploying > this program from my desktop (at home) to both my laptop > and to computers at AXA Rosenberg. My program worked fine > on my desktop, but on the other computers it ran into > stack overflow. The stack overflow was due to a bug in > my program: in a routine that I gave to `change_actions' > of my text field I was calling `set_text' on that same > text field. I had just forgotten to "block" the > `change_actions' agents before calling `set_text'. > I have no idea why it was working without falling into > this bug when I was running the same exe on my desktop. > So prehaps there is a problem with Windows on my desktop > about the order in which it processes the queued messages > or something like that. And perhaps the problem with the > popup menu appearing when dropping a pebble is related. > Would that make sense? Do you have any advice/suggestion > for me to try in order to shed some light in this weird > problem? Unfortunately I won't have access to my desktop > until mid-september, so I won't be able to test anything > on it before then. > > -- > Eric Bezault >