X-Y Plot Region - Extends SMath Studio with a X-Y Plot Region. - Сообщения
There's no better option than having choices.
Procrustes solution must be banned:
https://en.wikipedia.org/wiki/Procrustes ...
Procrustes solution must be banned:
https://en.wikipedia.org/wiki/Procrustes ...
Do to others as you would like them to do to you!
Knowledge is of no value unless you put it into practice - Chekhov
You should understand that the flexibility of implementation (the ability to choose) is limited by future compatibility. It's like in the structure of DNA - you drag all the garbage of evolution along with you and must support it. Each new "mutation" of the component must be compatible or include all the previous ones, so as not to break thousands of documents. This is especially true for the appearance, which must always be unambiguously restored from the saved document.
You can now use the UseDefault property, but when transferring a document to another user who doesn't have a new version of the component or doesn't want to install it, the appearance should not change much. The other user will not see your settings, because the old version of the plugin doesn't know anything about it.
You should understand that your request to restore the standard behavior of the component will break the appearance of already created documents. I think about this for you, but next time you should also imagine how your preferences will affect thousands of already created documents. I showed examples above.
So freedom of choice is to allow many users to work as they are used to and not break their work, ensuring compatibility in both directions. This is a difficult task. That is why I sometimes refuse to make changes, because the overall picture of the consequences may not be clear and require significant research.
You can now use the UseDefault property, but when transferring a document to another user who doesn't have a new version of the component or doesn't want to install it, the appearance should not change much. The other user will not see your settings, because the old version of the plugin doesn't know anything about it.
You should understand that your request to restore the standard behavior of the component will break the appearance of already created documents. I think about this for you, but next time you should also imagine how your preferences will affect thousands of already created documents. I showed examples above.
So freedom of choice is to allow many users to work as they are used to and not break their work, ensuring compatibility in both directions. This is a difficult task. That is why I sometimes refuse to make changes, because the overall picture of the consequences may not be clear and require significant research.
Russia ☭ forever, Viacheslav N. Mezentsev
Right,
Compatibility - great feature and hard task. Thanks to Andrey and to all the developers.
While talking about freedom, what about the creation of a user’s function totally encapsulated. This must be simpler than the graphical tools (?)…
This could produce “happiness” to more than one…
Have a nice day.
Compatibility - great feature and hard task. Thanks to Andrey and to all the developers.
While talking about freedom, what about the creation of a user’s function totally encapsulated. This must be simpler than the graphical tools (?)…
This could produce “happiness” to more than one…
Have a nice day.
Do to others as you would like them to do to you!
Knowledge is of no value unless you put it into practice - Chekhov
WroteWhile talking about freedom, what about the creation of a user’s function totally encapsulated. This must be simpler than the graphical tools (?)…
This could produce “happiness” to more than one…
Have a nice day.
I don't think it is completely possible plugin-side, as there is no direct connection with the evaluation operator (I.e. a sandbox(...) function on the RHS won't be able to connect to the arguments of a function on the LHS); also I'm not sure you can keep sealed the assignments from the global context without some very strict rule.
If you like my plugins please consider to support the program buying a license; for personal contributions to me: paypal.me/dcprojects
1 пользователям понравился этот пост
ioan92 12.11.2024 01:08:00
Thanks for the answer.
So, the only solution is in Andrey's hands?
However, there is a model, that of imbedded (eg. trigonometrical) functions.
I imagine that there are many peoples annoyed to perpetually decorate the local variable with @; #; $ etc.
So, the only solution is in Andrey's hands?
However, there is a model, that of imbedded (eg. trigonometrical) functions.
I imagine that there are many peoples annoyed to perpetually decorate the local variable with @; #; $ etc.
Do to others as you would like them to do to you!
Knowledge is of no value unless you put it into practice - Chekhov
WroteI imagine that there are many peoples annoyed to perpetually decorate the local variable with @; #; $ etc.
It's a safe approach but it's not really needed since the introduction of the built-in Clear() function. You can place a Clear(all_variables_I_want_local_used_in_the_function) and you are done; it's also very similar to declaring the local variables before using them.
If you like my plugins please consider to support the program buying a license; for personal contributions to me: paypal.me/dcprojects
1 пользователям понравился этот пост
sergio 12.11.2024 15:50:00

Plugin updated.
Changes:
- added support for copying a set of properties.
The following properties are not currently supported: Name, Points, Traces.
The property set contains the current values of the component settings. They can be used as a template. To control the component, they must be located above it in the document.
Файл не найден. Файл не найден.
Russia ☭ forever, Viacheslav N. Mezentsev
2 пользователям понравился этот пост
https://en.smath.com/forum/yaf_postsm86081_X-Y-Plot-Region.aspx#post86081
@Davide,
I also use Clear, but, IMHO, the use of Clear can destroy values useful later.
@Davide,
I also use Clear, but, IMHO, the use of Clear can destroy values useful later.
Do to others as you would like them to do to you!
Knowledge is of no value unless you put it into practice - Chekhov

Plugin updated.
Changes:
- added support for copying a set of properties (Points, Traces#n).
The following property is not supported: XYPlot.Name. This is for safety.
The property set contains the current values of the component settings. They can be used as a template. To control the component, they must be located above it in the document.
When copying the properties of a curve, the component name must be corrected by yourself, since it is equal to "XYPlot". It's hard to automate this part.
Файл не найден. Файл не найден.
Russia ☭ forever, Viacheslav N. Mezentsev
3 пользователям понравился этот пост
Should we assume these new Copy options are not working on linux?
WroteShould we assume these new Copy options are not working on linux?
Should work under Linux, I can't check.
This is not a new feature, but a feature that has been used for some time to manage the component. The copy feature was added to avoid having to remember the full names of the component properties.
Russia ☭ forever, Viacheslav N. Mezentsev

Plugin updated.
Changes:
- fixed the problem with drawing images;
- some demo examples are inserted from looped lists, these examples are separated from constant ones.
xyplot-drawimage-file.sm (7 КиБ) скачан 215 раз(а).
xyplot-drawimage-tag.sm (67 КиБ) скачан 206 раз(а).
xyplot-drawimage-mat.sm (8 КиБ) скачан 216 раз(а).
xyplot-drawimage-mat-rgb.sm (18 КиБ) скачан 209 раз(а).
Russia ☭ forever, Viacheslav N. Mezentsev
2 пользователям понравился этот пост
4 пользователям понравился этот пост
Davide Carpi 19.11.2024 02:20:00, Oscar Campo 17.11.2024 08:35:00, Alvaro Diaz Falconi 18.11.2024 11:05:00, overlord 17.11.2024 17:26:00
2 пользователям понравился этот пост
3 пользователям понравился этот пост
Davide Carpi 19.11.2024 02:20:00, Alvaro Diaz Falconi 18.11.2024 09:40:00, overlord 17.11.2024 17:26:00
3 пользователям понравился этот пост
sergio 18.11.2024 16:33:00, Davide Carpi 19.11.2024 02:20:00, Alvaro Diaz Falconi 18.11.2024 09:40:00
Some Basic Image Manipulations.

Image-Basic.pdf (3 МиБ) скачан 174 раз(а).
Image-Basic.sm (2 МиБ) скачан 199 раз(а).
Best regards.
Alvaro.

Image-Basic.pdf (3 МиБ) скачан 174 раз(а).
Image-Basic.sm (2 МиБ) скачан 199 раз(а).
Best regards.
Alvaro.
3 пользователям понравился этот пост
francesco rapuano 18.11.2024 14:25:00, Вячеслав Мезенцев 18.11.2024 11:45:00, sergio 18.11.2024 16:33:00
3 пользователям понравился этот пост
francesco rapuano 18.11.2024 18:34:00, sergio 18.11.2024 16:33:00, NDTM Amarasekera 18.11.2024 18:42:00
-
Новые сообщения
-
Нет новых сообщений