This code crashes :

Code: [Select]

int main()
{
  char *filename;

  if(show_msg_user_input("A", "B", "C", &filename) != -1) free(filename);
  return 0;
}

It runs fine for me. Update your Ndless (on the handheld) to the latest.

And I can't find any libndls directory in /ndless/ ... (I use the Ndl3ss SDK)

Okay ... in the sources, so here is the sample code :
   const char * title = "Title";
   const char * msg = "Element";
   char * defaultvalue = "default value";
   char * value;
   unsigned len = show_msg_user_input(title, msg, defaultvalue, &value);
   if (len >= 0)
   {
      printf("%s (%d)\n", value, len);
      free(value);
   }
   else
      puts("Canceled");


EDIT : second question on the go : why does libndls's refresh_osscr() crashes ?

Same, I think your Ndless version on the handheld is not up to date.

Quote from: Levak on January 21, 2013, 10:19:18 am

Indeed, you don't know its size and putting arbitrary size (here 256) is a bad programming behavior.

I don't want to be a nitpicker, but I have to disagree. In a practical context, using "big enough" buffers when dealing with arbitrary-sized strings is in many cases better than hassling around with a bunch of pointers and dynamically allocated memory. Using the latter method complexifies and bloats the code unnecessarily, gives the programmer additional responsibility (gotta compute the size of the data, malloc it, remember to free the memory, etc.), decreases the programs maintainability (as the code for that filename container is scattered around, when modifying bigger chunks better check it doesn't cause any undefined behavior), and generally the whatever academic perfection of the code doesn't outweigh the pain of dealing with such trivial stuff. We're not talking about security-critical government-class programs here, and it's not like there aren't any functions to avoid buffer overflows and whatnot.
I'm not saying you should be using statically allocated data for everything (quite the contrary usually), but for string buffers and such, a char buf[BUF_SIZE]; is usually good enough.

I know, but this applies in a context you can't control the length of the string. Here, the popup does not limit the number of characters entered, and at first it was a 256 buffer. Some people complained because it crashes when you enter a 120 chars string, and indeed ... the popup does not limit it. Thus, without having to allocate a 1024 buffer, I prefer using the dynamic length String API the Nspire uses. I think this API is the only one that runs really nicely compared to a lot of things on Nspire development.
On the other hand, there is a place in the OS where it limits the string length to 256 because the buffer is 256 : The SaveAs popup. And this has sense, I agree.

I'm using nspire_emu_easy from Ti-Planet, it's a version with Ndl3ss already in it. Do you think it could be the wrong version ?

I've never heard of that before and I cannot find any archive having this name on TI-Planet.
But yeah, if Ndless is included in the archive, it is surely outdated. Ndless updates syscalls and developments tools in background a lot of times.

And there is a SaveAs popup ? O.o I didn't see it.

Yes and No. It is a syscall I did not added to Ndless for the moment as it is part of nFrame, still under development.
If you really want it, pick it up from ThemeEditor sources.

Is there an ndless sdk/editor for linux?

Do I need to get ndless 3.1, and should I?

Ndless 1.0 and 1.1 only work on the oldest OS 1.1 versions, and those are only for the Clickpad models. For a CX / CX CAS calculator, you need OS 3.1.0.392 and Ndless 3.1.

Do I just download os 3.1 from tiplanet and then follow the nspire 3.1 instructions?

Depends on the manufacturing date and hardware revision of your calculator. It's a group of 1 letter, 4 figures and 1 letter written on the back, at the right of the serial number.
If the last letter of that group is J or higher, you're in trouble: at the time of this writing, there's no way to do anything with those calculators. If it's H or lower, you can downgrade for OS 3.1 to work, either directly (if the calculator's boot2 is 3.10.16) or after reflashing the boot2 through a relatively cheap, widespread but extra equipment known as USB-RS232 TTL adapter.

Is there any particular order that I should install nlaunch and ndless in?

Yes, it's described in the instructions

Do I install nlaunch or nlaunchy?

nLaunchy is the newer, community-maintained version of nLaunch and nLaunch CX, which were made by unknown author(s).

Is there any way to find all user uploaded games for nspire cx ndless (and can I use games for the regular nspire ndless on the cx?)?

In the Omnimaga, ticalc.org and TI-Planet archives. There's also a site by compu, but I'm not sure how to date it is.