Okay, thanks
I just do these optimizations to lower system requirements
I will use inlining in essential screen update, and function calls anywhere else.
I have another problem. I use "write long" in my old DBPro made map editor to write four bytes integers to a map file, but I cannot read them as integers in AGK2 with "GetMemblockInt" (I load the whole file into memory first, just so that users running my app from a HDD have optimized read as HDD likes reading big chunks of data in one go). If I change this to bytes, I can read them in my AGK2 app, but I do need numbers much, much higher than a bytes 255 :-P Can you point me in any other direction? Like splitting up integers to bytes?
EDIT: I tried this:
make memblock 5,4
for x = 1 to work_map_info(1)
for y = 1 to work_map_info(2)
write memblock dword 5,0,work_map_events(x,y)
write byte 1,memblock byte(5,0)
write byte 1,memblock byte(5,1)
write byte 1,memblock byte(5,2)
write byte 1,memblock byte(5,3)
next y
next x
But I still get nothing when trying to read back in AGK2 :-( I tried reversing the byte order, no luck :-(
EDIT 2: I fixed it, somehow
I went back to writing the integer as a long in DBPro app, I read them back like this:
for m = 0 to 3
SetMemblockByte(5,m,GetMemblockByte(2,n))
inc n
next m
work_map_events[x,y] = GetMemblockInt(5,0)
instead of just:
work_map_events[x,y] = GetMemblockInt(2,n)
and that, somehow, fixed my long standing problem with long ints written to file from a DBPro app
13/0
