Re: V3 slow


Todd Baremore
 

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 move to XPA desktop would be the need for integration with 3rd party tools/applications that require .NET 4.   That being said, the Print Data To Excel ability in 3.2a could come in handy.

Todd


On 2/17/2017 12:11 AM, John Knickerbocker wrote:

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


On Thu, Feb 16, 2017 at 10:41 PM Avgerinos <mento@...> wrote:

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, and this is why you see old style screens appearing here and there in studio.
Unfortunately, MSE seems to be still in the process of replacing old parts with new ones, and this makes every new release a risk to adopt.

In my opinion XPA3 was prematurely released - at least two years earlier than it should be.
This has already put in high risk all the good fame that was built in the past by Magic.
Plus risking the careers and relations with clients of those who rushed to adopt the new version. 

Avgerinos



On 16/2/2017 9:24 μμ, Pavel Mencl wrote:

Avgerinos,

similar here,I'm pissed that Tab controls no longer support & as an accelerator key. Some stuff is really intriguing: Magic studio itself uses the "old" Tab controls with accelerator key. Magic's main window has a Windows 10 style frame but windows within,say Programs,use Win 7 style (I guess).The same in runtime.And then most types of windows are the new style but default or Fit to MDI not.

Of course it's not a major issue,minor at best but it just doesn't feel right to me.

Pavel



Join main@magicu-l.groups.io to automatically receive all group messages.