Menu
▾
▴
openmsx-bugs — Bug mails
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(14) |
Jun
(24) |
Jul
|
Aug
(6) |
Sep
(6) |
Oct
(1) |
Nov
|
Dec
(18) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(16) |
Feb
(5) |
Mar
|
Apr
(4) |
May
(10) |
Jun
(9) |
Jul
(4) |
Aug
|
Sep
(3) |
Oct
(4) |
Nov
(13) |
Dec
(15) |
| 2004 |
Jan
(23) |
Feb
(22) |
Mar
(24) |
Apr
(18) |
May
(17) |
Jun
(1) |
Jul
(4) |
Aug
(3) |
Sep
(22) |
Oct
(22) |
Nov
(7) |
Dec
(15) |
| 2005 |
Jan
(10) |
Feb
(5) |
Mar
(19) |
Apr
(14) |
May
(17) |
Jun
(8) |
Jul
(13) |
Aug
(1) |
Sep
(22) |
Oct
(12) |
Nov
(9) |
Dec
(16) |
| 2006 |
Jan
(10) |
Feb
|
Mar
|
Apr
(6) |
May
(3) |
Jun
(2) |
Jul
(10) |
Aug
(11) |
Sep
(29) |
Oct
(1) |
Nov
(11) |
Dec
(13) |
| 2007 |
Jan
(17) |
Feb
(14) |
Mar
(4) |
Apr
(5) |
May
(9) |
Jun
(3) |
Jul
(8) |
Aug
(9) |
Sep
(5) |
Oct
(5) |
Nov
(5) |
Dec
(17) |
| 2008 |
Jan
(7) |
Feb
|
Mar
(2) |
Apr
|
May
(3) |
Jun
(1) |
Jul
(4) |
Aug
|
Sep
|
Oct
(2) |
Nov
(5) |
Dec
|
| 2009 |
Jan
(36) |
Feb
(21) |
Mar
(62) |
Apr
(13) |
May
(15) |
Jun
(36) |
Jul
(8) |
Aug
(22) |
Sep
(2) |
Oct
(13) |
Nov
(15) |
Dec
(7) |
| 2010 |
Jan
(30) |
Feb
(60) |
Mar
(27) |
Apr
(1) |
May
(10) |
Jun
(12) |
Jul
(10) |
Aug
(4) |
Sep
|
Oct
|
Nov
(9) |
Dec
(9) |
| 2011 |
Jan
(2) |
Feb
(3) |
Mar
(9) |
Apr
|
May
(5) |
Jun
(21) |
Jul
(15) |
Aug
(14) |
Sep
(9) |
Oct
(6) |
Nov
(3) |
Dec
(2) |
| 2012 |
Jan
(14) |
Feb
(1) |
Mar
(7) |
Apr
(7) |
May
(14) |
Jun
(2) |
Jul
(9) |
Aug
(8) |
Sep
(12) |
Oct
(2) |
Nov
(1) |
Dec
(27) |
| 2013 |
Jan
(4) |
Feb
(19) |
Mar
(3) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
1
|
|
2
|
3
(9) |
4
|
5
(1) |
6
|
7
|
8
|
|
9
|
10
|
11
|
12
|
13
|
14
|
15
(8) |
|
16
(1) |
17
|
18
|
19
(1) |
20
(1) |
21
|
22
(3) |
|
23
|
24
(1) |
25
|
26
|
27
|
28
(2) |
29
|
|
30
|
31
|
|
|
|
|
|
|
From: SourceForge.net <no...@so...> - 2012-12-28 20:12:49
|
Bugs item #1515567, was opened at 2006-07-01 08:03 Message generated for change (Comment added) made by manuelbi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=1515567&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: Graphics Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Nobody/Anonymous (nobody) Summary: VDP Pirates shouldn't work on some TMS VDP's Initial Comment: The VDP Pirates demo does not run properly on (at least) one real Toshiba HX-10, while it does run on openMSX's HX-10. Attached is a ROM and a screenshot of the result on the real HX-10 (it blinks). See also http://www.msx.org/VDP-Pirates-Demo.newspost3752.html ---------------------------------------------------------------------- >Comment By: Manuel Bilderbeek (manuelbi) Date: 2012-12-28 12:12 Message: <hap> the cause is the extra mask on pattern table on 99xx <hap> that doesn't happen on 91xx <hap> (or v9938) <hap> pattern mask becomes (p_mask & 0x3800) | (c_mask & 0x7ff) <hap> instead of (p_mask & 0x3800) | 0x7ff <hap> it is the feature mentioned here http://www.msx.org/forum/development/msx-development/new-hybrid-mode-found ---------------------------------------------------------------------- Comment By: Manuel Bilderbeek (manuelbi) Date: 2008-06-11 11:51 Message: Logged In: YES user_id=78178 Originator: YES I reproduced this problem also on my own Toshiba HX-10, exactly like the screenshot. The demo works fine on a Sony HB-201P (which should also have a TMS VDP). ---------------------------------------------------------------------- Comment By: Manuel Bilderbeek (manuelbi) Date: 2007-04-12 10:34 Message: Logged In: YES user_id=78178 Originator: YES The same happens on my real Yashica YC-64. I couldn't run the demo on real MSX2's either: it hung with "VDP test" on the screen. I'm not sure if this is caused by my Flash device or another problem in this demo. The VDP test works fine on the MSX1 machines. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=1515567&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-28 20:11:21
|
Bugs item #3598181, was opened at 2012-12-22 12:58 Message generated for change (Comment added) made by manuelbi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3598181&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: Graphics Group: None >Status: Closed >Resolution: Duplicate Priority: 3 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Nobody/Anonymous (nobody) Summary: Certain hybrid mode in 99x8 (and not 911x) not implemented Initial Comment: See http://www.msx.org/forum/development/msx-development/new-hybrid-mode-found for all details. ---------------------------------------------------------------------- >Comment By: Manuel Bilderbeek (manuelbi) Date: 2012-12-28 12:11 Message: According to hap, this is a dupe of 1515567... so closing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3598181&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-24 12:17:10
|
Bugs item #2946167, was opened at 2010-02-04 13:05 Message generated for change (Comment added) made by m9710797 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=2946167&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: Open Resolution: None Priority: 5 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Nobody/Anonymous (nobody) Summary: Fast!DiskROM doesn't detect drives if no disk is inserted Initial Comment: Here's an edited e-mail conversation I had with FRS: The Fast!DiskROM extension I tested here on both Expert 1.1, Hotbit 1.2 and Panasonic FS-A1 and I did notice that if there isn't any disk inserted on the drive on the MSX boot, the Fast!Rom is detecting 0 physical and 0 logical disk drives. If you boot the machine with a disk inserted on the drive it works, so there's something wrong with the WDC2793 emulation. I have two real interfaces (One DMX-1.2 clone and one DDX-3.0) upgraded to use the Fast!DiskROM, and the real hardware is always detected properly when no disk is inserted. I believe the WDC2793 emulation bug isn't affecting the other DiskBIOSses because all of them assume that there's at least one floopydrive connected to the systems and just try to detect the second drive. Fast!DiskROM, OTOH, always try to detect up to 4 drives on boot and will map the detected physical drives (DS0, DS1, DS2, DS3) on the order they're found. This means, for example, that you can have a PC drive that is hardcoded to DS1 connected to your MSX and the Fast!DiskROM will map it correctly as the drive A:. The standard MSX diskBIOSses will only map the DS1 drive as the B: drive. To make sure it wasn't a limitation of the CDX-2 hardware (known for not being able to detect if there was a disk inserted on the drive) I created another Fast!DiskROM extension file, now using the ROM image specific for the DDX-3.0 disk interface. It had the same results: if the emulated MSX is booted without any disk on the drive, no physical drives are detected by the Fast!DiskROM. I'm attaching this new extension to the bug. ---------------------------------------------------------------------- >Comment By: Wouter Vermaelen (m9710797) Date: 2012-12-24 04:17 Message: I figured out how to make the detection work, though unfortunately if I change the emulation code so that it works for this interface, it will break stuff for other interfaces ... In the DDX-3.0 the 'NOT READY' bit (bit 7 in the WD2793 status register) seems to be 0 -> when the drive is present and the drive motor is turned on 1 -> in all other cases But e.g. in a Philips NMS8280 there's an additional condition that there must also be a disk inserted in the drive (this is why if you insert disk(s) in the drive(s), the DDX-3.0 detection code does work). I'd first like to verify that my findings are correct. Do we have schematics of the DDX-3.0 interface? Or does someone who owns such an interface do tests on it? (I can do tests on a NMS8280). If these tests confirm what I found out above, then we should add extra configuration parameters in the WD2793 section in the hardwareconfig.xml file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=2946167&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-22 21:13:08
|
Bugs item #2776825, was opened at 2009-04-20 14:59 Message generated for change (Comment added) made by manuelbi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=2776825&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: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: FRS (sd-snatcher) Assigned to: Nobody/Anonymous (nobody) Summary: Dir-as-disk data corruption Initial Comment: The dir-as-disk feature seems to corrupt the data sometimes, when the directory contains more than 720KB of data. Steps to reproduce the problem: 1) Put both the MSX-DOS1 and MSX-DOS2 files (MSX-DOS?.SYS and COMMAND?.COM) 2) Add some files to the same dir, making it pass the 720KB limit 3) Boot a MSX Turbo-R. It will boot the MSX-DOS2 4) Modify some file 5) Shut down the MSX Turbo-R 6) Boot a Panasonic FS-A1WSX. It will boot the MSX-DOS1 7) The MSX-DOS1 is probably corrupted. It freezes after the "MSX-DOS version 1.0" message. ---------------------------------------------------------------------- >Comment By: Manuel Bilderbeek (manuelbi) Date: 2012-12-22 13:13 Message: Dir-As-Disk has been refactored now. Can you still reproduce this? ---------------------------------------------------------------------- Comment By: Patrick van Arkel (vampier) Date: 2009-08-11 22:01 Message: While working on GraCo I had random crashes on openMSX when working with Dir-As-Disk. Switching to a .DSK image worked. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=2776825&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-22 20:58:59
|
Bugs item #3598181, was opened at 2012-12-22 12:58 Message generated for change (Tracker Item Submitted) made by manuelbi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3598181&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: Graphics Group: None Status: Open Resolution: None Priority: 3 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Nobody/Anonymous (nobody) Summary: Certain hybrid mode in 99x8 (and not 911x) not implemented Initial Comment: See http://www.msx.org/forum/development/msx-development/new-hybrid-mode-found for all details. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3598181&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-22 20:55:55
|
Bugs item #3395702, was opened at 2011-08-21 08:03 Message generated for change (Comment added) made by manuelbi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3395702&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 >Resolution: Fixed Priority: 5 Private: No Submitted By: Manuel Bilderbeek (manuelbi) >Assigned to: Wouter Vermaelen (m9710797) Summary: Dir-as-dsk doesn't support subdirectories Initial Comment: Start up an MSXturboR with DOS2. Insert a dir in drive a: (e.g.: diska /tmp/bla). In MSX-DOS, create a subdir on that drive: mkdir test check on host PC: no subdir appears. On the MSX side, the subdir is visible. Copy files into the subdir. Again, nothing on the PC side, but on the MSX side all files are there. Copy files into the root. Those files do appear on the PC side. Conclusion: subdir support not implemented for dir-as-dsk? ---------------------------------------------------------------------- >Comment By: Manuel Bilderbeek (manuelbi) Date: 2012-12-22 12:55 Message: Implemented by Wouter in revision 12915, thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3395702&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-20 01:07:13
|
Bugs item #2552579, was opened at 2009-01-31 06:01 Message generated for change (Comment added) made by sd-snatcher You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=2552579&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: Graphics Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Nobody/Anonymous (nobody) Summary: Mirrored VDP mode doesn't work on Toshiba VDP's Initial Comment: <n_n> mirrored mode however is known not to work on toshiba vdp <n_n> to clarify <n_n> mirrored mode = screen2 with a mask on the pattern or color table address to make it use less than 3 separate tables <Quibus> mirrored mode doesn't have a test in ident.bas, right? <n_n> it does <n_n> it's the 'do you see this text 3 times?' test <Quibus> ah <Quibus> mirrorred mode works always, except on Toshiba MSX1 VDP's? <n_n> yes, it works on v9938/58 too So, also testable with ident.bas. openMSX doesn't emulate this difference at all. ---------------------------------------------------------------------- Comment By: FRS (sd-snatcher) Date: 2012-12-19 17:07 Message: Any news on this matter? Would it be to hard to emulate this VDP and its unique color palette? It would be nice to test some future patches, since it's very hard to come by a machine with this specific VDP. It would be good to attach the IDENT.BAS file here too. The only test I know is this one: screen2:vdp(3)=159:vdp(4)=0:line(33,33)-(99,55),15,bf:a$=input$(1) [ENTER] The Toshiba T6950 VDP will show only a single horizontal white band, while the other VDPs (even the v2 of the Toshiba VDP inside the T7937 chipset) will show three horizontal white bands. It's unsure which version of the Toshiba VDP is inside the T7775 chipset. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=2552579&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-19 20:32:38
|
Bugs item #3597547, was opened at 2012-12-19 12:32 Message generated for change (Tracker Item Submitted) made by sd-snatcher You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3597547&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: Graphics Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: FRS (sd-snatcher) Assigned to: Nobody/Anonymous (nobody) Summary: screenshot -raw is using gamma correction Initial Comment: The "screenshot -raw" should take a raw screenshot of the MSX image, without any scaling or effects. But currently the image has the gamma correction effect applied over it, resulting in modified colors. Tested on openMSX 0.9.1-dev12913 on Mac OS-X 10.6. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3597547&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-16 10:29:01
|
Bugs item #3596542, was opened at 2012-12-16 02:29 Message generated for change (Tracker Item Submitted) made by awulms You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3596542&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: Open Resolution: None Priority: 5 Private: No Submitted By: Alex Wulms (awulms) Assigned to: Alex Wulms (awulms) Summary: Android: openMSX crashes on Samsung i5800 Initial Comment: OpenMSX crashes on Samsung i5800. According to the debug output fro, 'adb logcat', it is in a libsdl function during the crash; See attachment for the adb logcat output ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3596542&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-15 17:19:30
|
Bugs item #3442678, was opened at 2011-11-26 04:02 Message generated for change (Comment added) made by manuelbi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3442678&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: Graphics Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Manuel Bilderbeek (manuelbi) >Assigned to: Edwin (edwinv) Summary: Tesel game shows white stripes on real GFX9000 Initial Comment: This software for GFX9000: https://github.com/out168/tesel shows white stripes on real hardware, but not in openMSX. See also http://www.msx.org/forumtopicl13789.html ---------------------------------------------------------------------- >Comment By: Manuel Bilderbeek (manuelbi) Date: 2012-12-15 09:19 Message: Edwin fixed the white stripe issue (VRAM init) in r13043. Thanks! There's one remaining issue: a half sprite is shown at the top. I'll make an new bug report for that. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3442678&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-15 17:19:27
|
Bugs item #3596299, was opened at 2012-12-15 09:19 Message generated for change (Tracker Item Submitted) made by manuelbi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3596299&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: Graphics Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Nobody/Anonymous (nobody) Summary: Tesel game shows half sprite on real GFX9000 Initial Comment: See 3442678: This software for GFX9000: https://github.com/out168/tesel half sprites at the top on real hardware, but not in openMSX: see http://www.msx.org/forumtopicl13789.html for a pic. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3596299&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-15 15:24:02
|
Bugs item #3596280, was opened at 2012-12-15 07:24 Message generated for change (Tracker Item Submitted) made by awulms You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3596280&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: Open Resolution: None Priority: 5 Private: No Submitted By: Alex Wulms (awulms) Assigned to: Alex Wulms (awulms) Summary: Android: issues with keyboard support in SDL Initial Comment: Example: Map virtual buttons as follows: -button 4 to F10 (console) - causing emulator to crash when pressed -button 5 to F7 (SELECT) - MSX does not see SELECT presses when in character mode -button 6 to F8 (STOP) - MSX does not see STOP presses when in character mode It works fine when in KEY mode (e.g. put <setting id="kbd_mapping_mode">KEY</setting> in settings.xml file in mnt/sdcard/openMSX/share folder) Investigation finding: openMSX receives on PC following SDL event when pressing F8: Key pressed, unicode: 0x0000, keyCode: 0x00121, keyName: F8 Key released, unicode: 0x0000, keyCode: 0x400121, keyName: F8,RELEASE But on Android it receives: I/Ballfield(19719): SDL key event: evt DOWN state PRESSED key 289 key name f8 scancode 33 mod 0 unicode 289 I/Ballfield(19719): SDL key event: evt UP state RELEASED key 289 key name f8 scancode 33 mod 0 unicode 289 Note that on Android, the messages come from a test app, not from openMSX. But the app interfaces the same with the SDL Keyboard driver. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3596280&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-15 14:41:41
|
Bugs item #3592046, was opened at 2012-12-03 01:55 Message generated for change (Comment added) made by awulms You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592046&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: Sound Group: None Status: Open Resolution: None Priority: 4 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Alex Wulms (awulms) Summary: Android: SDL audio buffer size Initial Comment: On all devices we tried so far, the SDL setting 'audio buffer size' had to be changed from "very small" to "small" to not get choppy sound. Can this be made default, so that people have good sound right away? ---------------------------------------------------------------------- >Comment By: Alex Wulms (awulms) Date: 2012-12-15 06:41 Message: Question asked on the SDL Android port support forum (http://www.anddev.org/code-snippets-for-android-f33/sdl-port-for-android-sdk-ndk-1-6-t9218-840.html#p2228174) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592046&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-15 14:28:07
|
Bugs item #3592048, was opened at 2012-12-03 01:57 Message generated for change (Comment added) made by awulms You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592048&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 Resolution: None Priority: 7 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Alex Wulms (awulms) Summary: Android: joystick control works badly Initial Comment: I had really a lot of trouble to browse through the lists in the menus with the touch screen joystick. It sometimes seemed to do a page up while I was browsing downwards. It's really quite hard to use. ---------------------------------------------------------------------- >Comment By: Alex Wulms (awulms) Date: 2012-12-15 06:28 Message: Increased dead zone for joystick from 25% to 40% in revision r13027 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592048&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-15 14:21:30
|
Bugs item #3592049, was opened at 2012-12-03 01:59 Message generated for change (Comment added) made by awulms You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592049&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 Resolution: None Priority: 5 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Alex Wulms (awulms) Summary: Android: default hard key key mapping Initial Comment: By default, the menu hard key didn't map and the back hard key mapped to MENU. It's better to not map the back-key and map the menu key to MENU. This does more what one would expect: open the menu or exit openMSX. ---------------------------------------------------------------------- >Comment By: Alex Wulms (awulms) Date: 2012-12-15 06:21 Message: Menu button fixed in r13031. Furthermore, made a small change in r13039, to bind the 'back' button to the openMSX exit command so so that preferences, sha1sum cache, etc get persisted when user quits openMSX by pressing the back button ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592049&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-15 14:15:05
|
Bugs item #3592053, was opened at 2012-12-03 02:03 Message generated for change (Comment added) made by awulms You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592053&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: Open Resolution: None Priority: 5 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Alex Wulms (awulms) Summary: Android: slow unlocking from screensaver Initial Comment: <Quibus> when openMSX is running and the 'screensaver' kicked in (so I have to unlock the device again), this unlocking goes very slowly. Is openMSX using CPU power or is it a memory issue? <awulms> it might be that openmsx keeps running on the background <awulms> I must investigate <Quibus> awulms: well, sound is stopped, at least ---------------------------------------------------------------------- >Comment By: Alex Wulms (awulms) Date: 2012-12-15 06:15 Message: Updated openMSX to go into 'blocked' mode when an SDL_ACTIVEVENT 'de-activete' is recieved and to return to 'running' mode when en SDL_ACTIVEVENT 'activate' is received. It has significantly improved the situation. However, openMSX is still using up to 12% CPU when in background, which is more then expected and a drain on the battery. Needs to be further investigated. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592053&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-15 14:09:50
|
Bugs item #3592052, was opened at 2012-12-03 02:02 Message generated for change (Comment added) made by awulms You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592052&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 Resolution: None Priority: 7 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Alex Wulms (awulms) Summary: Android: change user directory to an easier place Initial Comment: <Quibus> It might be good to change the default USER directory for the Anddroid port <Quibus> It's now .openMSX as you explained last night, but perhaps we can find a better place <awulms> yes good point <awulms> the .openMSX subdirectory is difficult to find <Quibus> We always recommend to install system ROMs and software in the USER directories, that's why I mention it <Quibus> These are usually not affected by installers etc. <awulms> and it gets deleted when you uninstall openMSX <Quibus> ah, right, then I really think we should look at an alternative :-) <Quibus> as my last argument would be moot then <awulms> I have noticed that most apps install data into /sdcard/... ---------------------------------------------------------------------- >Comment By: Alex Wulms (awulms) Date: 2012-12-15 06:09 Message: Code and documentation updated. It is in the beta release from Sat 8 Dec 2012 ---------------------------------------------------------------------- Comment By: Alex Wulms (awulms) Date: 2012-12-05 13:08 Message: Code updated to use <external storage directory>/openMSX as the USER directory on Android ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592052&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-05 21:08:03
|
Bugs item #3592052, was opened at 2012-12-03 02:02 Message generated for change (Comment added) made by awulms You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592052&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: Pending Resolution: None Priority: 7 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Alex Wulms (awulms) Summary: Android: change user directory to an easier place Initial Comment: <Quibus> It might be good to change the default USER directory for the Anddroid port <Quibus> It's now .openMSX as you explained last night, but perhaps we can find a better place <awulms> yes good point <awulms> the .openMSX subdirectory is difficult to find <Quibus> We always recommend to install system ROMs and software in the USER directories, that's why I mention it <Quibus> These are usually not affected by installers etc. <awulms> and it gets deleted when you uninstall openMSX <Quibus> ah, right, then I really think we should look at an alternative :-) <Quibus> as my last argument would be moot then <awulms> I have noticed that most apps install data into /sdcard/... ---------------------------------------------------------------------- >Comment By: Alex Wulms (awulms) Date: 2012-12-05 13:08 Message: Code updated to use <external storage directory>/openMSX as the USER directory on Android ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592052&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-03 21:28:26
|
Bugs item #3592258, was opened at 2012-12-03 13:28 Message generated for change (Tracker Item Submitted) made by manuelbi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592258&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: Open Resolution: None Priority: 5 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Nobody/Anonymous (nobody) Summary: Using GS2 with cursors is impossible Initial Comment: Using Graph Saurus 2 in screen 5 using the cursor keys is impossible. On a real MSX, when you tap a cursor key, the cursor moves 1 pixel. But in openMSX, it moves 2-3 pixels, making it impossible to dot a specific coordinate. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592258&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-03 10:03:51
|
Bugs item #3592053, was opened at 2012-12-03 02:03 Message generated for change (Tracker Item Submitted) made by manuelbi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592053&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: Open Resolution: None Priority: 5 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Alex Wulms (awulms) Summary: Android: slow unlocking from screensaver Initial Comment: <Quibus> when openMSX is running and the 'screensaver' kicked in (so I have to unlock the device again), this unlocking goes very slowly. Is openMSX using CPU power or is it a memory issue? <awulms> it might be that openmsx keeps running on the background <awulms> I must investigate <Quibus> awulms: well, sound is stopped, at least ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592053&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-03 10:02:34
|
Bugs item #3592052, was opened at 2012-12-03 02:02 Message generated for change (Tracker Item Submitted) made by manuelbi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592052&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: Open Resolution: None Priority: 7 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Alex Wulms (awulms) Summary: Android: change user directory to an easier place Initial Comment: <Quibus> It might be good to change the default USER directory for the Anddroid port <Quibus> It's now .openMSX as you explained last night, but perhaps we can find a better place <awulms> yes good point <awulms> the .openMSX subdirectory is difficult to find <Quibus> We always recommend to install system ROMs and software in the USER directories, that's why I mention it <Quibus> These are usually not affected by installers etc. <awulms> and it gets deleted when you uninstall openMSX <Quibus> ah, right, then I really think we should look at an alternative :-) <Quibus> as my last argument would be moot then <awulms> I have noticed that most apps install data into /sdcard/... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592052&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-03 10:00:18
|
Bugs item #3592051, was opened at 2012-12-03 02:00 Message generated for change (Tracker Item Submitted) made by manuelbi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592051&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: Open Resolution: None Priority: 3 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Alex Wulms (awulms) Summary: Android: performance not as expected Initial Comment: I saw that it doesn't get full framerate (although you hardly notice). That's a bit disappointing, as the Dingoo on 400MHz seems to get about the same or better framerate than my Gio at 800MHz. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592051&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-03 09:59:12
|
Bugs item #3592049, was opened at 2012-12-03 01:59 Message generated for change (Tracker Item Submitted) made by manuelbi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592049&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: Open Resolution: None Priority: 5 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Alex Wulms (awulms) Summary: Android: default hard key key mapping Initial Comment: By default, the menu hard key didn't map and the back hard key mapped to MENU. It's better to not map the back-key and map the menu key to MENU. This does more what one would expect: open the menu or exit openMSX. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592049&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-03 09:57:54
|
Bugs item #3592048, was opened at 2012-12-03 01:57 Message generated for change (Tracker Item Submitted) made by manuelbi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592048&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: Open Resolution: None Priority: 7 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Alex Wulms (awulms) Summary: Android: joystick control works badly Initial Comment: I had really a lot of trouble to browse through the lists in the menus with the touch screen joystick. It sometimes seemed to do a page up while I was browsing downwards. It's really quite hard to use. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592048&group_id=38274 |
|
From: SourceForge.net <no...@so...> - 2012-12-03 09:56:11
|
Bugs item #3592047, was opened at 2012-12-03 01:56 Message generated for change (Tracker Item Submitted) made by manuelbi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592047&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: Open Resolution: None Priority: 2 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Alex Wulms (awulms) Summary: Android: screen doesn't rotate Initial Comment: When I rotate my device, openMSX doesn't rotate with it, which is what I expected. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=3592047&group_id=38274 |
