http://www.xblite.com/forum/ http://www.eblah.com en http://www.xblite.com/forum/m-1319620833/ http://www.xblite.com/forum/m-1319620833/#num1
A second question - if I dim an array that uses more than 500MB it compiles but crashes on execution. Seems to be a limit to program size rather than a limit on a single array. Is there a way around this limit? I need an array of 1 or 2 GB.

Thanks for any help.
]]> Wed, 26 Oct 2011 04:20:33 xor0 http://www.xblite.com/forum/m-1311078509/ http://www.xblite.com/forum/m-1311078509/#num1
Iam new in xblie, i have problem when Compiling it always give the message "type mismatch at (50)". The problem is in the last line.

Here is the code

' #####  PROLOG  #####
' ####################
'
PROGRAM     "buffertest"
VERSION     "0.0001"
CONSOLE
'
     IMPORT     "xst"   ' Standard library : required by most programs
     IMPORT     "kernel32"
     IMPORT     "xio"
'

DECLARE FUNCTION  Entry ()
'
'
' ######################
' #####  Entry ()  #####
' ######################
'
FUNCTION  Entry ()

     SMALL_RECT srctReadRect,srctWriteRect
  CHAR_INFO chiBuffer[160]  
  COORD coordBufSize,coordBufCoord

     hStdout = GetStdHandle(STD_OUTPUT_HANDLE)
     hNewScreenBuffer = CreateConsoleScreenBuffer($$GENERIC_READ|$$GENERIC_WRITE,$$FILE_SHARE_READ|$$FILE_SHARE_WRITE,NULL,$$CONSOLE_TEXTMODE_BUFFER,NULL)                          
     SetConsoleActiveScreenBuffer(hNewScreenBuffer)
     srctReadRect.Top = 0
     srctReadRect.Left = 0
     srctReadRect.Bottom = 1
     srctReadRect.Right = 79
     coordBufSize.x = 2
     coordBufSize.x = 80
     coordBufCoord.x = 0
     coordBufCoord.y = 0
     ReadConsoleOutputA(hStdout,chiBuffer,coordBufSize,coordBufCoord,&srctReadRect)


END FUNCTION
END PROGRAM

Can someone help me ?

Regards

patrick]]> Tue, 19 Jul 2011 07:28:29 stapper http://www.xblite.com/forum/m-1309411846/ http://www.xblite.com/forum/m-1309411846/#num1
Let me know if there are any problems with how the forum operates.

thanks,

D.]]> Thu, 30 Jun 2011 00:30:46 XBLiteAdmin http://www.xblite.com/forum/m-1300910400/ http://www.xblite.com/forum/m-1300910400/#num1
You can see the difference in the two versions with the attached small graphics.

What tweek in the WinX version is partially hiding these button?  It doesn't look nice, or standard.

What might I do to make the WinX version of myprogram look more like the standard Windows API?

Thanks.

Al Taylor.]]> Wed, 23 Mar 2011 15:00:00 engineeral http://www.xblite.com/forum/m-1299093072/ http://www.xblite.com/forum/m-1299093072/#num1
I tried that and when I compile using XBLite I get two different error message.  One occurs only once - it says that in
     program$ = PROGRAM$(0)
     XstSetProgramName (@program$)
the XstSetProgramName is undeclared.  I cannot find documentation on XstSetProgramName.  I would assume it is in the xst standard library, which is INCLUDEd in my code.  There is a file xst.dec but no file xst.lib or xst.dll

The other error occurs for every instance of a line like:
XuiSendMessage ( g, #SetColor, $$BrightGrey, $$Black, $$Grey, $$White, 0, 0)
xui is INCLUDEd in the source code.  There is a file xui.dec but no xui.lib or xui.dll

The error message says #SetColor is undefined.  Yet elsewhere in the code from Vixen is a line:
     XgrRegisterMessage (@"SetColor", @#SetColor)

There is an xgr.dec file in the c:/xblite/include directory, but there is no xgr.lib file in c:/xblite/lib.
There are many other XuiSendMessage calls without error, just the SetColor ones have an error.
There are many XgrRegisterMessage calls - none give an error - for SetColor or for other parameters.

Argh!  I suppose I am missing something, probably something real basic (hah!)
Thank you for any help you can give me.
Al Taylor.
]]> Wed, 2 Mar 2011 13:11:12 engineeral