 Search Results - Recent posts as of less than a minute ago |
|
Showing 1 - 30 (210 results found)
|
|
|
I'm using Winx, very nice, but I need to be able to edit variables while the program is running. I have looked through the demos and at the Winx library VERSION "0.6.0.12" but don't see a function that pops up a dialog box or dropdown menu where the user can edit variables (enter new values etc). Anyone point me to the right function?
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.
|
|
|
Hi Al,
When you select the Xui GUI (XBasic's cross-platform GUI),
viXen generates code only to complie with XBasic, not XBLite.
Bye! Guy
PS. XBLite's purpose is to use the native Windows GUI instead of Xui, at the expense of the portability.
viXen allows you to prototype for XBLite if you want performance or XBasic if you want portability. |
|
|
WinX: The GUI library for XBlite, finely crafted by Callum Lowcay.
Unless you're addicted to the Windows API, you'll like this programming gem that wraps most of the useful APIs with a convenient interface.
viXen generates a GUI skeleton in WinX as good as the native API skeleton. Saying that viXen version 2 will use WinX, I rest my case... |
|
|
Hi,
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 |
|
|
I had to change my ISP for xblite, so I also had to manually move the xblite forum to the new server.
Let me know if there are any problems with how the forum operates.
thanks,
D. |
|
|
XblCockpit: an application launcher, entirely written in XBLite.
I use this app all the time. Since I start it at boot time, it's the first application I use. I can reopen the latest project I worked on and I find it convenient to take off where I left earlier. Works nicely for me as I taylored it to my taste.
I coded a group editor and a launch pad editor for added comfort. |
|
|
I started to use XbGrid and I finalized the port from C to XBLite.
It can be found in directory .\xblite\demo\custctls\xbgrid and I find it better suited for data entry than the listview control. |
|
|
| I am not able to find IconService in demo\console\iconservice folder.Please guide me. |
|
|
Hey I am new to this forum I just want to know that which services used in XBlite. Please tell in detail.  |
|
|
I don't know of any project in xBlite like Icon Editor. Maybe another Xbliter knows?
Bye! Guy
|
|
|
| Hi, i think this question is related with OS, till now I haven't face such kind of problem , Surly i will tell you the solution asap. |
|
|
A template manager for XSed
Attached is xxxman_1_02.7z, which contains:
1. xxxman_setup_v1_02.exe: the install
2. xxxman_gen.vxn: the viXen project, rename to prevent an overwrite of xxxman.x
3. xxxman.x and the associated files: xxxman.ico, xxxman.rc, ...
I enhanced WinX.x to allow this project to work, so you have to download the last version from
http://code.google.com/p/xbl-winx/
I welcome any comment that would help me to improve, so please try xxxman and don't hold your comments.
Bye Guy |
|
|
trace: a KISS trace utility that logs the execution of functions in an XBLite program.
I wrote trace to help me in viXen's development and it saved me hours of painstaking debug PRINTs. |
|
|
| SortSource: sorts the functions of an XBLite program source |
|
|
Hi Al,
I investigated the bug you reported. For some reason, I did not figure out immediately what the problem was. I corrected viXen and you can download the corrected version at SourceForge. Thanks for your bug report; like they say: "A bug report means a use report". (Actually, I heard rather "No bug, no use!", but same difference!)
Happy vixening!
Bye! Guy |
|
|
Everything is cool.
But i have question.
is there any project in xBlite like Icon Editor ? |
|
|
I think I have solved my immediate problem of getting extended comboboxes using WinX to look like regular comboboxes using the Windows API. For me I took the XBLite code generated by ViXen using WinX and for the extended comboboxes I removed the $$WS_BORDER from the style of the extended combobox and changed $$WS_EX_CLIENTEDGE to $$WS_EX_WINDOWEDGE.
It looks like if you only change CLIENTEDGE to WINDOWEDGE you get some change but still have a heavy border. Removing WS_BORDER lightens things up. I guess WS_BORDER combines with WS_WINDOWEDGE to make an extra-thick border.
Alan Taylor. |
|
|
Thank you, Guy. I'm glad you pointed out this feature of ViXen because I had missed it before. When I did as you said I got better-looking comboboxes.
I am still having trouble with the compiler - but that's for another thread, and once I can pin it down better.
Alan Taylor.
Hi Al,
1. removal of $$WS_EX_CLIENTEDGE extended style mask
Proceed as follows:
- run viXen on your project
- "unselect" $$WS_EX_CLIENTEDGE with Ctrl+mouse Left-click
- save and generate
2. WinX's $$WC_COMBOBOXEX vs WinAPI's $$WC_COMBOBOX
As you noticed, WinX uses the EXTENDED combobox class. Callum did so because it covers all the possibilities of $$WC_COMBOBOX, with some additional "niceties". However, they don't have the same Windows event messages. If you change WinX's combobox class, you invalidate all the associated WinXComboBox_* functions. Basically, you shoot yourself in the foot! (outch!)
Bye! Guy
|
|
|
Hi Al,
1. removal of $$WS_EX_CLIENTEDGE extended style mask
Proceed as follows:
- run viXen on your project
- "unselect" $$WS_EX_CLIENTEDGE with Ctrl+mouse Left-click
- save and generate
2. WinX's $$WC_COMBOBOXEX vs WinAPI's $$WC_COMBOBOX
As you noticed, WinX uses the EXTENDED combobox class. Callum did so because it covers all the possibilities of $$WC_COMBOBOX, with some additional "niceties". However, they don't have the same Windows event messages. If you change WinX's combobox class, you invalidate all the associated WinXComboBox_* functions. Basically, you shoot yourself in the foot! (outch!)
Bye! Guy |
|
|
I tried replacing $$WS_EX_CLIENTEDGE with $$WS_EX_STATICEDGE - no change in the appearance. I tried instead $$WS_EX_WINDOWEDGE - also no change in appearance.
I looked at the source code for WinX.x In WinX.x the $$WS_EX_CLIENTEDGE is used only once - in the function WinXAddEdit and I have no trouble with the appearance of edit boxes.
I looked at the WinX.x code for function WinXAddComboBox. As the code came to me in \winx_0_6_0_13_sources_1125\WinX_0_6_0_13_sources which I downloaded from this forum not long ago I can compile WinX.x fine. But if I change line 1023 from:
hCombo = CreateWindowExA (0, &$$WC_COMBOBOXEX, 0, style, 0, 0, 0, listHeight+22, parent, idCtr, hInst, 0)
to
hCombo = CreateWindowA (&$$WC_COMBOBOX, 0, style, 0, 0, 0, listHeight+22, parent, idCtr, hInst, 0) 'note three changes
' change CreateWindowExA to CreateWindowA, change $$WC_COMBOBOXEX to $$WC_COMBOBOX
' and delete the original first argument - was a zero in CreateWindowExA - because that argument is not used in CreateWindowA
and try to compile I get this error:
> Executing: C:\xblite\bin\xblite.exe "C:\xblite\winx_0_6_0_13_sources_1125\WinX_0_6_0_13_sources\WinXC.x" -conoff -lib -m4
> Compiling as a function library (DLL).
> Calling m4 macro preprocessor.
C:\xblite\WINX_0~1\WINX_0~1\WinXC.x(1020): Kind Mismatch(27)
> Done. Compiled file in 1360 msec
***** ERRORS = 1 *****
> Execution finished.
This I can't understand because line 1020 is:
'style = style|$$CBS_SIMPLE
a comment line. The 28th character position is the "L" in SIMPLE.
However, the 28th character position in line 1023 (the line with the call to function CreateWindowA) is the "&" character in the function argument.
Huh?? WC_COMBOBOX and WC_COMBOBOXEX are both window classes (http://msdn.microsoft.com/en-us/library/bb775491%28v=vs.85%29.aspx)
Have I discovered two problems? Or only one? Or have I some other elementary programming error?
Alan Taylor.
|
|
|
Hi Al,
I believe you used the extended style $$WS_EX_CLIENTEDGE.
Could you confirm that its removal corrects the combobox's visual appearence?
Bye! Guy |
|
|
I used WinX with ViXen to generate my program framework after I had trouble with the Windows API and ViXen. But I notice that the "drop-down-arrow-button" (whatever you call it) in the right corner of a combobox is partially hidden using the WinX version, while the Windows API version has a nice clean-looking "drop-down-arrow-button"
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. |
|
|
| ComGen: a comment generator |
|
|
| IniLib: an XBLite library that wraps WinAPI for INI files |
|
|
| FsoEmuLib: an XBLite library that emulates MS File System Object |
|
|
| DateX: an XBLite date library |
|
|
| Pedestrian Crossing Capacity |
|
|
I am using Windows XP Pro SP3. I recently have been trying XBLite with Vixen. I was trying to use the WIN API but I have become lost in the layers and layers of calls to functions and pre-defined variables. So I thought why not try the Vixen option of using XBasic's Xui? I hoped the documentation would be less deep and many-layered.
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.
|
|
|
I made someexperimentation on the binary search; here it is: BinSearchX_v1_01.zip, which contains:
- BinSearchX.x is a dll that contains FUNCTION BsxSearch (find$, @sorted$[]), a binary search;
- BinSearchGui.x is the corresponding demo GUI app,
- BinSearchGui_gen.vxn, the viXen project.
Enjoy! Guy |
|
|
Dont worry i will visit from time to time XBlite forum ....
belive or not i still dont made any program in XBlite ...
probably becose im to used with my own programming language.
From some aspects i will consider to use XBlite as free compiler and maby
(currently just maby....) to switch my development from currently campiler which i
use to XBlite.
I will try also if i catch some time to build my own editor for XBlite.
I know that XSed by Jose Roca is very good but i prefer my own stuff...
ok we will see...
|
|
Showing 1 - 30 (210 results found)
|
|
Home
Calendar
Search
Register
Login
