Today we have released an installer for XSharp Cahors 2.8 which contains MANY new features and changes.
The what's new document describing all the changes (this build alone over 6 pages) can be found here:
{rsfiles path="general/Readme/whatsnew28.rtf"}
{rsfiles path="fox/Compiler/XSharpSetup28Fox.zip"}
A public version of X# 2.8 will follow next week.
We will demonstrate X# 2.8 on Thursday April 29. See this message for more information.
Two of my previously-reported DBFCDX-related problems are magically resolved!
Got a couple of new XIDE compiler warnings but I suppose that's a positive development.
I think it's important to mention that I've converted several hundred thousand lines of VO code to XSharp using the VOExporter utility and just about everything works. And what doesn't is quickly resolved.
Great work guys!
In my neck of the woods we have a term to describe such outstanding work. It can be understood in any dialect:
Badass !!
warning XS9066: Symbol 'GetSubMenu' is ambiguous. Could be 'VOWin32APILibrary.Functions.GetSubMenu(void*, int)' or 'VO.Menu.GetSubMenu(params XSharp.__Usual[])'. Using the function because in X# functions take precedence over methods. To call the method use the fully qualified name (for static methods) or prefix the call with 'SELF:' for instance methods.
What is the recommended way to fix those?
Leigh, this is completely up to you, depending on your programming style and which version you find more readable and intuitive. You can either simply ignore and disable the warning, or otherwise enable the "enforce self" compiler option (in the project properties), which will force you to prefix all calls to class methods with SELF: (or SUPER:) and this will remove the ambiguity and thus all related warnings will disappear.
looks like that's my story, too. Had issues with setSelective parent-child, when there was no matching child - now it's gone.
Happy camper here ;)
I have battled a weird bug for the last few months.
I cannot report it because I believe it is my code.
Will try this new build...
--
Rene
looks like that's my story, too. Had issues with setSelective parent-child, when there was no matching child - now it's gone.
Happy camper here ;)[/quote]
This post seems to be talking about me. I think I made a workaround like SetRelation instead. I have to revisit that code and I do not where... oh my...
I expect a ReportPro compiled to the latest X# is now coming.
and I will try out the Form Editor which I have crashes, consistent to my action. I will document this if still occurring with this build.
Thanks,
Rene
I expect a ReportPro compiled to the latest X# is now coming.
[/quote]
Rene, normally this should not be needed, previous dlls should still be working as is (version number of the runtime has not changed). Did you have any trouble using your current RP dlls?