I was wondering if anyone else is haveing the same problem with webclient 3 that I am having:
Some controls such as buttons and icons do not display on screens when using webclient. The problem is not with all controls because some of the buttons and some of the icons appear and other don't.
When viewed through the regular proi-iv client this doesn't happen. All controls appear as normal
Windows Kernel 5.5 r411
Client 5.6.5.0
WebClient 3

Webclient 3 Dropping screen elements
Started by Dan Shreeve, May 12 2005 05:28 PM
4 replies to this topic
#2
Posted 12 May 2005 - 06:45 PM
Dan,
Complete shot in the dark:
Is it possible that your disappearing features as based on a location that is too far over to the right or too far down the screen?
If so, you may need to mess with the XY declarations for Web Client. (This is if they are still the same as they were for 1.0 and 2.0)
Regards,
Joseph
Complete shot in the dark:
Is it possible that your disappearing features as based on a location that is too far over to the right or too far down the screen?
If so, you may need to mess with the XY declarations for Web Client. (This is if they are still the same as they were for 1.0 and 2.0)
Regards,
Joseph
#4
Posted 12 May 2005 - 09:25 PM
Dan,
Ok that's bizarre. Is there anything unusual about either the field defs or screen formats? Do all of your icons have an explicitly declared height and width?
I did see a 5.5 issue recently where if you had a series of items declared in a screen format and the last item was an icon located on the left side of the screen, without GUI width declarations), the remainder of the screen on that row was blanked out. (sorry for th run on)
Regards,
Joseph
Ok that's bizarre. Is there anything unusual about either the field defs or screen formats? Do all of your icons have an explicitly declared height and width?
I did see a 5.5 issue recently where if you had a series of items declared in a screen format and the last item was an icon located on the left side of the screen, without GUI width declarations), the remainder of the screen on that row was blanked out. (sorry for th run on)
Regards,
Joseph
Reply to this topic

0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users