Thursday, December 19, 2013
Friday, December 23, 2011
Constants defined in the VCX or SCX include file are evaluated at compile time now. When you rebuild an existing project make sure to select Guineu > Clean up project name from the menu to force Guineu to rebuild all project files.
PRIVATE variables can be defined and are created in a truly private fashion. Undeclared variables are now PRIVATE, just like in Visual FoxPro. Missing variables raise an error message except when being assigned to. PARAMETERS creates private variables whereas LPARAMETERS is responsible for creating local variables.
Parameters can now be passed by value or by reference. Call the PARAMETERS() function to determine the number of parameters.
Some commands in Visual FoxPro are not relevant during program execution. EXTERNAL is a good example and is now supported by Guineu. Just like in the Visual FoxPro runtime this command does absolutely nothing. Previously, though, having the command in the code would raise a compiler error in Guineu due to an unknown token.
Code lines containing macro substitutions (& command) do not cause an error anymore. Currently, they are skipped at runtime since there's no tokenizer being part of Guineu.
Thursday, December 15, 2011
There are also minor bugfixes in the STREXTRACT() function and the Listbox control.
Monday, December 12, 2011
Some of these features are still lacking such as accessing a bluetooth or serial printer, retrieving GPS information, obtaining phone book entries and text messages, and much more. Quite often there's sample code for C# or VB.NET for the Microsoft Compact Framework. Yet, often it's only few who request a particular feature. That makes it particular difficult to implement a solution that covers not only those developers particular needs, but also the needs of others in future scenarios.
This release is a major step forward!
We now support .NET objects in the same manner as native objects. The philosophy behind Guineu has always been to keep the look and feel of Visual FoxPro. Therefore you use .NET objects exactly like you would use native objects in Guineu or ActiveX controls in Visual FoxPro. There are no new commands or functions as the next sample demonstrates:
The OS() function implements values 1-6 now. OS(6) returns the platform. This is 1 for Windows 9x, 2 for any Windows NT based system (NT, 2000, XP and later), and 3 for Windows mobile.
Repeatedly executing CREATE CURSOR would open a further cursor with the same alias.
ADIR() returned the wrong number of entries and wouldn't indicate directories.
SYS(2015) would not return a new value every call.
<assemblyIdentity name="OpenNETCF" publicKeyToken="E60DBEA84BB431B7" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-220.127.116.11" newVersion="18.104.22.168"/>
Tuesday, January 26, 2010
I just noticed that the past releases contained an older version of GuineuIDE.EXE without the fixes for the DO FORM problem some of you encountered. The new build contains the correct version. To benefit from the fixed generated code, you either have to modify the form (just changing the time stamp is sufficient) or delete the *.SCX.PRG files. Otherwise GuineuIDE won't regenerate the files.