SamIWas

I've never had enough document context scripts to find out. But I used to have like 150 scripts in my object context menu all broken down into sub-menus. Now, If I get even a few dozen in there, it starts to fail. I've mentioned it several times to VW, but it has never been fixed. Also, I should clarify...the workspace itself does not become corrupted. But the scripts in the object context menu become wonky. Some will work, some won't work at all, and others will run completely unrelated scripts.

The problem is that the workspace becomes corrupted if you add too many commands to the "object context menu", and has since like VW2011. I used to have a massive trove of scripts in my user context menu, but now I'm afraid to load too many in, because it corrupts everything and I have to start over. So many things I could speed up by having that option. And I still wish they'd upgrade the keyboard shortcut system so that I could make much better use of my scripts from the mouse or StreamDeck.

Never mind...restarted everything over again, and now everything is lightning fast and no more random errors. Weird. EDIT: Nope...I spoke too soon. Once I update the script I was working on to event-enabled, I started getting errors from other scripts again. Are the constant IDs global and clashing maybe? Do the constant ID numbers have to be unique amongst different plug-ins?

This just started a few days ago... Every time I exit the Plug-In manager after updating a script, several other random scripts report errors in compiling. If I go to the scripts themselves, they compile just fine. But as soon as I exit the manager, I get three pop-up windows saying there are errors, mostly "Identifier not declared" when it definitely is. I even tried removing those tools from my workspace for now just so I could not have the popups every time, but they persist. It's driving me insane because it adds an extra ten seconds every time I exit the plug-in manager having to click OK on all of the warnings, which is a lot when I'm testing scripts. I've also noticed that compiling scripts seems to have slowed down considerably in the last couple of days, coinciding with these errors appearing. Done a restart and restarted the computer, to no avail. Has anyone ever run into this and might know a solution?

Yeah, I've done a bit of that with bigger poly blocks, but with a mixture of dimensions, sweep definitions, and rotate calls throughout, I can't do it to large parts at a time. This post was mostly just to bitch. I know it was my own doing and that there's no clear easy way out. 😬

Going through an existing script and adding a " to every length dimension. I built all my plug-ins just using numbers without a dimension mark (because when I started, I didn't even think about it and it just worked and I never updated my thinking). And now I have to go back and add that dimension mark to tens of thousands of lines of code, with multiple dimensions on each line. Ugh...I'm going to be here until I retire!

Do you keep the same sheet layer viewports for all your drawings, or are you creating new viewports each time? Because you can override class settings in each viewport to use certain line weights and fills in the viewport. That way, your drawing classes stay as they are, and you can apply appearance overrides to your sheet viewports.

I'm going to try to digest everything you just wrote, but I think it makes sense. I'll give it a go. Thank you! EDIT: it maxes out at 4. So I can't indent it enough, but 4 makes it line up with the other stuff and collapse accordingly.

Ha...scrolled right past it....

Thanks to all who have guided me in upgrading my script game to include event-enabled PIOs. It has made a huge difference in how the plug-ins I've been writing operate. But, I've run into another issue I may need some guidance on. I've been able to create collapsible sections in the OIP, indent the parameters, and add buttons. But, the buttons are the full width of the OIP, and do not hide with the collapsing sections. Additionally, anything below the first button doesn't hide, either, although I haven't delved into whether I updated the numbers correctly on that one. So, first thing, I would like the "Select Texture" and "Select Symbol" buttons to be the width of the drop-down menus above, so that everything looks consistent. Is this even possible? Secondly, everything between "Mounting Options" and "Specs" should collapse away when "Mounting Options" is minimized. I will also need the buttons to hide based on the selection of some drop-down menus. I think I will be able to accomplish that by not calling for the creation of the button depending on the status of the drop-down, but that would also change the paramID of following buttons, so that could get squirrely. I appreciate all the help!!

What I've done in this case is figure out the range, multiply that by the random number, and add it to the low number.

That's what it was. I don't know when that changed, because I had used it before on this very plugin! Thank you!

It would be a pretty easy script to write. Essentially select your 300 symbols, run the script, enter a high and low value, then just loop through the symbols assigning a random value between the two numbers to the Z height of the symbols. Don't have time to write it at this moment, but might be able to tomorrow.

I did it. I finally managed to make an even-enabled plug-in using some of @Jesse Cogswell's helpful hints. So far, everything is working just like I want it. Except for one thing... on my final tests, I realized that the drop-down menu of class names no longer appears in my OIP. Before switching to event-enabled, it worked like I expected, as a drop-down menu with all the class names, just having the field set to a "class" type. I'm assuming something in the event code breaks this type of field, and it must be taken care of in the coding. Any ideas?

This is really helpful! I think I have finally been able to parse most of this and figure out what it does. Going to try to really dig into it when I'm back on my big system at home. But I think I can work from this and update a couple of my plugins to make use of this style. Having the collapsible headers and maybe a symbol dialog will be great!

I see headers, but not collapsible headers.

@Jesse Cogswell Oh boy! Thank you. I will have to dig into this. But my brain is too tired right now. One thing I really want to learn is how to make a collapsible header like you get in eh door or window tool. Someone else has linked to a way before, so I need to look through that as well.

I have tried so many times to wrap my head around event-enabled scripts so that I can have sections and buttons and other things in my OIP. But instead, I decided to just go put my head through a wall because it's less painful.

This is a little number/letter grid maker I threw together for a recent project. Might take a few tries for the output to make sense given the input, but I just haven't gone back in and clarified it all yet. But, yours to use for now if you want it. Insert Letter-Number Grid.vsm

TBB_GetPageArea gives me exact page size if I use a borderless page size in printer setup, and .00166666" off if using a page size with borders. Would be close enough for my needs.

I use Num2StrF quite a bit, but since I've only really ever worked in feet/inches, I just thought it dealt with Feet (figuring that's what the F stood for). Good to know that it works in other ways as well.

Yes, this is what I need to go back and do. I didn't include the " after all of my dimensions, so they're all over the place. I think the vast majority of the issues will be fixed with that. From there, I'll just work on converting entries in the OIP to and from whatever units.

Oh, perfect. That will probably be what I need. Going take me weeks to update all my plugins to work under different units settings. Just something I never paid attention to. Are you in the Atlanta area? I have a bunch of friends who have lost power after a storm rolled through a few hours ago.

I wrote a really awesome plugin, but realized upon further testing that it (and I guess nothing else I've written) accounts for document units being anything other than inches or feet/inches. Because I rarely draw any other way, I've never noticed it. So, now I need to modify things to account for document units. Is there a simpler way to do this outside of having a list of all possible units, and creating a multiplier variable which I then I have to multiply every dimension by?

I did a brief search and didn't find anything on this, but I imagine it's out there... Was testing out a cinder block texture and found that in 2023, the bump looked normal, then had a secondary bump at fumble the size on top of it. But only in shaded mode. The same texture in 2022 did not exhibit this behavior. The circle in the texture is just for extra visual cues while testing. I have tried every setting and mapping I can think of, and all come out with the same result. Tried a new bump map and the same thing happened. Any ideas? Running 2023 SP4.