Swipe gesture performing badly

[SynexusStuart]

Hi All, i have created an active report which has a pie chart on it. this pie chart sits inside a data deck with an iterator.

I have (i think) set it up correctly to work with swipe gestures

I have downloaded the file to my iPad but when I try to use the swipe gesture on the iPad it only works occasionally, basically is seems to be intermittent and somewhat jumpy.

I have downloaded some samples in the cognos mobile app and in these reports, the swipe gestures are smooth and stable.

Can anyone suggest what I can do to improve this?

Stu

[MFGF]

Hi All, i have created an active report which has a pie chart on it. this pie chart sits inside a data deck with an iterator.

I have (i think) set it up correctly to work with swipe gestures

I have downloaded the file to my iPad but when I try to use the swipe gesture on the iPad it only works occasionally, basically is seems to be intermittent and somewhat jumpy.

I have downloaded some samples in the cognos mobile app and in these reports, the swipe gestures are smooth and stable.

Can anyone suggest what I can do to improve this?

Stu

You probably don't want to hear me say this, but I'm guessing you have an old iPad and it's just not up to the job. I have an old iPad 2 and a newer iPad Air. With any reasonable sized report, the iPad 2 suffers the same lagginess you describe here, but the Air is smooth and responds to every gesture.

To give your iPad the best chance of working, remove all other apps from memory and try it with just the Cognos app active. My guess is you will still see sketchy performance and gesture reactions, though.

Cheers!

MF.

[SynexusStuart]

I asked my colleague who has a new iPad Air and it is the same for him.

He is a web developer and he said it looks like it is a problem with having an unfixed width of the element in the report. He was only guessing but it sounds plausible.

I have set the size of the chart and the table cell but it is still acting strangely, any tips on this?

[MFGF]

I asked my colleague who has a new iPad Air and it is the same for him.

He is a web developer and he said it looks like it is a problem with having an unfixed width of the element in the report. He was only guessing but it sounds plausible.

I have set the size of the chart and the table cell but it is still acting strangely, any tips on this?

When writing an active report, I generally size everything explicitly. When you are "swiping", the area your finger can swipe over is directly related to the size of the deck or data deck you have implemented the "Auto horizontal" transition on. This is what you should check first.

Just as a sanity check - how did you implement the swipe? Did you change the interactive behaviour of the deck/data deck so that the variable it reacts to in the Container Select section is also being set in the Set Variable Values section?

Cheers!

MF.

[SynexusStuart]

Thanks MF, I will have a play with the sizing.

Yes, set Variable Values variable is the same as Container select. Like I say, it works, just not well.

[navissar]

I'll add another question - what is the size of the report? A chart inside a data deck makes me suspicious - these tend to grow exponentially, and huge reports will bring even an iPad Air to its knees.

[Milk_Toast]

I had the same thing happen to one of my reports.

. My problem was in a size & overflow properties in one of the blocks in my swipe area. When I checked Always use scrollbars it would be really sluggish when I changed it to  Use scrollbars only when necessary it was nice and smooth as expected. Maybe try and see if you change that it performs better.

[SynexusStuart]

I'll add another question - what is the size of the report? A chart inside a data deck makes me suspicious - these tend to grow exponentially, and huge reports will bring even an iPad Air to its knees.

It's <2MB and stable at that. we've actually redesigned it slightly so that the chart is not in a data deck, purely for aesthetics and not for performance reasons.

The chart was not going to grow as it was only ever showing a finite number of members and a limited date range.