You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue page is meant for keeping track of all issues found in the ROOT experimental eve7 component. This issue will remain open until a "stable enough" version of eve7 will be provided.
1. Bugs
General
Can't work without internet connexion. Can't load openui.
No interaction with geometry scene at all. A menu like the settings in the geom viewer would be nice
Will be added soon
Left menu
After opening one event data collection and clicked on edit, a menu shows up down to edit the collection attributes (Rndr self, children, color, ...). Would be nice to add a close button to this menu
Left menu context menu:
Render only selected
Render all except selected
Render all
Render none
Feature request: left-click on element, highlight element on scene if rendered
In general the font size is too big. The mount of information shown in the left menu is not enough. The standard TEveManager had a nice vertical text spacing.
Dirty hack: CTRL+ - to reduce the font size
The sub EveElement indent is not enough. For example, on the picture below, the indent before Particle 0 in the sub list of PandoraPFOs is not enough. It's a bit hard to see which element belongs to which parent element.
Add check box instead of "pen icon". Check/uncheck to render/un-render the element in the scene. Even maybe with a three state: all rendered, not rendered, partially rendered (children).
Add an element color in the tree view. For example I want particles to be in red, tracks in violet and clusters in blue in the tree view
Event scene
Can't interact with drawn geometry in eve7 (picking, highlighting, etc ...)
Context menu:
"Reveal in tree view": Shows the element in the left menu
Select a point/object to center on for the camera
C++ interface
The TEveBoxSet class was really useful and was lost in translation (maybe on purpose?). It allowed us for example to set different hit size and colors for a cluster having hits in the ECAL and the HCAL.
Will be added soon again
I found the C++ interface a bit old style and confusing.
The memory management is not really clear. I see some RefCount methods dandling around, some pointers passed in methods that doesn't require a pointer to be passed, a (const) reference sometimes being more than enough.
A lot of ROOT old style inheritance from multiple classes make it really hard to address my implementation.
REveElement is a HUUUUUGE class like some other ones and the interface can be significantly reduced by using composition and "separation of concerns" principle.
Again separation would make the interfaces more clear. I found that the objects data (tracks, point sets, etc...) are not enough decoupled from the rest of the framework. A bit like TH1 and TCanvas with the Draw method
3. Nice features
Event scene
Navigation with the mouse is nice
4. Questions / HOWTO
How to setup a fixed url for deployment ? Currently the port is changing all the time. Also a key is generated on the fly every time on startup and is part of the URL.
This issue page is meant for keeping track of all issues found in the ROOT experimental eve7 component. This issue will remain open until a "stable enough" version of eve7 will be provided.
1. Bugs
General
Left menu
>not showing up after first event loaded. Fine with next eventEvent scene
kDasheddoes not render as dashed on display. Any other value too. Always renders as plain line.2. Feature requests
General
Left menu
CTRL+ -to reduce the font sizeParticle 0in the sub list ofPandoraPFOsis not enough. It's a bit hard to see which element belongs to which parent element.Event scene
C++ interface
RefCountmethods dandling around, some pointers passed in methods that doesn't require a pointer to be passed, a (const) reference sometimes being more than enough.TH1andTCanvaswith the Draw method3. Nice features
Event scene
4. Questions / HOWTO