Another Surprising Discovery About VLISP

As I begin to build more code, I am finding that things like OSMODE, OSNAP, PICKBOX, etc...all seem to have an affect when you're telling your VLISP code to pick exact points. I just now discovered that the zoom level also affects this. I have a code which runs great if the zoom all is set. But I just ran it and zoom was not as it was before, and the code ran into problems trying to pick the points I am telling it to work to.

I guess I could open up the program with a zoom all command, but is there a trick to basically turn off the system variables which are causing VLISP to behave differently. And what, besides OSNAP, OSMODE and PICKBOX would those other variables be?

I know this sounds chaotic, but remember I am working on projects which are to totally automate the drawings process with absolutely no user input whatsoever.

When using ssget with automatica on-screen selection modes (Window / Crossing / WP / CP etc.) objects won't be selected (even if they lie within the selection boundary) unless they are visible on-screen.

The behaviour differs from what is expected when selecting blocks too, as this example demonstrates.

Aha....I see said the blind man....actually, you'd think I would have known that but VLISP is working so well for me I think it can work miracles. So I just inserted a zoom all at the proper place just before I start the selections and viola...its back to working now.

This code is going to drive me to drink...even more! I'll have to remember this too when I start inserting blocks, although there I don't think I'm going to be doing much ssgetting....it will all be hard points.

Had the same problem with a wall clean up routine found it would work at some zoom scales but not others bang the head against the wall why is not working, the way around it was to zoom to a preset scale which always worked then return back. In nearly all my routines at start is get osnap settings change to something needed at end change back.