A small step for mankind, but a big one for me (as I've never done that before).

NODEMaple has got its own YouTube channel, where I'd like to show some of the things that are possible with Maple for structural engineering.

https://www.youtube.com/@NODEMaple

As an alternative to YouTube you might a similar channel was created on PeerTube.

https://peertube.wtf/c/nodemaple/videos?s=1

In addition I've also uploaded v1.1.1 to Github, with some minor fixes and an update to the download package, where all Maple files were missing in the previous release.

Here are 2 more screenshots which show a bit more (Maple 2025).

The biggest difference is in the context menu in my opinion. But also help file text and document text is easier to read in the unrotated version.

Rotated:

Unrotated:

The problem with the 2025 release is, that the magnification doesn't work for components.

https://mapleprimes.com/questions/240064-Maple-2025--TextArea-Component-Ignores

@C_R 

I haven't been successful in reproducing the temporary fix from yesterday (unplug - replug) unfortunately.

There are differences in hardware between my office PC and my home PC, so I'll just give a quick summary.

Common for both

• Windows 11 Norwegian
• 32 Gb RAM
• Nvidia P620 (not exactly same VideoBIOS though), driver version 572.83
• Screens with 1920x1200 resolution, 100% zoom factor

Office-PC (font ok).

• HP EliteDesk 805 G6
• 4 screens

Home-PC (font with antialiasing issues)

• Fujitsu D958
• 3 screens

Some more tests today with Windows ClearType, but I can't see any effect on Maple.

P.S.: I found out that Java runtime parameters can be added in the C:\Program Files\Maple 2024\bin.X86_64_WINDOWS\launch.ini file. However there was no effect visible in Maple with any of the proposed command line parameters from the pdf file i posted yesterday.

Here's the next finding on that issue.

Pulling out one of the screen connectors and back again temporarily fixes the font issue. After that Maple doesn't show the font problem.

But after logging out and back again to Windows, the problem is back again (home PC, Nvidia P620, 3 screens).

It is not important which of the screens that is unplugged.

@C_R 

Just tried what Gemini has to say about that issue.

Seems to be complex, and not easy to pinpoint who's fault it is. Maple, Java, Windows or Nvidia?

Btw., how would I add any command line options into Java when starting up Maple?

Using_Maple_I_have_issues_when_one_screen_is_rota....pdf

I've managed to recreate the problem once on my PC in the office today. I thought it had to do with which ports that are used on the backside of the Nvidia P620, but was unable to recreate it afterwards.

Windows Update was running at the same time, and after restarting the PC I am unable to recreate the issue.

I'm a bit stuck to be honest.

@C_R 

This is really odd, I have tried all kind of changes on my home PC, and nothing works.

I have exactly the same Nvidia graphics card (Quadro P620), but just 3 screens instead of 4. I've tried to have the default screen on all 3 different screens, same result.

The only thing that works is to set rotation on the vertical screen to horizontal, this will make the text readable.

The problem is definitive related to Font anti-aliasing. Switching Font anti-aliasing off shows exactly the same text.

@C_R 

• Windows 11 (norwegian)
• all monitors have the same resolution (1920 x 1200)
• scaling 100%
• Workstations with external graphics card

But I'll have to check which monitor is primary in that case later today (your last question).

Just checked an almost similar setting but with a newer PC and 1 additional monitor with different results. 1 vertical and 3 horizontal screens (same setup as above) doesn't show those issues, screen 2 is default screen.

Attached a screenshot from my office setup with Maple 2025 and 2024 on screen 1. Quite interesting that there is a difference in the layout by the way.

By the way, font rendering is set to default.

Thanks for the help.

This section in Maple 2025 Help should be updated.

worksheet,reference,WorksheetToolbar

@alex_b 

I am of course deeply honored by your review, and hope that you'll find this work inspiring for other projects. Maple is a great software package and I couldn't have done this project without the help from the community on MaplePrimes.

The biggest pro in my opinion for an engineer is actually the possibility to have access to all stored values - both input and calculated - after a calculation (of course only if you know how they are stored). Obviously there is a lot of work to do on the documentation side, which I will hopefully will do in the nearest future.

Version 1.1.0 was just released a couple of days ago, with some minor bugfixes and the added functionality of cutting beams by angle.

The package can be downloaded on Github (https://github.com/Anthrazit68/NODEMaple).

Sorry about that, I'll do that next time.

Btw., it isn't possible to delete the post, is it?

Thanks a lot, found it.

@nm 

Thanks a lot, I managed to modify it to use the working directory instead, and got some results.

However the size of the output seems to be far less than the file size of my library. Any other things that could be responsible for that?

P.S.: If necessary I could drop the source file somewhere.

@janhardo 

My experience is really limited, as I only have used it for a couple of days.

As a minus first, it does not show logical errors in the code, undefined variables, and syntax errors like the Maple editor does.

On the plus side it has code colouring, and lists the names of procedures in the code in a side window (if you have the Maple language addin installed). It also has GitHub connection, which makes this part very easy.

Regarding reasons why I came up with this see https://www.mapleprimes.com/questions/238887-Read-In-Maple-Code-Attachments

(...plus recommendation by one of my daugthers)