@Alexandrakristensen24 I was unable (as yet) to recover that corrupted portion, which contained a faulty image portion.

Your attachment's faulty portion does seem to start at line 274 of the XML. But there are only 286 lines in the file. It's quite possible that your attachment doesn't contain much more data, and that the (nor properly saved) original was actually much larger.

@C_R 

As I'd already mentioned in my original Answer: the custom mechanism is faulty in M2024.0.

I've already reported that functionality regression.

@C_R Regardless of which command you might extend, you'll need a conditional to test for type `=`.

Otherwise you'll have weird errors when applying rhs,lhs accidentally to type algebraic, Matrix, piecewise, etc.

What version are using? Did you see the part of my Answer that explained that the `simplify/ext` mechanism doesn't work properly in Maple 2023.2 and Maple 2024.0?

The general mechanism worked in 2022.2.

Which are you using here?

@C_R It may be due to the special characters in the file name. The OP could try renaming it.

@C_R Experiment and the quest for understanding are great motivations. I was curious, is all. Thanks.

I'd have to study those other examples later.

@mmcdara 

I gave the Compile variant because I didn't know whether you wanted to repeat this operation on many Matrices or column choices.

If anything else has been compiled then part of the overhead is lessened. Also, you might be able to get a faster compilation without inmem=false, but that may depend on version and OS.

In later Maple versions there are also some variants using andseq (possibly with evalhf), which also allows for a quick bailout.

@nmacsai You can change the font for the color-bar's textplot values.

colbar_M2023_4.mw

[edit] In Maple 2024 such adjustments are directly possible via additional options, eg.
   colorbar=[barcaption = ..., labelfont = ... ]
see  ?plots,colorbar

@Ronan You're very welcome; I'm glad if it suits your purpose.

I'm not quite sure that I understand that screenshot, though. Was this elision mechanism used in that shot?

@nmacsai I forgot to ask whether the effect you wanted could not at all be accomplished with a shortened view option choice.

Yes, there is a way to decompose and reparse the output of InlinePlot, to get back to a plot structure.

But that mentioned zoom/scale is not part of a plot structure. It's only part of the XML markup of the actual worksheet. So reparsing from an InlinePlot's XML return back to an actual plot structure would not retain an such scaling/zoom level information.

If that scale/zoom (like with right-click manipulator) were a programmatic part of a plot structure itself then I'd have shown that way in your previous Question.

However, another possibility for getting a "zoomed" effect might be to use the viewpoint option with just a single frame.

note: please put your close followups on this topic as Comment/Reply in your earlier Question, or Branch from that, instead of spawning more wholly separated and unlinked Question threads for it.

For fun, here is the first example, but using the allsolutions option to get a result in terms of conditional relations.

(Sorry, this site doesn't render it so nicely.)

Download trip_int_exb.mw

Download trip_int_ex2.mw

You cannot link just the character length or length of the 1D code representation of a general expression with the width the takes to pretty-print it as 2D Output. It generally needs a bit more finesse, according to type of expression.

However, I've seen at least one quite decent attempt at estimating 2D rendering width for algebraic expressions. I'd have to go hunting to find it.

But the elision fade-out was done using Typesetting constructs, in the instance I'm recollecting. I'm not 100% sure that the further/repeat 2D type-setting by Tabulate would work ok. If not then the DocumentTools:-Layout constructors might be used to get the same kind of Table result.

Alas it is the end of the day for me.

@nmacsai These two ways of injecting the COLBAR substructure into the cylinder's PLOT3D structure end up with the same result.

Download colbar_M2023_2.mw

I used contourplot to get its accompanying color-bar. You could alternatively use densityplot and then pass that your choice of colorscheme option. Eg,

colbar_M2023_3.mw

[edit] The constructed color-bar is itself just a 2D densityplot with aligned values shown. There are doubtless more efficient ways to construct it, and I just chose one that was reasonably straightforward. The trick is to wrap it in a COLBAR call, and then make it the new last operand of the PLOT3D structure. You could likely use other kinds of 2D plots. The GUI recognize the COLBAR within the PLOT3D and renders it (only) on the right side.