Menu
▾
▴
[openMSX-devel] [ openmsx-Feature Requests-1171999 ] Support blueMSX' keyboard config files
|
From: SourceForge.net <no...@so...> - 2008-02-12 10:35:12
|
Feature Requests item #1171999, was opened at 2005-03-28 17:59 Message generated for change (Comment added) made by utuhiro78 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421864&aid=1171999&group_id=38274 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General/misc Group: None Status: Closed Priority: 5 Private: No Submitted By: UTUMI Hirosi (utuhiro78) Assigned to: Alex Wulms (awulms) Summary: Support blueMSX' keyboard config files Initial Comment: You know blueMSX has a cool keyboard editor. (Try Tools -> Keyboard Editor) We can generate new key mappings easily. Please support blueMSX' keyboard config files. I checked openMSX' "keymap.default" file, but it seems difficult to change it for most users. Thanks for reading. openMSX is so cool! ---------------------------------------------------------------------- >Comment By: UTUMI Hirosi (utuhiro78) Date: 2008-02-12 10:35 Message: Logged In: YES user_id=969019 Originator: YES > can we contact you to test the upcoming automatic KANA-lock code? Yes. Please use this address: utuhiro78 at users.sourceforge.net ---------------------------------------------------------------------- Comment By: Manuel Bilderbeek (manuelbi) Date: 2008-02-12 10:03 Message: Logged In: YES user_id=78178 Originator: NO Hi again, Thank you for your fast replies! Ah, you just took the last CVS code. That code is from September 2006... Please do not use CVS anymore, that code is not updated anymore. We only use SVN now. About the noise: GLEW has nothing to do with sound, so I can't explain that the noise was gone when building with GLEW... Maybe you used SDLGL-PP renderer, which needs GLEW and uses less CPU cycles. Anyway, I'm happy that jp106 keys work now! I'll close this tracker item. Please reopen if you find more problems (or check out the other tracker item I mentioned in my previous post). Also, if you have any questions or problems, please contact us. Thanks! By the way, can we contact you to test the upcoming automatic KANA-lock code? (And maybe other things that are related to Japanese keyboards.) ---------------------------------------------------------------------- Comment By: UTUMI Hirosi (utuhiro78) Date: 2008-02-12 04:58 Message: Logged In: YES user_id=969019 Originator: YES Hello, I found the message "too many nested evaluations (infinite loop?)" in the terminal. I thought "My config files might be old" and it was right. I copied the latest config files from openMSX/share/ and jp106 keys work fine now. I installed the CVS snapshot first and overwrote the SVN snapshot without updating the local configs. I think it caused the annoying behavior. Some jp106 keys didn't work on the CVS snapshot, but they work fine on the SVN trunk. Thank you for the work! We can close this bug. For a reminder, I leave my old messages: // I've got the "CVS snapshot" by $ cvs -z3 -d:pserver:ano...@op...:/cvsroot/openmsx co -P openMSX and the "SVN trunk" by $ svn co https://openmsx.svn.sourceforge.net/svnroot/openmsx/openmsx/trunk openmsx $ openmsx -machine Sony_HB-F900 Start up MSX BASIC Press Shift + 1,2,3,4,5,6,7,8 On the CVS snapshot: It shows !"#$%&'( and it's OK. On the SVN snapshot: It shows !*#$%':) and it is not correct. The noise was gone after I built openMSX-CVS with GLEW. // ---------------------------------------------------------------------- Comment By: Manuel Bilderbeek (manuelbi) Date: 2008-02-11 16:58 Message: Logged In: YES user_id=78178 Originator: NO Um, what do you mean with "CVS snapshot"? Do you mean "SVN snapshot"? (We are not using CVS anymore since more than a year and there are no CVS snapshots available on our web site since then...) Can you tell us what works and what does not work, exactly? And what MSX machine you're emulating? Maybe it's useful to join us on IRC, check out #openMSX on irc.freenode.net. Then we can discuss in detail, without filling this tracker :) Finally: thank you for your nice words! About keyboard support, please also keep an eye on this other tracker item: http://sourceforge.net/tracker/index.php?func=detail&aid=563780&group_id=38274&atid=421864 I know that awulms (Alex) bought a Japanese keyboard and is trying to get the automatic KANA lock pressing working. I was hoping that most keys would work on current SVN head (indeed r7596). ---------------------------------------------------------------------- Comment By: UTUMI Hirosi (utuhiro78) Date: 2008-02-11 15:42 Message: Logged In: YES user_id=969019 Originator: YES hmm, Most jp106 model keys work fine on the latest CVS snapshot, but the sound is very noisy. The jp106 model keys doesn't work on SVN-r7596 (trunk), but the sound is clear. It is difficult to choose one of them. :-) Anyway, thank you for maintaining the great work! ---------------------------------------------------------------------- Comment By: Manuel Bilderbeek (manuelbi) Date: 2008-02-11 13:18 Message: Logged In: YES user_id=78178 Originator: NO Maybe I'm wrong, but I think with the new keyboard routines by awulms, it is not necessary anymore to edit keyboard configuration files at all (maybe only in very special circumstances). Maybe you can try out the latest SVN source code and see if those new keyboard routines already fix any problem you may have with keyboard configuration. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421864&aid=1171999&group_id=38274 |