---

Edited by user 24 June 2020 16:57:13(UTC)  | Reason: badges

Too fast ioan, there are many things to do and to fix before a relase


Is a region that show a SMath Studio numerical variable as written in a table; basically is an image, the look is customizable using the context menu (a cell editor like excel is too complicated to make for me); as for now there's only the body, I'll try to add other things (those shown in the dialog above and schematized below (colored boxes are all "optionals", as general idea); the hardest thing will be surely unit's handling ...


Best regards,

Davide

Edited by user 11 August 2013 22:00:08(UTC)  | Reason: Not specified

Davide, please take a look at this code by another Davide. Davide et impera!!
http://www.codeproject.c...en-Source-C-Grid-Control

Edited by user 12 August 2013 00:59:30(UTC)  | Reason: Not specified

Just want to mention that the matrix editor is part of the unofficial distribution.

I agree with Radovan and kilele that matrix/table editing features are much higher on the wish-list than corresponding display features. I guess that faking a real editor using the customregions interface with just a single placeholder is close to impossible or at least, inefficient.

Davide, to be honest, there are quite some topics on my wish-list, where all my hope rests on you, first of all the unit-proof functions (linsolve(), int(), Im(), Re(), arg()...) I just hope that the table region won't kill all chances for progress in these issues.

The possibility to display wide tables is in my mind, I've already a couple of ideas...

I'm very cautious about the possibility to edit matrices (and then systems or tables);
the actual SMath approach is very clear, because if you want to change something in an existing matrix you have two ways:
- manually: copy & paste the matrix to a new definition and edit;
- by programming: use el(), stack(), augment(), submatrix() to create "by routines" a different matrix;

the first (matrix editing on definitions) must be improved, and there are no objections;
the second (matrix editing on evaluations) works fine and keep trace of any change; here a manual editing could be very dangerous, if is not distinguishable; I hope no one thinks on a similar feature.
I've a lot of spreadsheets where a "temporary edit" to cover non common situations is become a hidden bug.

Edited by user 12 August 2013 21:16:10(UTC)  | Reason: Not specified

Hi Ioan,

Like anyone else I want a better matrix's editing (select by columns/rows by ctrl+drag and the insert/delete by context menu, f.e. would be a very nice feature ) but the question may be focused, because actions on definitions may be different from actions on evaluations; I agree that "a knife could be used as well in the kitchen as to kill somebody" but in the 99% of the cases, if you kill someone with a knife is because you want to use the knife against a man (instead of a beefsteak), and all those who have the opportunity to attend the scene recognize immediately that you're not peeling an apple, so the bad use is wanted and recognizable.
IMHO a manual editing "on the fly" on evaluated variables may be possible only if is easily recognizable, so "less manual" as possible; f.e. a region where you can see an outline of the matrix with red rows/colums where the region delete the rows and green rows/colums where new ones are placed (and maybe another color for cells where elements are replaced); here input and output are separated (by the region, like for the Andrey ComboBox), the intermediate steps are visibles, and the front end is "user friendly".
As I've written, hidden changes may be easily converted into hidden bugs (sometimes I open a worksheet after months, I can't remember all, other times I share the worksheets; and don't forget that if you can edit manually an evaluation, you can do it because you want it or because you have pressed something not intentionally ); is not ethical, are survival things



Best regards,

Davide

Edited by user 13 August 2013 13:50:57(UTC)  | Reason: Not specified

Indeed I was hoping that the ban of editing IN DISPLAY CONTEXT as opposed to INPUT CONTEXT could be agreed on in the community. This might be due to me overestimating the value of the principle that an SMath computation documents itself based on what I see is what is computed. Perhaps I could change my mind based on a convincing example of where display contents editing is useful.

I totally misunderstood you. I had the impression that you in fact did not agree to what Davide said and that you were questioning the traceability concern. But even if that was so, there was no intent to hurt, just to be clearly understood. Sorry for any pain.

[UPDATED]

- Improved compatibility between different localization settings;
- Number format now uses SMath's decimal separator instead of system's separator;
- Code Improved (units summary changes, size's calculation flow).

great job Davide,
I just want to report a small problem to open your sample file attachment in post #1 TableRegion.sm
I had to manually edit the file and change the size of font that had the decimal point, with a full size.
Smath Studio Desktop Portable 0.96 - Win7 64 bit

sergio

Hello, I am newbie in smath.
I'm playing with it, it seems amazing and I wanted to thank you for your work.
I have a little question regarding "Table Region": Is it compatible with the "SMath viewer"? It does not work to me.

Many thanks from Spain,
Pablo.