Hello All,
After a recent update to Tessitura 15.1 (Version: 15.1.5.55335, Build 583) we've begun seeing a problem with the Tessitura Client (one which I cannot find Documentation or Forum posts about).
Whenever the Tessitura Client "login" screen is being drawn (for example, after the user selects the "ReLogin" menu item), it is being placed outside the bounds of the monitor.
Using the windows ALT+Spacebar shortcut allows us to bring up the menu to "move" the window back on-screen; but the system reverts to the off-screen location the next time this window pops up.
Is there an INI file setting we might be able to adjust, to ensure the Login Window is placed within the bounds of the standard Desktop / monitor coordinates?
Anyone else have a bright idea on how to fix this problem?
Thanks!
--Noel
P.S. I should also mention that the "Loading" window with its progress bar appears to be getting placed off-screen as well)
We have seen behavior like what you describe with RAMP Citrix. (Tessitura 15.0.4 & 15.1.4)
Your ALT+Spacebar temporary solution is very cleaver.
You do not say if you are on RAMP or not. If you are on RAMP (therefor Citrix is involved) put in a support ticket there is an INI file that the support folks can work on to resolve the problem for a while. We believe that this may be related to having 2 monitors on a laptop and unplugging one monitor while the Tessitura Application is up and running. We have also seen some improvement by upgrading the Citrix Client. I'm currently running on my Mac. Our PCs have also seen some benefits in upgrading the Citrix Client.
If you are not on RAMP/Citrix. This is also a very interesting symptom. Again well worth a support ticket. However, my responses above are likely not related to your issue.
Noel -
Daniel's suggestion is what we also found. During one upgrade, the tessitura.ini file got modified for someone with multiple monitors, and that ini file got copied down for everyone. Rather than deleting the lines with x and y, we set them with low values, spread that version around the network, and the problem went away. Now that I look at it, they seem to have negative values! In any case, it works.
[Frame]State=MaximizedScaling=100Width=5925Height=4000X=-37Y=-32
Clarke