sypherce / ds2key Goto Github PK

Setting GUI log to "All Messages" causes lag. 

A profile toggle function needs to be implemented that you can bind to a
button. A hold function should be implemented similar to holding "Ctrl + A"
does something different than pressing just "A".

The software doesn't support DSi mode via Sudokuhax Please compile latees 
relase with the updated libs

Please allow an option to make any of the buttons go turbo while being held
down.

Arrow key settings actually send numpad arrow keys, or numbers, depending
on numlocks status

What steps will reproduce the problem?
1. Checkout r67 by "svn checkout 
http://ds2key.googlecode.com/svn/branches/cpp_rewrite/ ds2key-read-only" (use 
"-r 67" if needed)
2. Run "make" in "/client"
3. Run the created "DS2Key.nds" on a Nintendo DS

What is the expected output? What do you see instead?
Expected output (taken from r52):

DS2Key SVN Build
-
<ini parser output here>
Connecting via WFC

After connecting, the bottom screen shows up. This is usually a few seconds 
after running the .nds as the DS has to connect.

Actual output (taken from r67):

DS2Key SVN Build
-
Connecting via WFC
<ini parser output here, I have errors as I don't have a ds2key.ini>
Error (socket): #12
<infinite loop of> Error (UDP::Send): Not connected

Instantly after running the .nds, the bottom screen shows up. The DS light 
indicator shows that it has not connected.

What version of the product are you using? On what operating system?
Compiled both r52 and r67 on Windows 8.1 using the latest devkitARM, r52 works 
fine, r67 has errors.

Please provide any additional information below.
I'm looking through the code, comparing the two (I'm not familiar with C++), 
and I can't seem to figure out why this is happening. I'll try the other 
revisions and see which ones don't work.

What steps will reproduce the problem?
Lag Problems, not with the output but the application itself.
1. Using an Emulator or application that takes average CPU %
2. Changing the process priority can cause worst responding
3. You don't have to use an application that takes too much system CPU Usage.

What is the expected output? What do you see instead?
I expect an immediate response from the buttons with relatively no lag.
I see Immediate Response when i use little applications like Gens or other
emulators. Project64 has no lag, same for Gens and VisualBoy Advance.
Zsnes has some lag specially when you press too much buttons rapidly (this
also happens on Gens).

What version of the product are you using? On what operating system?
DS2KEY v1.10 on Windows XP SP3. Athlon64 3200 [email protected] OCED Processor

Please provide any additional information below.

When i underclocked the CPU to the STOCK speed (2.0Ghz) the button LAG
REALLY INCREASED SIGNIFICANTLY, hope a computer with DUAL CORE CPU will do
much better.

Overall, this App is Awesome and works Very Well if you've an average good
computer. 
I also would like to help on anything i can do as a Tester or whatever.
Thanks to Derrick (Sypherce) for making this possible. You can count on me.

Sonic Dreamcaster

The option to connect to an access point other than one configured in 
Nintendo's WFC needs implemented.

I'm having a lot of trouble getting this project to build in Ubuntu 9.04. 

Judging from some of the things I've seen, I'd be surprised if it even
builds in Windows.

I'm wanting to add a full keyboard emulation mode where you use the
keyboard on the touch screen to send keys. Also a media controller mode
with support for play, pause, previous, next and a current song listing.
Possibly playlist support in the future

What steps will reproduce the problem?
1. open a profile and delete everything
2. select that profile in the server

What version of the product are you using? On what operating system?
Windows Vista and XP, 1.1

Please provide any additional information below.

ds2key consumes 44%-48% of cpu; doesn't work as it would on Windows.

DS2Key SVN Rev 39

OS:Ubuntu 8.10

In some earlier releases of DS2Key (and possibly the current release) under
certain configurations changing the IP on the DS ends up making the server
repeatedly send "/p?".

The server should send "/p?" once and then be connected.

I mapped the buttons to support Sonic Adventure DX, which is in a different 
fullscreen resoultion. When I exit SADX, the resolution becomes native again. I 
then try to remap the buttons on DS2Key Server after playing, and DS2Key's 
button management window DOES show up, but it won't respond afterward, and two 
DS2Key icons are shown on the taskbar.

Using Windows XP

What steps will reproduce the problem?

1. Start DS2Key r52
2. After it connects to your network, tap "TOUCH"
3. Make a quick (horizontal/vertical/diagonal) movement with your stylus

What is the expected output? What do you see instead?

Expected output: Move to the area where the stylus is being moved normally

Instead, it freezes and stops moving until I lift the stylus then press and 
move it again

What version of the product are you using? On what operating system?

I'm using the DS2Key r52 client on a Nintendo DSi over a WEP network, with the 
server on a Windows 7 computer.

Please provide any additional information below.

This bug happens for both "relative" and "absolute" touchpad movement and it 
doesn't happen in DS2Key 1.01

Play for X amount of time and you eventually lose a button press or button
release. This is most likely a problem by the nature of UDP and the
protocol used with DS2Key from day one.

When closing a DS running DS2Key and being connected to a PC does not
change anything. This means that even though the DS is closed actions
mapped under the shoulder buttons will still be triggered. The DS however
knows that it was closed once you open it again, which is proven as the
screen will no longer be turned off right after opening.

May I suggest you look into blocking the usage of the shoulder buttons when
the DS is closed? Or maybe even disconnect from the network to spare the
battery.

Some key's such as "BackSlash" are unavailable in Linux. Possibly some in 
Windows as well.

A setting needs to be implemented that makes the touch screen function
similar to a laptop mouse pad, while still having the ability to switch
back t the original mouse function presented in other versions of DS2Key.