This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - ExtendeD
Pages: 1 ... 34 35 [36] 37 38 ... 55
526
« on: February 27, 2011, 02:22:52 pm »
I have updated the ReadMe file to make these things clearer.
527
« on: February 27, 2011, 03:38:05 am »
It looks like the '=' key is mapped incorrect...
You're right! It's now fixed. wait...so "no bug" means that it no longer haz installation bug/theta bug?
The theta bug had already been fixed in v1.7. The calculator may still hang during some installations, but it will always succeed the second time.
528
« on: February 25, 2011, 06:07:57 pm »
Great! I like it.
I suppose Ndless should both make available the current isKeyPressed() function to detect left/right/... and a new touchpad-specific scanning function. Touchpad-based games may be fun to play!
529
« on: February 25, 2011, 05:58:34 pm »
Thank you all for your suggestions.
It appears to be a significant amount of implementation work and maintenance just for a better experience with possible shells and file explorers, and unfortunately cannot be one of my current priorities. Hopefully this may change once the current major missing features of Ndless are implemented, or if other interesting use cases are identified.
530
« on: February 25, 2011, 05:51:34 pm »
In the meantime, I think that the number keys may actually be easier to use. But do you think it would be possible to move the down arrow to 5? If you're using one hand, the key in the middle makes it hard to use the keys as a joypad.
So:
....8...
.4.5.6.
8 = up
4 = left
5 = down
6 = right
and then maybe make click "2".
Have any apps other than block dude been compiled with this configuration? (i.e., gbc4nspire or nes)
I haven't touched a single line of code since then, but I'm keeping track of your bug reports and suggestions, hopefully I'll try to integrate them soon.
What have you decided about the arrow and number keys?
I think mapping arrow keys to number keys at the Ndless level (which has been introduced in the last builds if I've understood well) is a bad idea.
I can understand this "hack" has been introduced to make old Ndless 1.7 games work without modifying the source...
But let's look at the future and not at the past: there are many reasons a program would like to test for number keys (numerical input, menu choice...).
I think it's up to the program itself to test for number keys and to decide to handle them either as numbers either as arrows.
About this, I have an idea that might make everything work great: how about add a line in Ndless program headers so as to specify for which version they were compiled for. If this line is absent, consider it to be an Ndless 1.7 program, and make Ndless decide which buttons to use, but if the line says that the program was made for Ndless 2.0, let the program decide its own course of action in regard of the keys.
What do you think?
I have implemented codeslicer's suggestion for the v2.0 release. Block Dude and maybe nDoom need to be rebuilt to use the new mapping if apcalc and Mrakoplaz want to, sorry for the inconvenience. In any case programs written for Ndless 1.1 needs to be rebuilt with this version to be compatible with the Touchpad, and programs will have to be rebuilt once the full Touchpad support is added to Ndless, since the key mapping is actually inlined into the program's codes. With the current implementation the options are the following: - either the program keeps the current default mapping, and will be rebuilt (and perhaps slightly adapted) once the Touchpad arrows scanning is available in Ndless - either the program needs both arrow keys and numeric keys as input, and layout the keyboard as it wants, without using the KEY_NSPIRE_LEFT constants and the like. Are we all OK with this?
531
« on: February 25, 2011, 05:16:34 pm »
The install process is unchanged.
532
« on: February 25, 2011, 05:13:52 pm »
Thanks! Just commited to the trunk.
533
« on: February 25, 2011, 05:06:12 pm »
Just found a little bug: I notice that when Ndless tries to restore the FIQ vector (in arm/bootstrapper.S main_copy), it overwrites the Undefined Instruction jump instead:
A4000000 18 F0 9F E5 E4 66 26 10-18 F0 9F E5 18 F0 9F E5
A4000010 18 F0 9F E5 18 F0 9F E5-18 F0 9F E5 18 F0 9F E5
A4000020 30 60 26 10 28 48 04 11-4C 47 04 11 20 48 04 11
A4000030 18 48 04 11 00 00 00 00-C0 66 26 10 40 00 00 00
This one was well hidden! I've just fixed it. I wonder if this could be the source of the random crashes at installation time.
534
« on: February 25, 2011, 04:44:47 pm »
Thanks, Ndless's va_* definitions are now wrappers to GCC builtin functions.
535
« on: February 25, 2011, 04:32:00 pm »
I currently need more development workforce than testing. How about implementing the Touchpad keypad protocol from Goplat's spec? 
536
« on: February 25, 2011, 04:21:26 pm »
Beta binaries are now available to avoid wasting your time.
537
« on: February 25, 2011, 03:40:57 pm »
If you just need to wait for an arbitrary number of milliseconds, you can try the sleep() function. Else if you need asynchronous processing, you can have a look an the sleep function source code for the timer setup and Hackspire for the interrupts management.
538
« on: February 25, 2011, 01:56:41 pm »
Ndless 2.0 is the latest and greatest way to develop and run third-party software on the TI-Nspire. This version: - (update: 2011/06/11) has now moved to a stable state - is compatible with OS v1.7, v2.0.1, v2.1.0 - run on both Clickpad and Touchpad models Ndless v2.0 binaries are available in Omnimaga's download section. Issue tracker: http://www.unsads.com/projects/nsptools/report/1
539
« on: February 25, 2011, 01:06:20 pm »
I'm wondering how quickly support for OS 3.0 will be added.
540
« on: February 25, 2011, 07:43:46 am »
Excellent Goplat, as usual!
Does this mean that we now have enough information on the USB controller to implement on-calc drivers?
Pages: 1 ... 34 35 [36] 37 38 ... 55
|
Show Posts
