TiTaNiuM sAMuRai Posted May 30, 2002 Share Posted May 30, 2002 When specifying a colour 65535, 65535, 65535, or 0, 0, 0; will it automatically be corrected for black / white background state? I noticed in 8.5.2 that sometimes a 65535 fill fore would not be switched to 0 during runtime if I have a black bg. 9.5.1 does a switch, or must I check that getPrefInt(14) or whatever? Quote Link to comment
TiTaNiuM sAMuRai Posted June 21, 2002 Author Share Posted June 21, 2002 Regens appear to be inconsistent. I have a check to pref #16. Stretching the PIO recalculates for redraw, but doesn't get the right numbers. Moving does get the right numbers before recalculating. What's the deal? Switching between white and black appears to show no consistency. Quote Link to comment
TiTaNiuM sAMuRai Posted June 21, 2002 Author Share Posted June 21, 2002 Let's say I have a LinearObject PIO that's printing white elements (PenFore), since I'm using a black background. The PIO can be reshaped, moved, rotated, or otherwise modified, and still prints correctly (white pen on black background). At some point when I'm drafting, such modifications to this PIO (and all my other ones) will cause it to switch to a black pen.I use my SetPrefInt(16) to FALSE via a menu item, so I get a white background. The incorrect PIO is now white pen against the white background; this makes sense enough. Then I enter the 'Create Plug-in...' dialogue, click 'Done', and all the PIO's are re-executed. The PIO corrects itself, using black pen against the white background. I use my SetPrefInt(16,TRUE) menu item, and the PIO is white pen again. Now: if modification (rotation, etc.) to this PIO caused it to write with a black pen (the background is black now, remember), I wouldn't be all that surprised. However, this is not the case. Re-execution of the PIO script due to moving, rotation, parameter-changing, etc. does not cause the pen white/black flip. Not until a little while later, maybe 20 or so commands down the road. I've tried my PIO with and without a check to see what the GetPrefInt(16) value is -- and compensate for it -- but this has yielded no solution. I'd like to think that there is something I'm doing wrong, instead the result of a VectorScript bug. Quote Link to comment
TiTaNiuM sAMuRai Posted July 16, 2002 Author Share Posted July 16, 2002 It appears as though the GetPref(16) is returning the value as of application launch. If I don't switch backgrounds WHILE drawing, the PIO's are okay. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.