Pavel, We did already many Xpa 3.2 conversion and i can tell you, from the experience of many customers which are already live, that Xpa 3.2 is almost 2 time faster in runtime with SQL databases than

I did exactly that, although not so much because I thought about the security issue. You can make an *amazing* little program if you work at it, combining all those little functions into one cool

Pavel, I did suggest that a while ago. If I remember correctly, MSE removed the built in user functionality when they stripped the Magic Engine from all built in UI functions. My understanding is

I ran into this issue as well. The solution was to completely uninstall Magic, clear the directory, then reinstall. Best regards, Arch

Hi magicians Anyone knows how to avoid the error regarding "ExcelPIA.dll" assembly when starting XPA3.2a? The dll is there but probably it fails to load (maybe because there is no office in this

I agree that mobile continues to improve, at least on the Android side. I have yet to venture into iOS. My desktop app remains in UP1.9 for now. The only thing that would compel me to

Suggested solution does work always A better solution is to add a condition to temporarily "unlink" the string variables from the ItemsList and DisplayList properties while updating them.

I believe it was Keith who suggested a while ago that we could ask for both! And you could choose if you want to use the built-in search/locate... by screen or use the component. Regarding the

Correction: message refers to tab-control and not to combo-box

Hi magicians Documenting an incompatibility in behavior of combo-box controls between XPA3.x v/s prior versions: Desktop app form contains a combo-control, with bot ItemsList & DisplayList

Hi Graham You 're right - my suggestion referred to desktop apps. Is that browser-control you mention as Magic control? Regards Avgerinos On 16/2/2017 11:02 μμ,

Yes, it's obvious they have moved their focus to mobile. Desktop apps practically have nothing to gain - only to lose On 17/2/2017 7:11 πμ, John Knickerbocker wrote:

Maybe, but the mobile got much stronger in the latest updates.

Thanks for that Todd, My build.gradle file is exactly the same as yours. My build.cmd now looks like below after I have removed the setting / updating of the java_home @Echo Magic RIA Build

Jordan, Here is my build.gradle file. It appears you have to many entries in yours. Try backing it up and using the following

Hi Todd & Brenda, Thanks for your replies and help. I am still getting the same error message: I have removed the updating of the java_home from the build.cmd, I have run all the updates to the SDK's

Hi Group, My company is using File Hold document management system and we are defining Meta data information for each file to store on the file hold file vault. My question is: is there a way to call

Hi Avgerinos, Thanks for your reply, however, .NET controls are not supported on Mobile devices. Regards Graham

Hi Graham The only solution I know is a nice trick that was mentioned here some years ago (yes this group is really magic! ) Tried it with uniPaaS & XPA3 and it works fine with both

Hi Pavel XPA3 is probably a wrap that encapsulates both old and new libraries. This is why it's almost double in size than it was Major functionalities are still served by the old engine,