On Thu, 13 Feb 2014 20:25:12 +0530 Mayur K <emineme...@gmail.com> said:
> Hi, > > I am trying to understand what the _Evas_Event_Key_Down::key signifies. > >From the documentation, it is : > ===== > const char * _Evas_Event_Key_Down::key > The logical key : (eg shift+1 == exclamation) > ====== > Hence it looks like some ascii string for the key, but on printing it, it > appears to be junk for non-latin chars. > I have checked with Cyrillic keyboard. > Can some one shed some light on this field? key and keyname are the NAME of the key (one including any modifiers the other the name of the key without modifiers like shift etc. - so key changes based on modifer keyname does not). these strings are always simple ascii strings. they are the same strings you will get from xev on keysyms etc. - we just fetch them from x as a string and put them into the event struct for convenience). for framebuffer we have a table built into ecore_fb - for other os's we need to translate so they look like x keysym etc. names as above. the "string" member and "compose" will be different. these will contain utf8 strings... so if you are looking at non-ascii chars.. they will be in utf8. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
