Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authenticated: #13288571 Message-ID: <4352EC94.7@gmx.de> Date: Mon, 17 Oct 2005 02:13:08 +0200 From: Peace Everyone User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: EventListening References: <101520051745 DOT 25630 DOT 43514022000160940000641E22007614380A050E040D0C079D0A AT comcast DOT net> <43517099 DOT 5080908 AT byu DOT net> <82hdbh93gr DOT fsf AT vzell-de DOT de DOT oracle DOT com> <4352DE51 DOT 1030404 AT gmx DOT de> <4352DD85 DOT 6050105 AT cygwin DOT com> In-Reply-To: <4352DD85.6050105@cygwin.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-IsSubscribed: yes Peace Everyone wrote: >> I'm a noob with cygwin and have a question about EventListening, is >> there an interface or a class I can use? Or some add on libraries to >> include or do I have to write/implement my own EventListening Class? > > > That's a good question. I guess it depends on what kind of events you > want to listen for and where you believe the events are being generated. > You'll have to get much more specific about what you're trying to do > before someone on this list can offer you advice on this matter. > Okey, It's like creating events in the (Console and Graphic)UI to inform the ENGINE which data is needed. One alternative is the console based UI, u type one command and several options, from which u generate the adequate event to inform the ENGINE what data the GUI needs The other alternative is the "real" graphic based UI, with all the cute little buttons and textfields in place of the console based UI.... I hope u now understand what I mean ;) thanks for your answers Peace Everyone -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/