Another thought related to this...
If these 30 or so widgets are all displayed at once, there's probably
not much to do except optimize the layout and video driver code. If
this is in a scrolling box though, and only some of these widgets are
actually on screen, there may be some scrolling/clip
okan wrote:
>
> Answers:
> - Our video driver is EZ328,
> - 2 BPPs
> - using no theme,
> - CPU freq. is as you thought ,32 MHz,
> - and socket type is UNIX type,
>
> I need your helps.Thanks anyway...
sorry for the delay.
Using 1 BPP may help a little:
1) less memory to handle, gfx routin
Answers:
- Our video driver is EZ328,
- 2 BPPs
- using no theme,
- CPU freq. is as you thought ,32 MHz,
- and socket type is UNIX type,
I need your helps.Thanks anyway...
Pascal Bauermeister wrote:
> okan wrote:
> >
> > Hi all,
> > I'm developing a project on MC68VZ328 ,that has so muc
okan wrote:
>
> Hi all,
> I'm developing a project on MC68VZ328 ,that has so much windows and
> widgets in it.And when I open a window(there is no any bitmap in it,but
> approximately 30-35 widgets(boxes,buttons,fields etc)),it is shown 4-5
> sec.s after I 've clicked the to open it.My questi
Hi all,
I'm developing a project on MC68VZ328 ,that has so much windows and
widgets in it.And when I open a window(there is no any bitmap in it,but
approximately 30-35 widgets(boxes,buttons,fields etc)),it is shown 4-5
sec.s after I 've clicked the to open it.My question is ; is it normal
on t
