Re: [Amelia-development] UI StyleSheet Stuff

[Joao P. <jpp...@lb...>]

Karol,

Before answering your questions, I'd like to inform you that the 
transition to the new data model (different classes and node types for 
different track types) is complete. The old functionalities like pT 
cutoff and track selection are again in place. This will be committed in 
minutes.

Tomorrow I'll work on the physics, after having done a full revision on 
adding 4-vectors today.

>
> 1) The background of the geometry.ui is currently a 1024x730 image,
> which does not get scaled. However our window is 1024x730, which
> includes the toolbar and menubar, so the background does not really
> work. That is why the Designer form does not look correct, because the
> size of the central widget is not 1024x730, but less... It used to
> work in Ameila though, because when we loaded geometry.ui, the central
> widget was automatically resized to 1024x730 (thus the window was even
> bigger). However if I try my new method, the central widget is no
> longer resized, so it looks like it would in the Designer (see
> dynqt-widget).
>
> I think that one solution would be to either make the entire window
> bigger than 1024x730 (so that the central widget is 1024x730 when we
> add the toolbars) or make the background smaller. The problem with the
> latter solution is that it greatly reduces the real-estate that we
> have available. What do you think?
>   
I'll play with that tomorrow. But it seems OK as seen in Designer.
We can not spoil real-estate indeed, and I also don't like the idea of 
making the window bigger since some people still have screen resolution 
of 1024x768. And with border, menu bar and frame that's exactly the size 
I have right now.
Unless we reposition the toolbar manually on the code... Will try that 
tomorrow and then let you know.
> 2) As I mentioned before, using border-image for a background image is
> not very efficient, so when I run my sliding animation there is a lot
> of choppiness. If I replace all border-images with background-images,
> the performance improves greatly. There are several places that I
> think we should be able to do this, because all border-images does is
> automatic scaling. However certain widgets will not be resized (ei:
> background of the tabwidget, the selected track info tool). So would
> it be possible to use a background-image instead of a border-image for
> those?
>
>   
It is possible of course. I'll do it tomorrow. The problem is there will 
be no automatic resizing so we should have background images oversized 
by default (or in a fixed size we won't allow to change)
Now the tab handles would have to be of a fixed size... Will study this 
problem tomorrow.

Cheers,

Joao