Topic: screensize reactor

[Bobb]

All,

New to your forum.  Just went searching for the capability in the subject.

I've discovered that some system variables cannot be used with reactors, and SCREENSIZE is one of those.  I have managed to set a reactor to the USERS(1-5) systems variables.  So, the question is, what would be the best option for updating one of the USERS variables on a timer, say every 1/4 second, with the values in SCREENSIZE that can be run in the background 100% of the time without affecting other routines like LISP and/or other scripting?

Or, am I plain old loony, and this can indeed be accomplished with LISP??

Thanks

bobb

[BlackBox]

Welcome to TheSwamp!

Without your code, I'm not sure that I can follow what you're doing with ScreenSize / UserS* System Variables.

You're not 'loony' but perhaps just new(-ish) to the API... Perhaps if you could clarify what it is exactly that you're attempting to do, as there may be alternatives that would preclude the need to have a constant timer running at all (tabling feasibility for the moment).

[Lee Mac]

Welcome to the Swamp Bobb!

Since the vlr-sysvar-reactor can only monitor the values of certain System Variables, an alternative approach might be to use a different reactor type that will be triggered relatively often (such as a vlr-command-reactor or vlr-mouse-reactor), and store the value of the SCREENSIZE System Variable when the callback function is evaluated.

I am curious however as to the application for this?

[TheMaster]

All,

New to your forum.  Just went searching for the capability in the subject.

I've discovered that some system variables cannot be used with reactors, and SCREENSIZE is one of those.  I have managed to set a reactor to the USERS(1-5) systems variables.  So, the question is, what would be the best option for updating one of the USERS variables on a timer, say every 1/4 second, with the values in SCREENSIZE that can be run in the background 100% of the time without affecting other routines like LISP and/or other scripting?

Or, am I plain old loony, and this can indeed be accomplished with LISP??

Thanks

bobb

Have you tried using vlr-Window-Reactor ?

[Lee Mac]

Have you tried using vlr-Window-Reactor ?

Nice idea Tony; however unfortunately this reactor only fires when the drawing window frame or application window frame is moved or resized (returning T or nil respectively for each action). Zooming or panning within the window frame goes unnoticed by the reactor

[roy_043]

@ Lee Mac:
Actually Tony's suggestion is correct. Zooming and panning do not change the screensize (= size in pixels).
Although in BricsCAD the reactor seems to fire before the window is changed.

If you want to catch zooming and panning you can use vlr-acdb-reactor. See:
http://www.theswamp.org/index.php?topic=43408.0

[Lee Mac]

@ Lee Mac:
Actually Tony's suggestion is correct. Zooming and panning do not change the screensize (= size in pixels).
Although in BricsCAD the reactor seems to fire before the window is changed.

My apologies, you are absolutely correct - for some reason I was sidetracked into thinking the OP was looking for a reactor to fire when the zoom magnification was altered, but after re-reading the first post I realise the OP was referring to the SCREENSIZE system variable (dependent on window size) rather than the VIEWSIZE system variable (dependent on zoom); thanks roy.

[TheMaster]

Have you tried using vlr-Window-Reactor ?

Nice idea Tony; however unfortunately this reactor only fires when the drawing window frame or application window frame is moved or resized (returning T or nil respectively for each action). Zooming or panning within the window frame goes unnoticed by the reactor

Yes, SCREENSIZE is the size of the document view window's client rectangle, it's not the size of the virtual screen or anything that would be affected by ZOOM or PAN.

[Lee Mac]

Yes, SCREENSIZE is the size of the document view window's client rectangle, it's not the size of the virtual screen or anything that would be affected by ZOOM or PAN.

Thanks Tony, I realised my mistake.

[TheMaster]

@ Lee Mac:
Actually Tony's suggestion is correct. Zooming and panning do not change the screensize (= size in pixels).
Although in BricsCAD the reactor seems to fire before the window is changed.

If you want to catch zooming and panning you can use vlr-acdb-reactor. See:
http://www.theswamp.org/index.php?topic=43408.0

Can't speak for what happens in BricsCAD, but in AutoCAD, there's quite a few reasons why a AcDbViewport or AcDbViewPortTableRecord could be modified, aside from pans/zooms, and I know from experience that detecting transparent pans and zooms is actually quite difficult to do even in ObjectARX.  The native ObjectARX AcEditorReactor has a viewChanged notification (which fires for pans/zooms, and also for viewport and layout switches), but it's not exposed to Visual LISP's :vlr-editor-reactor) :S

[roy_043]

@ TT:
You are right that a AcDbViewport or AcDbViewPortTableRecord can be changed without panning or zooming. These objects will, for example, also change if you toggle the grid. So you will need additional code to detect if a pan or zoom has in fact occurred. But in BricsCAD ALL zooms and pans are detected (including transparent and real-time zooms and pans).