thanks Alex
I will try to figure out if and how I could apply it to this view
Am 28.11.2016 um 23:26 schrieb Alex Harui:
On 11/28/16, 12:49 PM, "Frank Dahmen" wrote:
this looks like magic :)
I'll try to understand the concept
In fact, it is based on the principles that most professional
I doubt digging in further will be off any general help to anyone. The main
thing is to recognize the problem and know what to do to solve it.
Many thanks for your help,
Doug
--
View this message in context:
http://apache-flex-users.246.n4.nabble.com/Calls-to-superclass-failing-tp14230p142
On 11/28/16, 8:28 PM, "doug777" wrote:
>That was the solution. Everything now works correctly.
>
>When I start to do some new work on an old project I always upgrade it to
>the latest sdk before starting.
>
>I never realized before that there can be hidden changes that affect
>things
>without s
That was the solution. Everything now works correctly.
When I start to do some new work on an old project I always upgrade it to
the latest sdk before starting.
I never realized before that there can be hidden changes that affect things
without showing errors or warnings in the Problems panel.
E
So I ran swfdump and have been studying the results. The module in which this
skin is used created a file with 200,000 lines. From the ABC2 tag to the end
of the section where newclass ViewListingsDataGridSkin is shown there are
about 3000 lines.
I can't see anything in there that looks odd, but t
> you could use the debugger to step into the super.updateDisplayList call
> to make sure no exception gets thrown at that point.
The first line with a warning that gets called in my skin is
super.initializationComplete and stepping into this shows it goes through
various components UIComponent -
On 11/28/16, 12:49 PM, "Frank Dahmen" wrote:
>this looks like magic :)
>
>I'll try to understand the concept
In fact, it is based on the principles that most professional magicians
use, such as illusion. There is probably no requirement in your app to
create, say, 200 UI widgets at the same t
this looks like magic :)
I'll try to understand the concept
thanks
Am 28.11.2016 um 17:29 schrieb Alex Harui:
On 11/28/16, 5:57 AM, "Frank Dahmen" wrote:
that's why I said "magic" not "unpleasant" :)
Fundamentally, if it isn't visible on-screen, don't create it right away.
If you look
On 11/28/16, 5:57 AM, "Frank Dahmen" wrote:
>that's why I said "magic" not "unpleasant" :)
Fundamentally, if it isn't visible on-screen, don't create it right away.
If you look at the FlexStore example here [1]
I've used states and a "prebake" trick to finish up initialization of
off-screen
On 11/28/16, 1:27 AM, "doug777" wrote:
>It's so odd.
>
>This line in ViewListingsDataGridSkin -
>
>super.updateDisplayList(unscaledWidth, unscaledHeight);
>
>has the warning : Call to a possibly undefined method updateDisplayList
>
>How is that possible???
Don't know. Are you getting this err
that's why I said "magic" not "unpleasant" :)
i measured in release mode:
creationcomplete is fired after ca. 3 - 3.5 sec
than the remote request is started and upon result the controls are
"configured"
this takes about 1 - 1.2 sec
I think I leave it as it is, and ask the customer if splitting
It's always a question of requirements, if 5 s is ok for the use case,
then may be it is not worth spending too much time on it.
Unfortunately, the only magic technique than I know when it comes to
increase performance on mobile (for complexes views a least) is to give
up on some of the things
would be over 1px high ;)
but 5 sec. (not in debug mode) is almost ok
it IS huge and there is a lot of stuff going on
I know, spending some days and revise all components (and make it more
complicated) i could lower it 1,2 seconds.. i guess
I thought there are some "magic" techniques, li
I said not always ;-)
can you show a screen capture of the view ?
Le 28/11/2016 à 12:25, Frank Dahmen a écrit :
thanks,
yes, I know, but as you said, not easy
Am 28.11.2016 um 11:46 schrieb Vincent:
Hi,
If it takes 2s on desktop, it is very likely that the process will
cost at least twi
thanks,
yes, I know, but as you said, not easy
Am 28.11.2016 um 11:46 schrieb Vincent:
Hi,
If it takes 2s on desktop, it is very likely that the process will
cost at least twice more on mobile (and probably a lot more on low end
devices)You can set the destructionPolicy property of the Vie
Hi,
If it takes 2s on desktop, it is very likely that the process will cost
at least twice more on mobile (and probably a lot more on low end
devices)You can set the destructionPolicy property of the View to never,
so the view is just created once, the downside is memory consumption.
The onl
It's so odd.
This line in ViewListingsDataGridSkin -
super.updateDisplayList(unscaledWidth, unscaledHeight);
has the warning : Call to a possibly undefined method updateDisplayList
Yet if I control-click on super, SparkSkin pops up where updateDisplayList
is very obviously defined.
How is that
If I create a test case it all works - the skins work fine in all my other
projects.
I've done something to this project that has caused this fault - I was just
looking for some clue as to where the fault might lie. The fault is passed
onto the compiled Release Build as well.
In the particular tr
Thanks,
the view is really, really huge so 2 seconds would be perfect ok
Yes seperate views would work I guess, but when the view is loaded once
its's very fast to use
(fast scrolling etc.)
and when switching between views, the overall "use-time" wouldn't be
better i think
I am an
Hmm, 2 seconds on a desktop is quite slow :-( Perhaps you can create
separate views and load them on demand? Or is the view completely
customizable?
Also, on your device, are you running the release build or debug build?
You could also create sections in the View and as each section becomes
vis
20 matches
Mail list logo
