I moved to v3.1 from v10.1 a few months ago and the studio is noticeably (aggravatingly at times) slower in certain operations,mainly opening tasks,zooming into expressions and opening forms.I run it on a new laptop,Win10, 8 GB memory,SSD,should be flying but it's not.I've read that Windows Defender may not play nice with VS 2015 so I've excluded the Magic studio from real-time checking but even turning it off completely doesn't help much.

Any hints what I should look at?

Thanks

Pavel

Pavel,

We've actually frustratingly and recently seen the slowness you describe on a 3.2 install.  Seems exporting and importing your ENTIRE app as new is the best way to resolve it.
--
Charles Coe, CPA, MCSE

New Orleans, Louisiana

I've considered that as well  but judging from the responses here so far I'm not convinced as it appears to have its share of problems,just different ones.

Pavel

I moved to v3.1 from v10.1 a few months ago and the studio is noticeably (aggravatingly at times) slower in certain operations,mainly opening tasks,zooming into expressions and opening forms.I run it on a new laptop,Win10, 8 GB memory,SSD,should be flying but it's not.I've read that Windows Defender may not play nice with VS 2015 so I've excluded the Magic studio from real-time checking but even turning it off completely doesn't help much.

Any hints what I should look at?


Thanks

Pavel

I'll try that tonight,thanks.

Pavel

Met vriendelijke groet - With kind regards, Sabrina Horst Analist/programmeur +31 (0)6 20303889

Think more, type less :-)

---

From: main@magicu-l.groups.io <main@magicu-l.groups.io> on behalf of Avgerinos <mento@...>
Sent: Tuesday, February 14, 2017 10:22:01 AM
To: main@magicu-l.groups.io
Subject: Re: [magicu-l] V3 slow

 

Hi Pavel

Excluding Magic from Windows Defender did work for me: It decreased by
40% the time required to run a full program check (W10, 16Gb, i7, SSD).

My personal experience so far from :
Development in version 3 is much slower that it was in prior versions.
This is an unfortunate fact you cannot avoid no matter how much money
you invest in hardware.
Almost 2 years after v3 launch and this tool is failing to make me feel
trust as in the past. For months after I moved to version 3, I kept
feeling like I 've been cheated.
Version 3.1b at least became a bit faster in some aspects, plus I got
rid of the frequent Studio crashes. Version 3.2 does not offer yet
something interesting to me, no speed, no issues solved.

Regards
Avgerinos

On 14/2/2017 2:00 μμ, Pavel Mencl wrote:
>
> I moved to v3.1 from v10.1 a few months ago and the studio is
> noticeably (aggravatingly at times) slower in certain
> operations,mainly opening tasks,zooming into expressions and opening
> forms.I run it on a new laptop,Win10, 8 GB memory,SSD,should be flying
> but it's not.I've read that Windows Defender may not play nice with VS
> 2015 so I've excluded the Magic studio from real-time checking but
> even turning it off completely doesn't help much.
>
> Any hints what I should look at?
>
>
> Thanks
>
> Pavel
>
>

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

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

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

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 v94 or uniPaaS, so the end users are happy. 

For developers - it is much more Challenging than Xpa 2.5 because of the Visual Studio which is embedded in this version but you can used to it at the end

David Rechter
Go Up Technology