Using LiteC Free. I have noticed that some of functions aren't painted red even when the engine can compile it. Also Command Help wont show what it does or what arguments it needs. Some of functions/values I have noticed:

vec_rotate
font (in TEXT* definition)
NULL
on_space
PH_RIGID,PH_SPHERE
ENABLE_FRICTION
GLIDE
IGNORE_WORLD
(probably all the modes in c_move...)

Thats what I have tested and seen. Is it a normal thing or really mistakes, because I don't know to use builtin functions if not coloured so... (thus not showing up in Command Help)

Thanks for the info. A function is painted red in the editor when it is in the blue box with the black border in the manual. Thus, NULL, on_space etc. won't be painted red. But vec_rotate and font should, so that's an issue with the format of their manual pages. Whenever you find some function that should be red but isn't, please post it here or in the manual forum.

a few more

FUNCTIONS
---------
asin
pan_setdigits
pan_setbutton
pan_setneedle
pan_setwindow
str_width
vec_rotateback
vec_rotateaxis
vec_for_ent
ent_for_file

EVENTS
------
on_exit

TYPES
-----
byte

PROPERTIES / PARAMETERS
-----------------------
genius
min_x ..to.. max_z
mtlSkin1
flags2 - (not manual header)

VARIABLES
---------
shift_sense

would also be useful if #defined items would be painted too

sign
emask

Other things noticed:

1. When I make text active and right click on it without moving the mouse! the activness disappears and I cant do actions with it. But when I make it active, move mouse! and right click, everything is fine.

2. When I write a function/value etc sometimes SED displays this little description. Its exactly one line down and even when I click on it nothing happens, I can't click on that lower row position (in order to edit something on that position) where that description is shown
It's quite annoying. I need to get rid of that description line first and then I can click on position where it stood in my way earlier.

3. Syntax check doesn't work at all... pressing F6 doesn't do anything and cant see any errors in Syntax Checker Results tab.

4. SED Auto indent makes funny things:
When I press Enter to a new line it sets the text cursor correctly to the indent position, but when I write } It jumps in the beginning of the line and I get: }@@@@@@

//would also be useful if #defined items would be painted too

as well as pre-defined functions

PH_RIGID

4. I typed
phent_settype(eBall,

and looked from Command Help in "var type" for values. Copied PH_RIGID from there and when trying to paste it into SED I suddenly got:

phent_settype(eBall,
phent_settype(eBall,

which is wierd.

atan2
width
height
angle

pi isn't recognised, error: 'pi' undeclared identifier :S

hi! how do you move one entity to a target position using c_move. I cant seem to get the right relative values. Im having a hard time finding a calculation using the target vector and current vector to apply in c_move. Please Help

hi! how do you move one entity to a target position using c_move. I cant seem to get the right relative values. Im having a hard time finding a calculation using the target vector and current vector to apply in c_move. Please Help

WIIMOTE

wiimote_smoothfac

video_alpha