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 - CinusMinus
2
« on: November 25, 2014, 04:47:31 pm »
I've improved the User Interface quite a bit, now it's a lot more intuitive and uses Buttons. There are no hotkeys anymore though. It comes along with an example file, to give you an idea of how the program formats a turing machine. Images:  
3
« on: November 18, 2014, 06:48:07 pm »
Well, i made a small Turing machine for the nspire, complete with an editor for the transition functions. It features:
- editor (WIP)
- saving, loading, importing and exporting transition functions in the editor
- visualization of the Turing machine
Controls:
- editor:
- switch active element: [ tab]
- insert transition function: [ i]
- remove transition function [ r]
- edit transition function [ Enter]
The two upper Textboxes are for the input and the initial state
- Turing machine:
- calculation step: [ i]
- reset: [ r]
- run: [ g]
The user interface isn't final yet, so the controls will probably change.
4
« on: November 13, 2014, 12:38:19 pm »
Too sad Theme Editor doesn't work on OS3.6 
5
« on: November 09, 2014, 12:21:15 pm »
N steht für eine beliebige natürliche Zahl. Du kannst einfach 0 dafür einsetzen, dann sollte ein brauchbares Ergebnis rauskommen.
6
« on: November 05, 2014, 09:42:50 am »
Most of them are either TI-Basic or Lua. If you are not sure, whether it works, just download them and run them. If it doesn't work they might be for ndless. But most of them should work with OS 3.9. You could also check whether they can be run in the student software, which doesn't support ndless.
7
« on: November 04, 2014, 12:49:29 pm »
I'm running OS 3.6 on kArmTI and it works fine. I suppose that OS 3.9 would also work, but I've not tested it.
8
« on: November 02, 2014, 08:43:54 am »
To enable more c++ stuff like #include <vector> I updated my yagarto toolchain using the installer provided here. The includes don't cause any errors anymore, but I can't run the compiled programs anymore. It's likely to be caused by this: c:/programmieren/ti_ndless_sdk/yagarto/bin/../lib/gcc/arm-none-eabi/4.7.2/../../../../arm-none-eabi/bin/ld.exe: warning: cannot find entry symbol lf2flt; defaulting to 00000000 How can I fix this? I've already consulted google, but I couldn't find any helpful answers.
9
« on: November 02, 2014, 07:10:02 am »
You forget, that it's quite easy to check whether you are in exam mode or not.
And you can deactivate all restrictions (except for the documents) when entering exam mode. And connecting to another calc to leave exam mode isn't that hard. And I'm quite sure, that you can't move your ndless folder.
10
« on: November 01, 2014, 10:59:49 am »
You could turn on exam mode by turning the calculator off and pressing [Esc] + [On]. The ndless folder won't show up and you can't access your normal documents. After your exams you can connect it to another handheld to leave exam mode and your files will be accessible again. That way you don't have to delete your documents in order to have the document list cleared.
11
« on: October 24, 2014, 04:08:56 pm »
For all those who can't access the student software for whatever reason: The source code.
If there is an other way to open documents you could do a memory dump and search for lua code. I've used that to recover unsaved code from the student software after it had crashed. You can even access protected code that way. But it could also work with other software that can open nspire documents.
edit: I've just tested that method with nspire_emu and ndless_installer.tns and it worked. So you can retrieve the source files from scripts even when you don't have the student software. Just do the memory dump and search for some lua pattern. There is some other stuff, probably from the OS, but the lua source code of the current document can also be found.
12
« on: October 22, 2014, 05:52:59 pm »
My main intention was not to prevent cheating. And yes, when the user updates the new file doesn't contain the variable anymore. But there are at least three ways of updating without data loss:
1: Use the script editor and copy-paste the new lua code into the old program. 2:Copy the page of the new version to the file of the old version. 3: Overwrite the var in the new file with the old state, close the file and reopen it. As I said my main intention was to provide a way to keep your old highscores and your unlocked cars and tracks. If you really want to cheat you can always do it. It's easier when the savestate is accessible but that's acceptable. The problem is that any kind of data saved via on.save will be bound its script. The only other way would probably be to let the user insert the old state directly in the script. That wouldn't be much more safe though. Obfuscation will prevent most attempts to cheating, but other methods won't ban cheating completely, too.
13
« on: October 22, 2014, 01:31:48 pm »
I know about on.save and on.restore. but data saved in these methods doesn't survive an update. That's not that tragic, when you don't update at all or your game doesn't depend on previous sessions. but if you unlock something and then there is an update with a lot of new features, or even a small bugfix update all your data is lost. That's what I tried to avoid by storing the data into a variable. It's still not easy to cheat, because the text in the variable in unreadable. And as I want to maintain the possibility of updating without users losing their progress I implemented it that way.
14
« on: October 22, 2014, 12:45:32 pm »
That's quite similar to what I do here. I don't use sprites for the background though. On of the most costly operations is to recalculate the positions of the vertices every frame. That's necessary though a blind mode would probably be quite funny  But by disabling the soil it gains some performance. The abstract mode just avoids filling shapes, which makes it faster, too.
15
« on: October 22, 2014, 11:57:55 am »
It would, if there was a physics engine in 3.1. Unfortunately it isn't available on 3.1 and it's essential for running the game. So basically there earliest supported version is OS3.2, because of the physics engine. It would be possible to include the physics engine via ndless, but that would be a lot of work only to add a feature, that's already available on newer versions that also support ndless. I'm sorry, but it won't work on OS 3.1
|
Show Posts