1 |
Regarding the performance cost:
|
1 |
Regarding the performance cost:
|
2 |
Chili Minimap actually uses engine minimap. It doesn't draw the minimap. If you look at the code it doesn't have any OpenGL call for drawing stuff, instead it only call engine's minimap.
|
2 |
Chili Minimap actually uses engine minimap. It doesn't draw the minimap. If you look at the code it doesn't have any OpenGL call for drawing stuff, instead it only call engine's minimap.
|
3 |
\n
|
3 |
\n
|
4 |
Its really confusing/perplexing on how to make it more efficient than it already is because when you wanted to tweak the widget there's little choice that you have: you either disable engine minimap or enable engine minimap. The chili minimap also didn't draw the border either, it is 100% processed by Chili Framework.
|
4 |
Its really confusing/perplexing on how to make it more efficient than it already is because when you wanted to tweak the widget there's little choice that you have: you either disable engine minimap or enable engine minimap. The chili minimap also didn't draw the border either, it is 100% processed by Chili Framework.
|
5 |
\n
|
5 |
\n
|
6 |
So in conclusion:
|
6 |
So in conclusion:
|
7 |
Chili Minimap is just a shell that call Chili Framework (draw border) and engine minimap (draw minimap), and doesn't process anything on its own. Its an "empty" widget.
|
7 |
Chili Minimap is just a shell that call Chili Framework (draw border) and engine minimap (draw minimap), and doesn't process anything on its own. Its an "empty" widget.
|
|
|
8 |
\n
|
|
|
9 |
People should also test the performance cost if you hiding the Chili Minimap (click on the red docking bar), becuase that's the only time when Chili Minimap do not call for engine's minimap.
|