Found a small bug in V10:
When i am using a workspace where the macro's view is in page 2, then close the window and open another workspace where the macro's view is supposed to be in page 1 it still is in page 2, when click again on that workspace the macro view changes to page 1 as its supposed to do. When i don't close the macro view manualy but just click the new workspace it does what its supposed to do.
appearently it was in V9.1 also
bug report V10
Moderator: Moderators
Re: bug report V10
Confirmed. Actually is true for all pageable workspaces.
#65306
#65306
Re: bug report V10
niclights wrote:Confirmed. Actually is true for all pageable workspaces.
#65306
a second (bit more anoying) one:
i cant seem to change the key profile of my bpm master to "tap speed". i can see the option and select it but when i exit the key profile editor it doesnt seem to save the changes
Re: bug report V10
Agreed.
#65307
#65307
Re: bug report V10
Hi,
I'm not certain it's a bug but I try to use the function " save temporary speed " in the edit times menu on a chase, nothing's happening.
I understand the explanation of the manual like this: enter a time value and click on save temporary speed. chap 8.2.2
I have some bugs with the manual sizing of windows in the workspace.
When I open the visualiser the third line in the capture visualiser menu is cut in half.
Manu
I'm not certain it's a bug but I try to use the function " save temporary speed " in the edit times menu on a chase, nothing's happening.
I understand the explanation of the manual like this: enter a time value and click on save temporary speed. chap 8.2.2
I have some bugs with the manual sizing of windows in the workspace.
When I open the visualiser the third line in the capture visualiser menu is cut in half.
Manu
Re: bug report V10
Re. temporary speed with the user setting [Connected View Sets Temporary Chase Speed] chase speeds will revert to their original speed when the show is loaded. [Save Temporary Speed] will cause the new speed to save with the show.
Re. visualiser menu it might be useful to attach a screenshot to demonstrate.
Re. visualiser menu it might be useful to attach a screenshot to demonstrate.
Re: bug report V10
Hi, thank's,
The visualiser menu :
The visualiser menu :
Re: bug report V10
The minimum screen resolution is 1280 x 800 pixels, judging by the resolution of the screenshot I would estimate that your screen is 1366 x 768 pixels which would explain why some of the buttons are being cut off.
Re: bug report V10
You're right, so that's my tactical computer which can't no longer work with titan.
Thank you.
Thank you.
Re: bug report V10
You could try setting the taskbar to auto-hide and maximise the Titan Mobile window to give you a bit more space.
Re: bug report V10
Hi,
On the picture editor of legend, if I open the Keybord entry on the top left, and if i touch a letter or type something with the keyboard of my pc, the keyboard window disappear.
I'm on titan mobile.
On the picture editor of legend, if I open the Keybord entry on the top left, and if i touch a letter or type something with the keyboard of my pc, the keyboard window disappear.
I'm on titan mobile.
Re: bug report V10
Try toggling the Manual Open button to Auto Open. In Manual Open mode the keyboard only opens for picture legends and is closed when entering text legends - this is intended for computers or consoles which have a physical keyboard; in Auto Open mode the keyboard will open automatically for alphanumeric text entry and for picture legends - for consoles without a keyboard.
Who is online
Users browsing this forum: Google [Bot] and 24 guests