Jump to content




[OrangeOS] Weird function bug


  • You cannot reply to this topic
2 replies to this topic

#1 Ziriee

  • Members
  • 47 posts

Posted 23 August 2014 - 01:31 PM

So, I am having a weird bug, where I got window:57: expected number, then I removed a 'local' from 1 variable in the bar api and then I started to have even a weirder bug.
Spoiler
You can get the whole OS here:
pastebin run cYQF9usm


#2 Bomb Bloke

    Hobbyist Coder

  • Moderators
  • 7,099 posts
  • LocationTasmania (AU)

Posted 23 August 2014 - 02:52 PM

Is this an OS you're building yourself, or one you've found from somewhere? If it was initially written by someone else, it may not be compatible with your version of ComputerCraft.

I can tell you that the "window" API is mostly called by the "term" API. If "window" is erroring, it's likely because you called a term function incorrectly.

I can also tell you that the "rough description" in that screenshot is wrong - an attempt to index nil doesn't mean that "part of a table doesn't exist" so much as it means "the object you're trying to treat as a table in the first place doesn't exist".

#3 Ziriee

  • Members
  • 47 posts

Posted 23 August 2014 - 03:18 PM

View PostBomb Bloke, on 23 August 2014 - 02:52 PM, said:

Is this an OS you're building yourself, or one you've found from somewhere? If it was initially written by someone else, it may not be compatible with your version of ComputerCraft.

I can tell you that the "window" API is mostly called by the "term" API. If "window" is erroring, it's likely because you called a term function incorrectly.

I can also tell you that the "rough description" in that screenshot is wrong - an attempt to index nil doesn't mean that "part of a table doesn't exist" so much as it means "the object you're trying to treat as a table in the first place doesn't exist".

I am building the OS by myself, also even after using
os.loadAPI("data/api/bar")
This happens:
Spoiler

View PostZiriee, on 23 August 2014 - 03:14 PM, said:

View PostBomb Bloke, on 23 August 2014 - 02:52 PM, said:

-snip
-snip-
I found the problem, it was in the bar api itself





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users