Securities Price History Graph has Vanished!
Good morning all,
I've just upgraded from MD 2022 to 2024.1 (5118) and the price history graph on the securities detail page has vanished. I haven't experienced this with any other version of MD and am wondering if there is an option in the new version to show/hide the graph (I assume there isn't).
Sorry if this issue has already been raised, although I can't see anything.
Regards
Neil
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Stuart Beesley ... on 24 Apr, 2024 11:14 AM
Have you clicked the security dropdown box to select the security you want?
2 Posted by soleroadams on 24 Apr, 2024 11:32 AM
If the account holds any investments, the drop-down box will automatically show the first investment when the securities detail page is opened. So you do not need to select one; at least that has been my experience with MD so far.
3 Posted by soleroadams on 24 Apr, 2024 11:43 AM
I'm not sure whether this is related but when I run the extension 'Select Performance Graph' from the Extensions menu, I get the following error:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@ UNEXPECTED ERROR CAUGHT!
Traceback (most recent call last):
File "security_performance_graph.py", line 6120, in <module>
File "security_performance_graph.py", line 6109, in run
File "security_performance_graph.py", line 6033, in setGraph
File "security_performance_graph.py", line 5460, in setGraph
AttributeError: 'org.jfree.chart.renderer.xy.XYLineAndShapeRenderer' object has no attribute 'setDefaultToolTipGenerator'
File "extension(security_performance_graph):security_performance_graph_bootstrap.py", line 105, in <module>
File "security_performance_graph.py", line 6128, in <module>
File "security_performance_graph.py", line 598, in dump_sys_error_to_md_console_and_errorlog
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
4 Posted by Stuart Beesley ... on 24 Apr, 2024 12:05 PM
Let me know on both.
5 Posted by soleroadams on 24 Apr, 2024 12:29 PM
1. Yes, many times!!!
2. v1012 is installed. Would it help to remove & re-install?
6 Posted by Stuart Beesley ... on 24 Apr, 2024 12:52 PM
https://yogi1967.github.io/MoneydancePythonScripts/
look for the latest signed version...
7 Posted by soleroadams on 24 Apr, 2024 02:28 PM
Screenshots attached.
I've accessed your site and your security performance graph .mxt files - both signed and unsigned - are v1012, at least that's the version given upon trying to install them.
...unless I'm looking in the wrong direction!
8 Posted by Stuart Beesley ... on 24 Apr, 2024 03:13 PM
2. I must have screwed up and not loaded the latest SPG extension build, or something. Will look later.
1. Is a crash related to graphing in Moneyforesight. I’ve reported it onwards.
9 Posted by Stuart Beesley ... on 24 Apr, 2024 03:19 PM
What happens if you use preferences and remove the two moneyforesight views from the summary page, and then save, and restart? Does the security view then work? If not, please upload another console.
10 Posted by soleroadams on 24 Apr, 2024 03:44 PM
Nope...no effect at all.
11 Posted by soleroadams on 24 Apr, 2024 03:46 PM
Console attached.
12 Posted by Stuart Beesley ... on 24 Apr, 2024 03:47 PM
Actually. I’m now wondering if somehow you are picking up the wrong graphing jar, or that it wasn’t installed/bundled correctly as the .setDefaultXXX are the new methods it can’t find?? This would explain why both MD, Moneyforesight and my SPG extension are failing.
Do you have other jars that take precedence in your environment? Can you send a file listing of the jar files in your moneydance app folder?
13 Posted by Stuart Beesley ... on 24 Apr, 2024 03:49 PM
It has to be the JFreeXXX jar libraries. Somehow you are accessing the wrong one?
Support Staff 14 Posted by Sean Reilly on 24 Apr, 2024 03:53 PM
Hello,
As Stuart mentioned, it seems that the graphing libraries that moneydance is using are incorrect for your installation. Can you list the contents of the "lib" folder under the directory where Moneydance is installed (usually c:\Program Files\Moneydance) and let me know which files are present that start with "jfree"?
Thanks!
Sean
--
Sean Reilly
Developer, The Infinite Kind
https://infinitekind.com
15 Posted by Stuart Beesley ... on 24 Apr, 2024 03:59 PM
I believe the current one is probably:
jfreechart-1.5.4.jar
So the directory listing will be helpful.
I wonder if a recent install failed to delete the old one (with a different name)?
16 Posted by soleroadams on 24 Apr, 2024 04:06 PM
jfreechart-1.5.4 is one and the other is jfreechart-1.0.13
Support Staff 17 Posted by Sean Reilly on 24 Apr, 2024 04:07 PM
that explains it! The jfreechart-1.0.13 shouldn't be there. I would recommend uninstalling moneydance, making sure the ProgramFiles \ Moneydance folder is completely gone (or renamed) and then install a fresh version.
Thanks,
Sean
--
Sean Reilly
Developer, The Infinite Kind
https://infinitekind.com
18 Posted by Stuart Beesley ... on 24 Apr, 2024 04:15 PM
That will also fix SPG
19 Posted by soleroadams on 24 Apr, 2024 04:25 PM
That seems to have done the trick.
Thank-you Stuart and Sean.
Neil
20 Posted by Stuart Beesley ... on 26 Apr, 2024 05:58 AM
… we would be interested to hear what your old version was before upgrade, and whether you had any install/upgrade issues, and in fact how you normally install/upgrade?
Thanks.
21 Posted by soleroadams on 26 Apr, 2024 08:49 AM
I was using 2022.6 (4097) prior to up-grading to 2024 and that version worked extremely well for me (as have most versions actually).
I haven't experienced any upgrade issues in the past prior to this particular problem.
I always use the win64 file available from the download page and follow the instructions. I don't have any other programs open when performing the install.
For what it's worth, I think this is just a glitch and I shouldn't be concerned about any inherent issues you feel may have been responsible for this issue.
System closed this discussion on 26 Jul, 2024 08:50 AM.