Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
Offline Andrey Ivashov  
#1 Posted : 27 August 2016 15:17:09(UTC)
Andrey Ivashov


Rank: Administration

Groups: Developers, Registered, Knovel Developers, Administrators, Advanced Member
Joined: 11/07/2008(UTC)
Posts: 1,286
Man
Russian Federation

Was thanked: 1415 time(s) in 482 post(s)
Release Candidate: SMath Studio 0.98.6083 available


Latest changes (against SMath Studio 0.98.6081)

  • Every first worksheet now always added maximized within SMath Studio window;
  • Cursor position change on selected Regions move fixed;
  • Required parenthesis automatically added in several cases;
  • Fixed issue when Area did collapse/expand on SMath Studio window maximize;
  • Logic to detect math equations from Clipboard improved;
  • Search for errors in plug-ins on application start improved;
  • Preloading assemblies to reduce first calculation time required on application start implemented;
  • Plug-ins which references standard regions (TextRegion, PictureRegion and PlotRegion) fixed for newer SMath Studio builds;
  • Main window activation after Splash Screen hiding fixed;
  • Displaying of current plug-in loading operation implemented on Splash Screen;
  • Splash Screen displaying logic improved.


Download

Edited by user 27 August 2016 21:50:21(UTC)  | Reason: Not specified

thanks 7 users thanked Andrey Ivashov for this useful post.
on 27/08/2016(UTC),  on 27/08/2016(UTC),  on 27/08/2016(UTC),  on 27/08/2016(UTC),  on 27/08/2016(UTC),  on 28/08/2016(UTC),  on 31/08/2016(UTC)
Offline Andrey Ivashov  
#2 Posted : 27 August 2016 15:50:13(UTC)
Andrey Ivashov


Rank: Administration

Groups: Developers, Registered, Knovel Developers, Administrators, Advanced Member
Joined: 11/07/2008(UTC)
Posts: 1,286
Man
Russian Federation

Was thanked: 1415 time(s) in 482 post(s)
Please note: starting of SMath Studio takes more time then in all previous releases (from 4 to 15 seconds based on the list of installed plug-ins).

What is a reason?

  1. SMath Studio preloads all plug-ins before main window is shown;
  2. SMath Studio preloads its own assemblies;
  3. SMath Studio checks (offline) if installed plug-ins were already tested with this version of the program, so they can be executed safely;
  4. SMath Studio initiates all its internals.


What it gives to user?

  1. It gives possibility to detect more possible errors in plug-ins compatibility (important because the most often bug report now is about plug-ins which are not updated) and to increase calculations on the first time these plug-ins used;
  2. It makes future use more smooth;
  3. Application become much stable because all assemblies already checked and loaded into memory;
  4. It makes first calculations as fast as possible.


Any plans to improve loading speed?

Yes, there are couple of techniques to improve speed in 2-10 times. I will use them in future, so loading speed of SMath Studio will be increased soon.
Please be patient, because currently the main problem is in plug-ins stability and their variety of versions.

Best regards, Andrey Ivashov.
thanks 6 users thanked Andrey Ivashov for this useful post.
on 27/08/2016(UTC),  on 27/08/2016(UTC),  on 27/08/2016(UTC),  on 27/08/2016(UTC),  on 27/08/2016(UTC),  on 29/08/2016(UTC)
Offline overlord  
#3 Posted : 28 August 2016 01:41:39(UTC)
overlord


Rank: Advanced Member

Groups: Registered
Joined: 23/07/2013(UTC)
Posts: 62
Turkey

Was thanked: 14 time(s) in 11 post(s)
Couldn't make Smath Studio Mono 0.98.6083 work on fully upgraded Arch Linux / KDE Plasma 5.
Smath Studio Mono 0.98.6081 works fine. I guess latest code change on TextRegionUtilities caused that.

Regards

Code:
[overlord@------ SMathStudioDesktop.0_98_6083.Mono]$ ./smathstudio_desktop_mono 
WARNING: The runtime version supported by this application is unavailable.
Using default runtime: v4.0.30319

(mono:14225): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",

(mono:14225): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",
- [AppDir] Special Functions (1.11.6083.7483) [13 ms]
- [UserDir] Mathcad File Access Functions (1.0.5997.41890) [21 ms]
- [UserDir] 3D Plot Region (Chart3DLib) (0.1.5997.41808) [6 ms]
- [UserDir] Custom Glyphs (1.1.5973.13108) [0 ms]
- [UserDir] DotNumerics (1.1.5997.41856) [16 ms]
- [UserDir] Maple Wrapper (1.0.6067.40150) [44 ms]
- [UserDir] Numeric Up-Down Region (0.2.6078.4873) [2 ms]
- [UserDir] MaximaPlugin (1.97.5327.41309) [14 ms]
- [UserDir] Hyperlink Region (1.0.6011.17119) [2 ms]
- [UserDir] Matlab C++ Math Library (1.0.5997.41897) [16 ms]
- [UserDir] Table Region (0.1.5951.11830) [7 ms]
- [UserDir] Writer Region (0.7.6075.12238) [36 ms]
- [UserDir] CheckBoxList Region (0.1.6078.4853) [2 ms]
- [UserDir] Data Exchange (1.1.6072.12900) [7 ms]
- [UserDir] Nonlinear Solvers (1.1.5992.25575) [25 ms]
- [UserDir] XLSX Import/Export (1.1.6047.42586) [3 ms]
- [UserDir] Image Region (2.97.5327.15954) [1 ms]
- [UserDir] RadioButtonList Region (0.1.6078.4885) [2 ms]
- [UserDir] Statistical Tools (1.0.5906.17253) [15 ms]
- [UserDir] Excel Files Plugin (1.3.5575.28855) [1 ms]
- [UserDir] ALGLIB® - numerical analysis library (1.0.5997.41821) [12 ms]
- [UserDir] Conditionally Formatted Label (1.0.6078.4865) [2 ms]
Could not load signature of TextRegionUtilities.SearchAndReplace:FocusWriterRegion due to: Could not load file or assembly or one of its dependencies. assembly:WriterRegion, Version=0.3.5878.33870, Culture=neutral, PublicKeyToken=null type:<unknown type> member:<none>
Stacktrace:

  at <unknown> <0xffffffff>
  at (wrapper managed-to-native) System.Reflection.MonoMethod.get_IsGenericMethod (System.Reflection.MonoMethod) <0x0005a>
  at System.Reflection.MonoMethod.get_ContainsGenericParameters () <0x00022>
  at SMath.Manager.GlobalParams.PreloadAssemblies (System.Reflection.Assembly) <0x000bd>
  at SMath.Manager.PluginsManager.LoadOne (string) <0x0052f>
  at SMath.Manager.PluginsManager.LoadBanch (SMath.Manager.PluginsStatusEventHandler,System.Collections.Generic.List`1<SMath.Manager.PluginInitialMeta>,System.Collections.Generic.List`1<SMath.Manager.PluginInfo>&) <0x00a1b>
  at SMath.Manager.AppSettings.Initialize (SMath.Manager.PluginsStatusEventHandler,System.Collections.Generic.List`1<SMath.Manager.RecentPage>,int[],int,int,int,int) <0x003b3>
  at .. (string[]) <0x001d3>
  at (wrapper runtime-invoke) <Module>.runtime_invoke_void_object (object,intptr,intptr,intptr) <0x000c8>

Native stacktrace:

        mono() [0x4acddf]
        mono() [0x500dce]
        mono() [0x428a43]
        /usr/lib/libpthread.so.0(+0x11080) [0x7f0821e13080]
        mono() [0x53ca3d]
        [0x4200c71b]

Debug info from gdb:

[New LWP 14226]
[New LWP 14227]
[New LWP 14228]
warning: File "/usr/bin/mono-sgen-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
To enable execution of this file add
        add-auto-load-safe-path /usr/bin/mono-sgen-gdb.py
line to your configuration file "/home/overlord/.gdbinit".
To completely disable this security protection add
        set auto-load safe-path /
line to your configuration file "/home/overlord/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
        info "(gdb)Auto-loading safe path"
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
0x00007f0821e12afb in waitpid () from /usr/lib/libpthread.so.0
  Id   Target Id         Frame 
* 1    Thread 0x7f0822913780 (LWP 14225) "mono" 0x00007f0821e12afb in waitpid () from /usr/lib/libpthread.so.0
  2    Thread 0x7f08213ff700 (LWP 14226) "mono" 0x00007f0821e0f10f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
  3    Thread 0x7f081f7e7700 (LWP 14227) "Finalizer" 0x00007f0821e114f7 in do_futex_wait.constprop () from /usr/lib/libpthread.so.0
  4    Thread 0x7f0810479700 (LWP 14228) "mono" 0x00007f082192c48d in poll () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f0810479700 (LWP 14228)):
#0  0x00007f082192c48d in poll () from /usr/lib/libc.so.6
#1  0x00000000421514c6 in ?? ()
#2  0x0000000000000002 in ?? ()
#3  0x00007f0810477ad0 in ?? ()
#4  0x00007f08217122e0 in ?? ()
#5  0x00007f080bed8970 in ?? ()
#6  0x0000000000000002 in ?? ()
#7  0x00007f080bf10900 in ?? ()
#8  0x00007f080c001960 in ?? ()
#9  0x00007f0810477ad0 in ?? ()
#10 0x00007f0810477ad0 in ?? ()
#11 0x00007f0810477000 in ?? ()
#12 0x00007f0821712300 in ?? ()
#13 0x00007f080bf10001 in ?? ()
#14 0x00007f0810477ad0 in ?? ()
#15 0x00000000421610f8 in ?? ()
#16 0x00007f08104773f0 in ?? ()
#17 0x00007f0810477ad0 in ?? ()
#18 0x00007f082143b498 in ?? ()
#19 0x00007f080bf10900 in ?? ()
#20 0x00007f08104773f0 in ?? ()
#21 0x00000000005bca68 in ?? ()
#22 0x00000000421490f0 in ?? ()
#23 0x0000000000000011 in ?? ()
#24 0x4068900000000000 in ?? ()
#25 0x4029000000000000 in ?? ()
#26 0x0000000000000011 in ?? ()
#27 0x4068f00000000000 in ?? ()
#28 0x4029000000000000 in ?? ()
#29 0x3fb999999999999a in ?? ()
#30 0x0000000021710100 in ?? ()
#31 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f081f7e7700 (LWP 14227)):
#0  0x00007f0821e114f7 in do_futex_wait.constprop () from /usr/lib/libpthread.so.0
#1  0x00007f0821e115a4 in __new_sem_wait_slow.constprop.0 () from /usr/lib/libpthread.so.0
#2  0x00000000005b7d57 in ?? ()
#3  0x0000000000597dd1 in ?? ()
#4  0x0000000000648a6a in ?? ()
#5  0x00007f0821e09454 in start_thread () from /usr/lib/libpthread.so.0
#6  0x00007f08219357df in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f08213ff700 (LWP 14226)):
#0  0x00007f0821e0f10f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
#1  0x0000000000617283 in ?? ()
#2  0x00007f0821e09454 in start_thread () from /usr/lib/libpthread.so.0
#3  0x00007f08219357df in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f0822913780 (LWP 14225)):
#0  0x00007f0821e12afb in waitpid () from /usr/lib/libpthread.so.0
#1  0x00000000004aceb6 in ?? ()
#2  0x0000000000500dce in ?? ()
#3  0x0000000000428a43 in ?? ()
#4  <signal handler called>
#5  0x000000000053ca3d in ?? ()
#6  0x000000004200c71b in ?? ()
#7  0x0000000000000016 in ?? ()
#8  0x00007f0821714fe8 in ?? ()
#9  0x00007f08217149d0 in ?? ()
#10 0x00007f08094a1180 in ?? ()
#11 0x00007f08217149d0 in ?? ()
#12 0x00000000012e5220 in ?? ()
#13 0x0000000000000016 in ?? ()
#14 0x0000000000000014 in ?? ()
#15 0x00007ffef842b870 in ?? ()
#16 0x000000004200c613 in ?? ()
#17 0x00007f0821714fe8 in ?? ()
#18 0x00007f08217149d0 in ?? ()
#19 0x00007f08094a1180 in ?? ()
#20 0x00007f0821712888 in ?? ()
#21 0x00007ffef842b8a0 in ?? ()
#22 0x000000004214f28e in ?? ()
#23 0x00007f08217108d8 in ?? ()
#24 0x00007ffef842bcd0 in ?? ()
#25 0x00000000022a8020 in ?? ()
#26 0x00007f08217108d8 in ?? ()
#27 0x00007f08217107e8 in ?? ()
#28 0x0000000000000001 in ?? ()
#29 0x00000000022e6a20 in ?? ()
#30 0x0000000042147da0 in ?? ()
#31 0x0000000000000000 in ?? ()

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

Aborted (core dumped)
[overlord@------- SMathStudioDesktop.0_98_6083.Mono]$ 
Offline JaanP  
#4 Posted : 28 August 2016 21:25:01(UTC)
JaanP

Rank: Newbie

Groups: Registered
Joined: 24/03/2016(UTC)
Posts: 9
Finland

Was thanked: 1 time(s) in 1 post(s)
The last build (0.98.6083) broke something in screen scaling. Now in Win 10 high resolution screens (Surface 3 pro) the program is unusable, mouse pointer scales to wrong place, menu fonts are too big and toolbar fonts too small.

SMath_screenshot.png
Offline Jean Giraud  
#5 Posted : 29 August 2016 00:09:58(UTC)
Jean Giraud


Rank: Advanced Member

Groups: Registered
Joined: 04/07/2015(UTC)
Posts: 3,152
Canada

Was thanked: 608 time(s) in 471 post(s)
The last build (0.98.6083) broke something in screen scaling.
Now in Win 10 high resolution screens (Surface 3 pro) the program is unusable,
mouse pointer scales to wrong place, menu fonts are too big and toolbar fonts too small.
____________________________________________

I don't use those gadgets "Surface and the likes" . The original graph is Smath pixel size
not like Mathcad used to be ½ pica [6 pixels]. The original is 708 pixels wide 96 ppi.
Thus, once transferred on Surface 3 that has resolution 216 ppi , it will appear zoomed
down by a ratio of 216/96 = 2.25 ... appearing pretty small . Further, your screen shot
is from whatever transmitted and finally appears pretty blurred on the back 96 ppi PC.
To me, Surface goes no further than playing with cat fur or writting "Hello Grandma".
Smath is essentially not a CAD tool, i.e: not an SVG software like the "likes".
Your screen shot is zoomed down 2.25 ... pixels for pixels.
If you read your Surface back on PC 96 ppi, it should reappear like original.

If you would create something worth for the Smath community and transmit such a
piece of crap from Surface ... better attach a readable Smath document.
Offline JaanP  
#6 Posted : 31 August 2016 07:40:12(UTC)
JaanP

Rank: Newbie

Groups: Registered
Joined: 24/03/2016(UTC)
Posts: 9
Finland

Was thanked: 1 time(s) in 1 post(s)
The problem was the Image Region plugin and after removing it, everything returned to normal. Curiously, this problem has never occurred with earlier builds in my Surface Pro. The screenshot was attached in original size. At lower resolution screens, it is downsized by the web browser and can probably look pretty horrible. This is the reason I use Surface: excellent screen. One can save the picture and inspect it in original resolution. High resolution screens are getting common and 4K is soon the monitor standard. I think it would be smart to keep Smath compatible with modern hardware.

Edited by user 31 August 2016 07:50:47(UTC)  | Reason: Not specified

Offline Davide Carpi  
#7 Posted : 31 August 2016 17:01:54(UTC)
Davide Carpi


Rank: Advanced Member

Groups: Registered, Advanced Member
Joined: 13/01/2012(UTC)
Posts: 2,045
Man
Italy
Location: Italy

Was thanked: 1040 time(s) in 683 post(s)
Originally Posted by: JaanP Go to Quoted Post
The problem was the Image Region plugin and after removing it, everything returned to normal.

Thank you for pointing out both the issue and the cause Good

Originally Posted by: JaanP Go to Quoted Post
Curiously, this problem has never occurred with earlier builds in my Surface Pro.

Because plugins are loaded differently in this relase
Originally Posted by: Andrey Ivashov Go to Quoted Post
Preloading assemblies to reduce first calculation time required on application start implemented;

We'll fix it.

Originally Posted by: JaanP Go to Quoted Post
High resolution screens are getting common and 4K is soon the monitor standard. I think it would be smart to keep SMath compatible with modern hardware.

I agree. BTW 4k is just the number of pixels, the issues are all about DPI/PPI different from 96.

Edited by user 31 August 2016 17:49:40(UTC)  | Reason: Not specified

Best regards,

Davide

---
If you like my plugins please consider making a donation to SMath Studio
Offline Andrey Ivashov  
#8 Posted : 01 September 2016 22:06:47(UTC)
Andrey Ivashov


Rank: Administration

Groups: Developers, Registered, Knovel Developers, Administrators, Advanced Member
Joined: 11/07/2008(UTC)
Posts: 1,286
Man
Russian Federation

Was thanked: 1415 time(s) in 482 post(s)
Originally Posted by: Davide Carpi Go to Quoted Post
Thank you for pointing out both the issue and the cause Good

Just for reference: http://en.smath.info/for...e-display.aspx#post35142

Best regards.
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.