TITLE UPDATES FAIL IN STYLE DASH 3 UPDATE
TITLE UPDATES FAIL IN STYLE DASH 3 CODE

Based on your description, is it fair to say: I may try and pick this up again later to see if I can make it more robust. I don’t think this will do what I am wanting to for this project. I had to restart the kernel every time I wanted to make updates. Also, this wouldn’t allow me to use Ctl - C to stop it. So once I run a certain file, that is the file I am running I guess.

TITLE UPDATES FAIL IN STYLE DASH 3 CODE

When I ran the dropdown file it like that, it ran fine and updated with whatever code I entered.

TITLE UPDATES FAIL IN STYLE DASH 3 UPDATE

You did give me an idea though, I copied and pasted the code from the update graph file, and pasted in over the dropdown file. Nothing would update the web browser portion. I would refresh, delete history, delete web cache. When I would save this second file, and run it from IPython, it would indicate that it was running at 127.0.0:8050, but not matter what I did, my browser wouldn’t pick it up. Return create_time_series(dff, axis_type, yaxis_column_name) )ĭef update_x_timeseries(hoverData, yaxis_column_name, axis_type):ĭff = df = hoverData]ĭff = dff = yaxis_column_name] Return create_time_series(dff, axis_type, 'figure'), '.format(country_name, xaxis_column_name) So, what I was doing was saving a file ‘dash_dropdown.py’: # -*- coding: utf-8 -*. In this case dash is not “watching” and you’ll have to kill the process and restart to show changes. Refreshing the page still shows the scatter plot, even though the file now contains the component example.

When I undid my delete/paste to get back to the components example and saved, I did not get the terminal output about Restarting with stat because the first app launched didn’t enable the debugger. When I Ctrl-c to kill my running server, then restart with python test-app.py, I get the scatter plot again (current contents of my file). This is what provides the instant restart of the server upon a file change.

note that the second example does not feature the debug=T arg to app.run_server().

It won’t reload itself (at least without doing something to make that happen in the code)

as far as I know, you will need to reload the page to see the new app.

Hopefully that helps a little bit? Without more details, I’m guessing, but the only things that come to mind are:

when I Ctrl-R on the screen, the component example is gone and I have the scatter plot.

* Detected change in '/path/to/dash-reload-test/test-app.py', reloading

upon saving, I get this in the terminal (still running):.

I then deleted the contents of my file, pasting in the second example from here (multi-colored scatter plot).

opened a terminal and went to the directory, then did python test-app.py.

created a file, test-app.py, pasted in this components example, saved file.

I don’t have this editor, but I did an example like so:

I’m just going by when you say you “load one” and then say that you copied it into your editor and chose run. I’m guessing, for example, that you are wondering why it didn’t reload on the fly when you pasted it into your editor? A reproducible example would help a lot, with very clear instructions on the actual code you used (with links so others can try), what steps you’re doing, what you expected, and what actually happened.

Title updates fail in style dash 3