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 - Levak
Pages: 1 ... 8 9 [10] 11 12 ... 68
136
« on: June 23, 2013, 07:55:58 am »
Well yeah, it's badly said, I meant judging what I'm doing. I don't like how you say :
In short, I don't really like the word "library" to describe bunch of code you reuse from one project to another.
This is most likely called "toolkit". A library is attended to be distribued and used by others and as far as I can see you're not willing to release it as a standalone library.
Without knowing that I only use a sole function of a whole engine that is already released.
This confirm what I was saying : you're calling "lib" the use (=copy/paste here) of a "sole function" from one project (nRayC) to another. Since you did not corrected the other points of my previous post, I take them as true statement. And the reason why I'm not using nSDL (and not "boycotting", it's a great lib) is that I really like to know exactly what I'm doing, not only to make things work like I want them to, but also to understand concepts.
For sure it is nice to understand on what your walking, but I'm not sure it is usefull to do it on every project you do, most likely wasting time.
137
« on: June 23, 2013, 07:27:23 am »
What Hayleia said. How can you judge me
Judging you ? Where is it question of judging people here ? when you know nothing about what I wrote ? I know about C programming on the TI-Nspire and the about the plasma demo, about your past projects and abut what you said in your post. According to that I was able to determine the following without being able to look at the code : It's exactly the contrary. I only use nRayC's setPixel function.
It is exactly what I'm trying to tell you, if you only use such a function, things are telling me you copy/pasted it in your code thus your not using a library but a tookit. There is a big difference between the two (copy/pasting vs compile time linking). If you feel offended by my remarks where I'm trying to teach you good programming practice then I'm sorry and I promise not to help you in the future. If, on the contrary, your using the proper to use a non-released-yet standalone library without copy/pasting your code from one project to another (since you're saying in a lot of projects that you're not using nSDL "because blablabla"), fine, but then please be more clear in the future, for example on how you managed to code a crossplatform setPixel that is not the Ndless nor the nSDL one ... (this caught my attention and was affraid you where boycotting nSDL for no reason).
138
« on: June 22, 2013, 09:07:52 pm »
he's obviously another portuguese...
Oh, so if I'm not wrong, he is trying to cheat using CAS on a non CAS Nspire and wants help in order to do so ?
139
« on: June 22, 2013, 09:00:49 pm »
for this I reused part of a library I'm writing to deal with screen and pixels
Like ... nSDL ? My library handles cross-compatibility, so you can use the same *.tns file for both CX and non-CX calcs 
Like ... nSDL ? In short, I don't really like the word "library" to describe bunch of code you reuse from one project to another. This is most likely called "toolkit". A library is attended to be distribued and used by others and as far as I can see you're not willing to release it as a standalone library. It takes ≈ 6 seconds to start because it has to compute and store 76800 * 7 sines and 76800 * 2 square roots in a table in order to get a decent execution speed 
I haven't looked at the code, but this is too long for such calculation, do you know about fast sine and fast cosine ? Do you know also that using C++ templates you can precompile such values ? (you can also directly put the tables in the source code) Only sine from 0 to 45° are usefull, not the entire 360°. Then you can also define cosine from sine.
140
« on: June 22, 2013, 08:53:25 pm »
I guess he only wants 3.2.3 CAS and 3.1 CAS on a CX non CAS. (so not the 3.2.4 that reflashes the boot2)
This is pretty easy to do, just follow the Ndless switch pack and use CAS OSes instead of non CAS.
141
« on: June 17, 2013, 09:19:59 am »
Hello ladies and gentle men,
I'm imath(nickname).I'm new here,although I have signed up for Omnimaga before long.
I think I can communicate with others here.It's a good place for us to talk about calculators such as Nspire,CASIO,HP and so on.
I think we can have a bright future here.
imath
That is a good looking Python-scoped presentation. Is that a turing complete presentation though ?
142
« on: June 14, 2013, 01:01:28 pm »
Evil but powerful, nah.
143
« on: June 14, 2013, 08:45:37 am »
I'm not sure to understand your reaction....
What else did you expect from TI ?
To grow up and have seperate builds for Exams only and builds for Users only.
144
« on: June 10, 2013, 08:22:56 am »
3) Without any saves the .tns is 29KB. Every save takes about 1-2KB. Btw every world is 200x100 Blocks large (but the code supports larger).
Nice work !
145
« on: June 09, 2013, 02:47:35 pm »
You select the item to craft via the built-in menu, but for some reasons the menu won't open on OS 3.1... I'll have to do some research to solve this...
I don't remember any changes in the toolpalette API from 3.1 to 3.2
146
« on: June 09, 2013, 02:37:55 pm »
I know what it means, I'm just curious what he is using. If it's the physics engine then yes (which I'm guessing because of the falling sand), it may pose a bit of a problem otherwise it may be very simple to change.
Uh ? You don't need the 3.2 physic engine in order to create great physic. I'd say it is only for one that doesn't know how to code one, because oncalc, the Physic engine is really slow.
147
« on: June 09, 2013, 02:21:56 pm »
- Full compatibility to OS 3.1
What's the problem at this time?
This means he doesn't use 3.2 Lua features. On the other hand, I'm wondering how much it weight.
148
« on: June 09, 2013, 10:17:06 am »
It is possible that an actual Linux one is hidden somewhere on TI-Planet, but I'm unsure.
Just replace "TI-Nspire Computer Software" by TiLP and that's all.
149
« on: June 08, 2013, 07:10:30 am »
Jacobly helped me on IRC so I was able to get rid of the crash,
Which was ?
150
« on: June 07, 2013, 06:30:16 pm »
Your code is not really readable since it is math based and with a poor coding style (for example, more than 80 columns, trailling white spaces, more than 4 arguments per functions, passing structures as copy instead of pointers, etc ...) Two things had retained my attention, maybe they are not revelant, but I did not had more than 5 minutes for your code : - Do goto and labels work with Ndless ? I mean, test them appart and tell us. (other than that, using goto in C is a _really_ bad practice to solve algorithmic problems)
int nRC_Cos(int angle)
{
// Beware ! All trigonometry is done in base 256 !
int table[256]={128,128,128,128,127,127,127,126,126,125,124,123,122,122,121,119,118,117,116,114,113,111,110,108,106,105,103,101,99,97,95,93,91,248,86,84,81,79,76,74,71,68,66,63,60,58,55,52,49,46,43,40,37,34,31,28,25,22,19\
,16,13,9,6,3,0,-3,-6,-9,-13,-16,-19,-22,-25,-28,-31,-34,-37,-40,-43,-46,-49,-52,-55,-58,-60,-63,-66,-68,-71,-74,-76,-79,-81,-84,-86,-248,-91,-93,-95,-97,-99,-101,-103,-105,-106,-108,-110,-111,-113,-114,-116,-117,-118,-119,-12\
1,-122,-122,-123,-124,-125,-126,-126,-127,-127,-127,-128,-128,-128,-128,-128,-128,-128,-127,-127,-127,-126,-126,-125,-124,-123,-122,-122,-121,-119,-118,-117,-116,-114,-113,-111,-110,-108,-106,-105,-103,-101,-99,-97,-95,-93,-9\
1,-248,-86,-84,-81,-79,-76,-74,-71,-68,-66,-63,-60,-58,-55,-52,-49,-46,-43,-40,-37,-34,-31,-28,-25,-22,-19,-16,-13,-9,-6,-3,0,3,6,9,13,16,19,22,25,28,31,34,37,40,43,46,49,52,55,58,60,63,66,68,71,74,76,79,81,84,86,248,91,93,95\
,97,99,101,103,105,106,108,110,111,113,114,116,117,118,119,121,122,122,123,124,125,126,126,127,127,127,128,128,128};
return table[angle & 0xff];
}
Are you kidding me ? Didn't you meant "static int table..." instead ?
inline void nRC_dispBuf(char *buffer)
{
memcpy(SCREEN_BASE_ADDRESS, buffer, SCREEN_BYTES_SIZE);
}
IIRC, there is way more efficient than copying the entire buffer back to the screen, you can swap it, go take a look on hackspire Possibles issues I was looking for in your code that might crash the calc are : - Overflow on the RAM (either malloc or the stack), either infinite recursives functions or too big data allocation (a screenbuff is OK with malloc, but not on the stack)
- Calling syscalls that are not implemented (-nostdlib required) or your version of Ndless is not up to date
- weird stuff on the stack, typically an overflow, but a common bug in Ndless history is global variables
- Bad pointer, like drawing outside the screen
Pages: 1 ... 8 9 [10] 11 12 ... 68
|
Show Posts