Hi Vixeners,
I believe that I corrected all remainding bugs in viXen;
does it mean that viXen is ready to leave the beta stage???
I'd answer yes, but I'm not the right person to say so.
What I need now is viXen to be put to a torture test by the lot of you.
I'd like you to:
1. Download the Window installer at SourceForge
http://sourceforge.net/projects/visual-xblite/files/vixen%20version%201/VIXEN%20v1.99/vixen_setup_v1_99u.exe/download2. Run vixen_setup_v1_99u.exe to install viXen on your machine
3. Try to re-create some GUI demos from .\xblite\demo\gui
I'd start with .\xblite\demo\gui\edit\edit.x
- Load it into XSed
- Compile/link/run and see what it displayed
From within XSed execute viXen with menu option Tools/viXen.lnk
and try to reproduce the exact same window
Create a new folder ...\gui\edit\gen
and save your project as ...\gui\edit\gen\edit.vxn
YOU MUST NOT REPLACE ...\gui\edit\edit.x
Generate ...\gui\edit\gen\edit.x (only this time)
and include the code extracted from the demo program ...\gui\edit\edit.x
until the generated edit.x behaves just like the demo program.
###########################################
BEWARE that RE-GENERATING ...\gen\edit.x
would OVERWRITE your working source edit.x.
MAKE A COPY OF edit.x BEFORE RE-GENERATING!
###########################################
I'd try next:
. button\button.x
. static\static.x
. menu\menu.x
. combobox\combobox.x
. bitmapbutton\bitmapbutton.x
. unigui\unigui.x
Not only would you get a better grip at the Windows API,
but you would put viXen in a real usability test.
I welcome any feedback from your tests:
- bug reports
- UI suggestions
- generation suggestions
- none of the above, but a great user experience with viXen :-))
Thanks for your efforts.
Bye! Guy