Add to Working Set and Remove from Working Set buttons not working

[Anonymous]

When I am editing a reference, there are two buttons available: "Add to Working Set" and "Remove from Working Set."  When I click on either one of them, the REFSET command is activated, but the object I have selected isn't automatically added or removed.  I am still prompted to choose "add" or "remove."  No matter which button I press, "add" is still the default selected.

Autodesk, how do I fix this?  I've found several different posts about the subject, none with answers.  In fact, someone from autodesk replied to one of the posts saying "this problem only happens to you."  Another post was from 2011!  Why haven't you fixed this bug yet?  Why have two separate buttons if neither of them actually executes the full command?

[rkmcswain]

Apologies, I can't help with this particular issue.

Just wanted to say that REFEDIT was buggy when introduced, so most people at that time avoided it and use BEDIT or XOPEN instead.

[Anonymous]

XOPEN is useless for transferring objects from the xref directly into the drawing and vice versa.  Same with BEDIT, unless you are editing the block in place, in which case, the add and remove buttons have the same issue.

Bugs are inevitable in any software, but the point of forums, suggestions, and updates is that Autodesk should be working to fix these bugs.

[rkmcswain]

You can use NCOPY for the Xref->Parent copy, and this lisp for the Parent>Xref copy:

http://lee-mac.com/copytoxref.html

As to your point on bugs, sure, you're right. But there are bugs in the software that have been there for years.

You can wait around for years or find a workaround and get back to work.

Cheers.

[Anonymous]

It actually takes less time to just manually select add or remove from workset.

As for bugs that have been around for years:

Those are the ones that need the most attention, wouldn't you agree?  Autodesk has customers who expect a working product.

You're right.  I will continue working (I never stopped).  I will also continue letting autodesk know that I am dissatisfied with this issue until they do something about it.

[john.vellek · Accepted solution]

HI @Anonymous,

I wanted to assure you that the issues you have pointed out are logged with QA/Development. Your continued diligence does get noted and I appreciate your contribution.

[Anonymous]

I'm running ACAD2015 and it works just fine here.  Have you checked you CUI for an error in the macro behind the button??

The macro behind mine reads:

$M=$(if,$(eq,$(getvar,refeditname),""),^C^C^P(ai_refedit_alert);^P,$(if,$(and,$(=,$(getvar,tilemode),0),$(=,$(getvar,cvport),1)),^C^C_refset;,^C^C_refset _add;))^Z

$M=$(if,$(eq,$(getvar,refeditname),""),^C^C^P(ai_refedit_alert);^P,$(if,$(and,$(=,$(getvar,tilemode),0),$(=,$(getvar,cvport),1)),^C^C_refset;,^C^C_refset _rem;))^Z 

[Anonymous]

Mine reads:

$M=$(if,$(eq,$(getvar,refeditname),""),^C^C^P_ai_refedit_alert;^P,$(if,$(and,$(=,$(getvar,tilemode),0),$(=,$(getvar,cvport),1)),^C^C_refset;,^C^C_refset _add;))^Z 

and

$M=$(if,$(eq,$(getvar,refeditname),""),^C^C^P_ai_refedit_alert;^P,$(if,$(and,$(=,$(getvar,tilemode),0),$(=,$(getvar,cvport),1)),^C^C_refset;,^C^C_refset _rem;))^Z 

There's only a slight difference - where you have a parenthesis, mine has an underscore, and mine is also missing a second parenthesis.  (sorry for layman's terms, coding is a language I have never been fluent in)

I tried changing mine to match yours, but it didn't work.  I also have 2014, although I can't imagine that would matter for the macro...

[Anonymous]

I've just looked at three versions (2014,2015,2016) OOTB all of them have parens (open and close) around  (ai_refedit_alert) like this:

Yours opens with an underscore and doesn't close.  Mine works.

Have you altered the function of ^c^c by any chance????

[Anonymous]

---

@Anonymous wrote:

I've just looked at three versions (2014,2015,2016) OOTB all of them have parens (open and close) around  (ai_refedit_alert) like this:

Yours opens with an underscore and doesn't close.  Mine works.

Have you altered the function of ^c^c by any chance????

---

@Anonymous,

what I was trying to say before is that I did notice the difference between my macro and yours (the fact that mine had the underscore and didn't close).  It makes sense that that might have been the problem, but I changed that.  I tried manually altering it and then I actually just copy-pasted the code that you posted, for good measure.  It still didn't fix the problem.

Like @rkmcswain said, this has been a problem for a few years.  I think if it was as simple as fixing the macro others would have found that solution by now.  I think this is a bug Autodesk needs to fix, which they have informed me they are working on, so as I see it, my post was a success.

[Anonymous]

I saw that some have said this has been a problem for a few years, but it works just as expected here (AC2015) without issue, and has for years.  That being the case, it appears to be setting related and not a bug.  (see attached setvar list)

Now it doesn't change prompts (if that's what you mean), but I don't read prompts half the time anyway, grab the button, grab the component, press enter and I get "1 Removed from working set" (or "Added") but i assumed that's because my QAFLAGS = 2 or something.

[Anonymous]

I'm glad it works for you.  That doesn't mean it's working for me.  It's not just about what the prompt says, it's about the fact that IT'S NOT REMOVING THE OBJECT.  It doesn't say "removed" or "added" because it doesn't work.

Autodesk has reached out to confirm that they are working to fix it.

If it is a setting problem, I would be happy for suggestions on how to fix it.  I checked the macro and that didn't work.  Telling me that yours works fine doesn't really help my problem.  I'm not even finding the refset command on your list.

[rkmcswain]

john.vellek wrote:

I wanted to assure you that the issues you have pointed out are logged with QA/Development.

@john.vellek - with all due respect, I think you may be giving @Anonymous some misguided hope. Just because something gets logged with the Dev team makes no assurances that it will be fixed. There are bugs with much more impact than this one that have been reported and unfixed for years.

I hope they do fix this and everything else that we all need fixed.

[Anonymous]

@rkmcswain I don't expect autodesk to fix this for me personally.  It's not like the program isn't working, it's a matter of convenience and something that marginally slows my workflow.  If it couldn't be fixed in a setting I wanted an assurance from them that they are aware that it is a problem, since there were no satisfactory responses in any of the other posts I looked through while I was troubleshooting.

[Anonymous]

Refset is not a system variable, which is the list I included for you to compare against your settings.

If it works for me, and I can't replicate your problem then we can ONLY compare settings from there.  I have no access to your settings so you have to do it yourself.   If you can't find an anomaly in the setvars, we'll then compare profiles.  Sorry I can't provide some magic for you to accomplish without effort but that the current state of the the issue. You can continue to kvetch to Autodesk, as you appear to have been doing for years to no avail, or you can look at your settings and see what different ... mox nix to me.

 

[Anonymous]

I know this is an older discussion but was having the same problem.  Saw the post about the macro & realized that the add/remove buttons on my 2015 work fine, except when in paperspace, TILEMODE=0 & CVPORT=1.

These are not variables I've paid much attention to - was wondering why the IF statement is necessary?

Thank you.

[aeichnerMBLN5]

I know, but as you will quickly notice looking in the forums, those suggestions are ignored for years.

There is an expression "Doing the same thing and expecting different results is a sign of insanity."