Re: [Amelia-development] UI StyleSheet Stuff

[Karol K. <kk...@gm...>]

On Thu, Oct 16, 2008 at 9:08 PM, Joao Pequenao <jpp...@lb...> wrote:
> 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.
>
I just saw the commit. I'll take a full look at the new data model
tomorrow to see it in it's full glory (so far I've just seen diffs
produced by svn).

> Tomorrow I'll work on the physics, after having done a full revision on
> adding 4-vectors today.
>
Heh, I am looking forward to seeing how the tracks are supposed to look like. :P

>>
>> 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.
Ah, but in the geometry.ui file it is only 1024x730 and NOT 1024x768
as it should be (as I understand from your reply). So yeah, if we
increase the window size (not the central widget) to 1024x768,
everything should be alright.

> 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)
I think fixed size would be the easiest solution.

> Now the tab handles would have to be of a fixed size... Will study this
> problem tomorrow.
>

Also there is currently a thread on the Qt mailing list about
animating a bunch of images in a QGraphicsView and performance that I
am following. Some points that were brought up include using the time
passed since last update in figuring out the next position (like done
by our Irrlicht animators) because QTimer cannot be trusted to provide
a constant tick signal. Also due the same problem, it was also
suggested to use an alternate thread for handling the position
updates. I will explore these possibilities over the weekend...

Anyways, I have integrated the code I have so far for the transitions
between layouts into AMELIA and it seems to work pretty well. I will
commit it now. However I have not tested it as much, so let me know if
you run into any problems. Also there is a few things that I want to
change in the way it changes the toolbars and menubars. Let me know if
you have any other suggestions.

Cheers,
Karol Krizka