Vanishing objects in desktop client

[#1]

Hi there,

our users are facing a strange problem: sheet objects (text boxes, buttons, list boxes, charts...) vanish from the sheet when the application is opened in the desktop client. If for example entries in a listbox are selected about half of the other objects on a sheet disappear.

To make them appear the users have to click on the title of one of the existing objects or in the background of a gauge or a text object.

Please see attached picture for details. on the leftyou see what it should look like and on the right what it looks like when something is selected.

At first I thought about a problem with their graphics board but I am facing the same problem now. Plus this only occurs with one application, we never had this problem with any other application.

The application is rather small (filesize 8,5MB) and the data structure is not complex (checked that with the Governance Dashboard).

We are using QV 11.0.11440 SR2.

We never see this problem while opening the application via the Internet Explorer. It only comes up when the application is opened in the desktop client. Here we can open via "open in server" or simply via "open". Both ways lead to vanishing objects.

Did someone ever experience this behavior? I have no clue how to solve that problem.

Thanks and best regards,

Chris

[#2]

Ok, I think I found something.

The problem only occurs after switching between the sheets. If I stay on the first sheet there is no way I can make objects disappear. No matter what I do.

I will check if there may be any issue with the performance as you suggested and will remove all the triggers we have for "OnActivateSheet".

Thanks a lot so far

[stevedark]

As a rule I avoid triggers wherever possible - as they cause the app to do

things that the user may not be expecting. My preference would always be

to have a button (ie. a text box with a set of Actions) to apply default

state for a tab - so the user can chose if they want to apply those

settings.

Perhaps not directly related to your problem, but I thought I would

share....

- Steve

[#4]

I could find the reason now. I removed all triggers but it is still possible to use buttons to fit the zoom to the resolution of the screen.

As soon as on of the sheets does not have the original zoom objects start to vanish from the sheet.

If all sheets have the original zoom everything is fine.

We use macros to fit the zoom to the screen. Is there any other way to achieve this "fit zoom to window", maybe with actions? I would like to keep the possibility to adjust the zoom level at least with a button.

Here are our macros for original size and fit to window:

sub FitZoom100

ActiveDocument.GetApplication.WaitForIdle
set mysheet=ActiveDocument.ActiveSheet
set sp=mysheet.GetProperties
sp.ZoomFactor = 1
mysheet.SetProperties sp

ActiveDocument.GetApplication.WaitForIdle

end sub

sub FitZoomToWindow

ActiveDocument.GetApplication.WaitForIdle
ActiveDocument.ActiveSheet.FitZoomToWindow
ActiveDocument.GetApplication.WaitForIdle

end sub

Not sure if there is anything wrong with them?

Thanks and BR,

Chris

[stevedark]

Using the zoom within QlikView is also something I try to avoid. With the

Ajax client using the browsers built in zoom sometimes gives okay results.

What I have done in the past is picked up what machine a document is

running on and shown extra content if it was not ones of the machines I

knew had a lower resolution screen.

I'm sure you will find what others have done for zooming sheets if you look

on the community - but as I don't do it it's not something I can help with.

Sorry!

Steve

DirectorQuick Intelligence

www.quickintelligence.co.uk

07767 472906

[#6 · Accepted solution]

At the end of the day there is "light at the end of the tunnel" as we say in german

Triggers were no problem but it was the resizing itself.

Working with the original resolution worked fine but as soon as you changed it (not matter if you did with macros or by clicking on View - Fit Zoom To Window) objects started to disappear after making selections or click on buttons.

Changing the resolution back to the original solution fixed the problem.

To be able to still provide the FitZoomToWindow-function I created a transparent textbox with a show conditional:

=if(Even(Second(time(now()))),0,1)

The textbox is shown if the current second is odd and hidden if it is even.

By switching the textbox "on and off" the vanished objects come back to life as it immitates the user cliking somewhere.

In the worst case the user has to wait nearly a second but usually it is not taking that long.

I was trying to switch it for example every 0.5 seconds but I could not get the milliseconds.

I guess that is not possible.

However, at least I found a workaround for that. Maybe I can think of a better solution but this gives us the chance to go on like before for the time being.

Thanks for your help,

Chris

[stevedark]

I would be wary of using now() in that way, as it could be a bit of a resource hog.  If it seems to be working for you though then perhaps best to leave it be.