I've not noticed a Windows report for this, so here is Windows 7,
high contrast black mode.
I've not done much with Unicon for a while. So I obtained the 12.1.1
binary for Windows for this and I got, running it twice, -- something
I can't cut and paste. OK,
Runtime error 140
File screeninfo.icn line 94
File screeninfo.icn line 94
Window expected
Window expected
Offending value: Offending value: &null &null
Traceback
(())
(()) from line 3 in screeninfo.icn from line 3 in screeninfo.icn
((Object Object
SSccrreeeennIInnffoo_1_1((&null&null,&null&null,&null&null,&null&null,&null&null,&null&null,&null&null,&null&null))fror
((""ddiissppllaayy"")) from line 94 in screeninfo.icn from line 94 in
screeninfo.icn
Yes, it is that repetitive.
I also note that although I am running in high contrast black mode
in Windows 7, the Unicon window comes up with black text on a
white background, (and syntax highlighting colours, of course). It
should probably come up as light on dark in that mode, if it can
detect it. The open file dialogs and font selection dialogs are
correct. Incidentally, the font only affects the program text, not
the GUI controls, which is another access issue that it would be
nice to address. I'm not au fait enough with Windows programming to
contribute to that, sorry.
I'm not sure why cut and past don't seem to work.
HTH
Hugh
On Tue, 28 May 2013, Bruce & Breeanna Rennie wrote:
> To all who can,
>
> I have attached an unicon file which I would appreciate being run to determine
> if it will work on various systems. The file contains a class which is used to
> determine the number of screens available and the specific characteristics of
> each screen.
>
> It uses xrandr on X Windows systems to determine screen characteristics, on
> others it simply uses the Wattrib function with the parameters "display",
> "displaywidth" and "displayheight" to get the characteristics. This will
> probably cause some difficulties on Microsoft Windows machines as it uses the
> assumption of 1 pixel per mm for such systems.
>
> The file contains a procedure main() which will print out the characteristics
> as found.
>
> If anyone knows a better way to determine the correct ratio or how to
> determine the actual screen sizes, I will incorporate it into the class.
>
> regards
>
> Bruce Rennie
>
>
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group
