[LTspice] Attribute Window doesn't do anything

Jun 08, 2005 9 Replies

Greetings:



In LTspice 2.15c the docs state: "You can edit the visibility of attributes using the menu command Edit|Attributes|Attribute Window. After you select an attribute with this dialog you will be able to position it as you wish with respect to the symbol."


I am able to get this dialog, but it appears to do nothing except, well, nothing.



That is, I don't find any option to position anything in relation to the symbol, or set any "visible on schematic" options.



What is wrong?


BTW: I have tested this on Windows 2000 running natively (also happens with Linux/WINE).


Good day!


_______________________________________________________________________ Christopher R. Carlen Principal Laser/Optical Technologist Sandia National Laboratories CA USA crcarleRemoveThis@BOGUSsandia.gov NOTE, delete texts: "RemoveThis" and "BOGUS" from email address to reply.

Thanks for the input, Helmut.

As I said, I tried it under native Win2k. It doesn't work :-(

What is the OS you are using?

I am surprized that I'm having trouble under Win2k.

_____________________ Christopher R. Carlen crobc@bogus-remove-me.sbcglobal.net SuSE 9.1 Linux 2.6.5

"Chris Carlen" schrieb im Newsbeitrag news: snipped-for-privacy@news2.newsguy.com...

Hello Chris,

I have done it thousand times and it works. Here an example.

  1. Open the symbol, e.g. LT1013.asy

  1. Edit -> Attributes -> Attribute Window

  2. Click on InstName

  1. OK

  2. Now you have "Unnn" on your cursor in the symbol window.

Please exercise under WIN to be sure not to fight with the WINE emulation.

Best regards, Helmut

It works just fine under Win2k here. After you click the attribute such as "InstName", then click "ok". You now can position it where ever you want. But it does not show up on the screen until you click "ok".

Hello Chris, I have done this thousand times under WIN-98, WIN-2K, and WIN-XP. Now I multiply this by ten thousand users which leads two ten million times that somebody has done it successfully.

This has nothing to do with WIN-2K and LTspice. :)

Best regards, Helmut

The LTSpice interface has oddities like this. For example, when you create a dot command, using the 's' function, it leaves it floating, invisible, on your cursor. You only see it when you move the cursor!

If you don't then place it by clicking the mouse, it cancels the command, rather than placing it in some default location. I get caught by this again and again. "Why doesn't this node have my .IC voltage?" I shout. Then, of course, I immediately shout "Doh!", and retype it, this time placing it in the schematic.

Now, I'm using this under linux/wine, so it may be that some of the oddities have to do with that combination. However, if only the thing would initially show up visible, it would save me a bit of time on occasion.

Regards

Oh, now I get it.

Duh!

Thanks.

_____________________ Christopher R. Carlen crobc@bogus-remove-me.sbcglobal.net SuSE 9.1 Linux 2.6.5

Implying what may I ask? That I am a bonehead?!?!?

Well in this case that happens to be correct. I dunno why I just didn't click "Ok".

Now I get it. And I feel like mud. ;-)

Not really.

Thanks for the input.

Good day!

_____________________ Christopher R. Carlen crobc@bogus-remove-me.sbcglobal.net SuSE 9.1 Linux 2.6.5

Hello Bob,

Your problem can be dedicated to WINE. People shouldn't always try to tell that LTspice has bugs when using WINE. In reality WINE has the bugs. I's the the task of the WINE programmers to correctly run WIN-programs. They promise that you can run WIN-programs, so they should fix their bugs.

Finally, every program has it's intended GUI behaviour. If you want it always different, then you should try to write a similar program. You will easily find that it's very difficult or impossible to strictly keep a certain methodology throughout all the features of a big program.

Best regards, Helmut

Oh, don't get me wrong, I'm getting more and more fond of LTSpice. It is simply that this particular situation annoys me, and I thought it might be the same issue as Chris was seeing.

Regards

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required