I just managed to read Thomas post on stackoverflow citation. Yes, it covers,
exactly what I found. This would have help if I would have found earlier.
@Ben:As I said, it's nice to see such implementation but it's offside the task
and offside the suggested components to use. It doesn't cover the issues I had
to deal with. I am not disregarding it! But if you have to use a gui built with
Qt Designer to decouple gui design which might be given as task to someone else
so you can focus on implementing the functional parts, and somewhat later,
someone shall improve the design, this way of creating things has the advantage
that proceeding the work, if one stops working for the project, is as easy as
it should be.You can split the work to gain more development speed, which is an
advantage, too. Keeping the functional part away from the gui itself, enables
one to improve the design without touching the functional code and without
changing it's revision number if version control systems are used. Code
recycling is a third one. I don't see any drawback, yet, if you don't take into
account that they may be something missing in the additional libraries and the
gab might cause problems not solvable.But that's not the topic of this thread.
Yes, Qt Designer just provides only the framework, which than can be filled
with content, for example, coming from matplotlib. Having just a dummy widget
to fill as interface pays respect to being most flexible.
No, having to re-initiate the mouse because it is disabled from matplotlib due
to an empty canvas is not wrong but a design decision. One could have easily
decided to not disable it, but the ones who wrote that part might have thought,
that if the canvas is empty,you don't need axes to rotate. They discovered that
this thoughts lead to problems and build a workaround enabling to switch it on
again, rather than change the default. That's ok for me, because it was there
decision. I would have like to find any hint about that in books, tutorials or
stuff like that, but that seems to be a not that often regarded problem.
I took your objection about adding the axis before the canvas is build and
changed the code so after creating the figure I'm adding it to the canvas so it
won't be empty anymore. This is a better way and is avoiding the mouse
issue.Yes, it's clear now, but that is what I asked for in the first place. I
mentioned that there may be something out of correct order. Now we know what it
was and I fixed it.
I like this kind of discussion which clarify the understanding, because you can
get them from books. So thank you very much for the talk.
I think I'm going to review the part where all the figures are created and will
put them into a method which builds them if needed. That would clean up the
design and the code, too.But that's something for after the deadline, for which
the code can be as ugly as it is. It just has to work to get my job contract
renewed.
cheers,Christian
--
"A little learning never caused anyone's head to explode!"
"Ein wenig Lernen hat noch niemandens Kopf zum Explodieren gebracht!"
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
