Custom Glyphs plugin (previously known as Functions' Extension) - Messages
- SS-83: custom skins for Maxima wrappers
The skin is applied to any Maxima(#) function (regardless the number of arguments)
As mentioned in the BTS, if is in Kay's plans (and there aren't bugs/things to change) he can copy the IPluginRegionDrawing code inside the Maxima MainClass.cs to have this feature embedded in the plugin.

Best regards,
Davide
I see two potential improvements with the size control of the outer parens
- They are a bit big for single line arguments
- They are a bit small for large expressions (smaller than the next inner level)
For outsiders it might be a bit difficult to find out what the symbol means and how to input it, but inside SMath you can inspect the help string by typing F12 when the function is marked. Would be fine to have the symbol on a side panel palette.
WroteReally nice, Davide. Thanks a lot.
I see two potential improvements with the size control of the outer parens
- They are a bit big for single line arguments
- They are a bit small for large expressions (smaller than the next inner level)
You're welcome. I've made a change about the brackets following your suggestions (plugin updated)
WroteFor outsiders it might be a bit difficult to find out what the symbol means and how to input it, but inside SMath you can inspect the help string by typing F12 when the function is marked. Would be fine to have the symbol on a side panel palette.
This is a problem for any "dressed function" as you know (here range(#) is on the top of the hits).
AFAIK toolbars/palettes are hardcoded in SMath, so actually we can only ask in the BTS if is possible to unlock these features.
I have a problem with the function 'cases' if used within the definition of a function that expects as a result numbers or strings.
[albumimg]353[/albumimg]
sergio
Wrote
I have a problem with the function 'cases' if used within the definition of a function that expects as a result numbers or strings.
cases() can only handle results that can be multiplied, as the function is expanded into a sum of the possible results multiplied by individual boolean statements, resulting in 0 or 1. Unless Andrey allows multiplication of strings (which could be very useful, at least multiplication by integers) or unless Davide changes the implementation of cases(), you are limited to numbers, matrices, lists and the like.
You can, however, wrap your strings into matrices and extract the element afterwards. That is not really a good solution, because outsiders won't comprehend the role of the index. Last not least this is also due to that one cannot tell the matrix brackets from ordinary algebraic ones
Edit: The above said applies only to numeric evaluation of the result. The solution is much easier, just switch the result optimization to "symbolic". This works no matter how the optimization setting of the definition is made.

switch the optimization of the [math eng]s.c(z)[/math] definition to "numeric" or "none". This uses a nested if/else structure instead of the symbolic sum (available just if you define your function as "symbolic"; this is shown also in the first post attachment).
In wide worksheets you can check fastly the definition optimization calling an evaluation using "none" as optimization:
- if you see the sum with booleans, you have defined the function as symbolic;
- if you see the cases function, you have defined the function as numeric/none.
best regards,
Davide
in fact I often do not pay attention to this option (symbolic-numeric). It would be useful to be able to visually differentiate this aspect
sergio
Wrotein fact I often do not pay attention to this option (symbolic-numeric). It would be useful to be able to visually differentiate this aspect
Yes, absolutely. You might consider voting for BTS issue SS-19.

I'm unsure on what is happening here, moving the cases outside the function it works correctly

Whatever is the problem, seems that eval() helps to bypass the issue :d
I have solved this equation in sage math. Please guide me how to solve this equation in smath.
Here an example based on your function (stripped off some decimals, just to make the example)
P.S. if your question is not related with a plugin in particular, the next time please open the question in a new thread in the Questions section
- Project name changed;
Since this relase, this plugin will be used only to add glyphs to existing functions in third party packages (such as Maxima) or not yet implemented functions. Real functions (at, ternary booleans, cases, Kronecker, perc, permil) will be moved in the Custom Functions plugin. I think this is better in terms of organization of the plugins and less cucumbersome to understand from the user why some functions are in a plugin instead of another.
I'm trying to make the transition as smooth as possible (even if this was a beta plugin with much less downloads of the Custom Functions), thus all functions are still included in this plugin but hidden (no dynamic assistance, no glyphs, no more documented here)
-
New Posts
-
No New Posts