HI!

Could you try this script at your end?
The results that I get from this is
variable 351.0000
integer 0.3427

I tought that an integer was a whole number.
Code:

---

#include <acknex.h>
#include <default.c>
//
var _p = 0;
int iP = 0;

TEXT* Vname = 
{
	pos_x= 90;
	pos_y= 90;
	layer 8;
	STRING = "Variable";
	flags |= VISIBLE;
}
TEXT* intname = 
{
	pos_x= 90;
	pos_y= 120;
	layer 8;
	STRING = "Integer";
	flags |= VISIBLE;
}

PANEL* Check =
{
	pos_x = 200;
	pos_y = 90;
	layer 8;
	digits (0,0,5.5,*,1,_p);
	digits (0,30,5.5,*,1,iP);
	flags |= visible;
}
function test_var_int ()
{
	while (_p <= 350)
	{
		_p += 1;
		iP += 1;
		wait (1);
	}
}

function main()
{
	wait (1);
	// now load the level
	level_load("");
	wait (3);
	test_var_int ();	
}  

---

this has to be bug.. Int indeed means integer, an "whole number".

Here is the bug:

digits (0,30,5.5,*,1,iP );

Digits is var, not int.

Hi guys/girls!

1) If digits is a var and I want to show integers in a panel what do I use?

2) When I changed the INT for VAR to all my variables it made a big difference in my game.
The panels started to show the right values.
(btw : these panels are for debugging)
and my game is going further than it was.(still a few migration bugs).

VAR seems to be acting like an integer and INT seems to be acting like???

1.) you can write "(var)YourIntegerVariable" or assign the integer to a var variable like "MyVar = (var)MyInt;" and use the var variable in the panel.

2.) An int is an int surprisingly. And a var is from the data type fixed. Vars don't behave like integers. Never.

Hi !

Thanks for the (var) solution but....

I believe that this (var) is a workaround and a fact that INT as a problem.

In any program, if I write 1 = 1 ...I am expecting to get 1 = 1.

When we define a VAR we get 1 = 1
But
when we use INT we get 1 = 0.00098 and in order to correct this
I have to use myint = (var)1 to get 1 = 1
which means that (var) works but INT does not.

int works, just not all functions work with int. When a function expects a var and you pass an int, the raw binary data in the int will be interpreted as a var. Because a var stores values differently than an int, the same binary data will represent another value when interpreted as var.

To "translate" the value from int to var, you use typecasting. Typecasting is needed in every C compiler so it is not a lite-c bug. The typecasting syntax is (typeToCastTo)variable. Example:
myInt = (int)myFloat;

If a function takes a var, and you have an int you want to pass, you must typecast it:

var myFunction(var x){...}
myFunction((var)myInt);

Apparently, the panel expects a var so you must typecast your int to a var before giving it to the panel.

HI Excessus!

Thanks for the information.
I've copied it and will look at it.

I will also look for int transfers in function.

Hi!
To continue the saga....of typecasting... or another type of problem...

This line was working in Cscript ...the migration is very hard on it :

if (var_green == MyEntity.skill16) {}

var_green is defined as a VAR


but what is MyEntity.skill16 which holds a value of 1.00 to 10.00 in WED.

If it’s an INT how do I typecast it? (I’ve tried a few ways without success )

AFAIK, skills are var, so no need to typecast. Are you getting compilation errors, crashes or strange behaviour without typecasting?