M
Michael Kaciuba
Good Afternoon. I am seeking advice on a terminal server
graphical error. We are currently in the process of
developing some software with out of the box .NET
developer applications, for use not only internally but
also externally via Microsoft Terminal Services.
Here's the story. The application incorporates a 16 bit
colour scheme. This is displayed with some background
graphics and basic text highlighting.
Running on a system with desktop settings as 16 bit - High
Colour, we have encountered no problems. Connecting to our
terminal servers, via Citrix ICA, with a 16 bit session,
we have encountered no problems. However, we would like to
be able to use Microsoft Terminal Server Client to connect
to our terminal servers. As you know, MSTSC only supports
256 colours, so connecting via this program translates 16
bit colour to 256 colours. This is evident with the
graphical changes on the background picture and the text
highlighting.
Our problem is this: Within our software we are opening
and closing windows. For example, you search on a client
and are presented with a list of policies. You double
click a policy and an information window opens up ontop of
the search window. All is normal and as expected at this
point. Its when you close the policy window that we have
the problem. When you close the window, the pallet has
changed and different colours are appearing, making text
unreadable.
From here the pallet seems different until i double click
the title bar of the application, or i minimise then
restore the application or minimise then maximise the
application. Clicking the restore button then the maximise
button (at the top right of the app) will revive the
pallet. Also, doing something outside of the application
like going to the start menu, will also revive the pallet.
It seems like to me that there is a problem with the
terminal server translation from 16 bit colour to the 256
colour scheme, or something to do with the terminal server
not redrawing the application properly. Can anyone help?
Can anyone tell me why this is happening? Whats causing it
and how can we get around it without having to redraw the
application in 256 colours?
A few things to note...
- We are connecting via LAN to a Windows 2000 Terminal
Server (SP3) from a Windows 2000 Professional Desktop
(SP2) via Microsoft Terminal Server Client (v 5.00 build
2195).
- Both desktops are set at 16 bit - High Colour.
- We have connected via Citrix ICA with a 16 bit session
and had no problems.
- We are using nothing but out of the box .NET developer
applications.
- We have disabled desktop wallpapers and changed colour
schemes, both have had no effect.
- The colours we are having problems with are not in the
256 colour scheme.
Any help appreciated. Thankyou for your time.
Michael Kaciuba
(e-mail address removed)
graphical error. We are currently in the process of
developing some software with out of the box .NET
developer applications, for use not only internally but
also externally via Microsoft Terminal Services.
Here's the story. The application incorporates a 16 bit
colour scheme. This is displayed with some background
graphics and basic text highlighting.
Running on a system with desktop settings as 16 bit - High
Colour, we have encountered no problems. Connecting to our
terminal servers, via Citrix ICA, with a 16 bit session,
we have encountered no problems. However, we would like to
be able to use Microsoft Terminal Server Client to connect
to our terminal servers. As you know, MSTSC only supports
256 colours, so connecting via this program translates 16
bit colour to 256 colours. This is evident with the
graphical changes on the background picture and the text
highlighting.
Our problem is this: Within our software we are opening
and closing windows. For example, you search on a client
and are presented with a list of policies. You double
click a policy and an information window opens up ontop of
the search window. All is normal and as expected at this
point. Its when you close the policy window that we have
the problem. When you close the window, the pallet has
changed and different colours are appearing, making text
unreadable.
From here the pallet seems different until i double click
the title bar of the application, or i minimise then
restore the application or minimise then maximise the
application. Clicking the restore button then the maximise
button (at the top right of the app) will revive the
pallet. Also, doing something outside of the application
like going to the start menu, will also revive the pallet.
It seems like to me that there is a problem with the
terminal server translation from 16 bit colour to the 256
colour scheme, or something to do with the terminal server
not redrawing the application properly. Can anyone help?
Can anyone tell me why this is happening? Whats causing it
and how can we get around it without having to redraw the
application in 256 colours?
A few things to note...
- We are connecting via LAN to a Windows 2000 Terminal
Server (SP3) from a Windows 2000 Professional Desktop
(SP2) via Microsoft Terminal Server Client (v 5.00 build
2195).
- Both desktops are set at 16 bit - High Colour.
- We have connected via Citrix ICA with a 16 bit session
and had no problems.
- We are using nothing but out of the box .NET developer
applications.
- We have disabled desktop wallpapers and changed colour
schemes, both have had no effect.
- The colours we are having problems with are not in the
256 colour scheme.
Any help appreciated. Thankyou for your time.
Michael Kaciuba
(e-mail address removed)