MORE BLOCK PROBLEMS

N/A

Ricky, based on my last entry re dragging/dropping blocks into the Library, I thought
I had figured it out and wouldn't have anymore problems. However, shortly thereafter,
I tried to edit a block. That went ok until I closed out the edit environment to
go back into the draft screen. The cursor looked normal but I wouldn’t select/highlight
anything. I could select a command but it would excute that command. If I saved/closed
the file and reopened, it worked ok until I tried to repeat and it also repeated
the problem. I restarted my PC and retried. Same thing. So I edited my registry
to reset back to default conditions. I tried it again. Damn it. Same problem.
This is a new one for me.
A few days ago I downloaded a Uniblue PC SpeedUpMyPC and System Tweaker. I ran
it without problems. Other programs are working ok. I mention this only because
it’s something different that I’ve done in the last few days.
Help!
Ron
Ronald W Latour
8 REPLIES

Re: MORE BLOCK PROBLEMS - EDITED

N/A

Rick, I've edited what I wrote intially below to better describe what's going on.
Ron
"Ronald W Latour" wrote:
>
>Ricky, based on my last entry re dragging/dropping blocks into the Library,
>I thought
>I had figured it out and wouldn't have anymore problems. However, shortly
>thereafter,
>I tried to edit a block. That went ok until I closed out the edit environment
>to
>go back into the draft screen. The cursor looked normal but it wouldn’t select/highlight
>anything. I could select a command but it wouldn't excute that command. If
>I saved/closed
>the file and reopened, it worked ok until I tried to repeat the block edit and

it also repeated
>the problem. I restarted my PC and retried. Same thing. So I edited my
>registry
>to reset back to default conditions. I tried it again. Damn it. Same problem.
> This is a new one for me.
>
>A few days ago I downloaded a Uniblue PC SpeedUpMyPC and System Tweaker.
>I ran
>it without problems. Other programs are working ok. I mention this only
>because
>it’s something different that I’ve done in the last few days.
>
>Help!
>
>Ron
>
>Ronald W Latour

Ronald W Latour

Re: MORE BLOCK PROBLEMS - EDITED

N/A
Ron,
When you exit block edit, are you using the Close Block button to exit or
are you killing the window to exit. Always use the button. There have been
some problems with killing the window when in Block Edit. These will be
fixed in the newxt release.
Regards,
Rick B.

Re: MORE BLOCK PROBLEMS - EDITED

N/A

Ricky, I've always used the Windows Close X. I didn't even pay any attention to
the ribbon button. However, I opened SE and clicked to edit a block. Than went
to the preferred ribbon command to Close the Block Edit. Nothing happened. The
edit window remained open. I tried several times.
Now what?
Thanks,
Ron

"Ricky Black" wrote:
>Ron,
>When you exit block edit, are you using the Close Block button to exit or
>
>are you killing the window to exit. Always use the button. There have been
>
>some problems with killing the window when in Block Edit. These will be
>fixed in the newxt release.
>
>Regards,
>Rick B.
>
>

Ronald W Latour

Re: MORE BLOCK PROBLEMS - EDITED

N/A
Ron,
There is a known problem with using the close window X when editing a block.
It can get your file into a bad state. This will be fixed in the next
release. Solid Edge users already have the fix because thet get regular
updates. For now always exit Block Edit using the command button.
If you create a new Draft file are you having the same problems with
commands?
Regards,
Rick B.

Re: MORE BLOCK PROBLEMS - EDITED

N/A

Ricky, I opened SE with the default template and tried the edit block double click.
Than closed out of the edit screen using the close block menu button. It worked
the way it is meant to.
I guess this apparently means that any file I may've used the window X to close
out of the block edit screen could be suspect/corrupted. That's a hell of secret
to keep to yourselves. Admittely this is a free download but at the very least you
could have posted a warning or something. THat makes me wonder is there other bugs
that can corrupt files that you know about but haven't shared.
Thanks,
Ron

"Ricky Black" wrote:
>Ron,
>There is a known problem with using the close window X when editing a block.
>
>It can get your file into a bad state. This will be fixed in the next
>release. Solid Edge users already have the fix because thet get regular
>updates. For now always exit Block Edit using the command button.
>
>If you create a new Draft file are you having the same problems with
>commands?
>
>Regards,
>Rick B.
>
>

Ronald W Latour

Re: MORE BLOCK PROBLEMS - EDITED

N/A
Ron,
There is easy way to see if the problem has been introduced into a file.
From the files that I have seen with the problem, the working Sheets tabs
disappear at the bottom of the application window with the file open.
Any file that you have created and this problem occurs can be fixed. All you
have to do is to sent the file to me. I can have it fixed and send it back.
This is an unusual situation. I do not know of other workflows that
introduce problems like this.
Regards,
Rick B.

Re: MORE BLOCK PROBLEMS - EDITED

N/A

Ricky, I tested your theory with the attached file. It is the custom template file
that I created which resides in My Documents and is one of the files that I tried
to close out of the block edit the wrong way. It also exhibits the problem that
I described in this tread; namely, 1) won't close the block edit screen using the
ribbon menu command and 2) if the block edit screen is closed using the Windows
X sucessfully, the model view cursor is dead. Both the Model View and Working Sheet
View show up.
Thanks,
Ron

"Ricky Black" wrote:
>Ron,
>There is easy way to see if the problem has been introduced into a file.
>From the files that I have seen with the problem, the working Sheets tabs
>
>disappear at the bottom of the application window with the file open.
>
>Any file that you have created and this problem occurs can be fixed. All you
>
>have to do is to sent the file to me. I can have it fixed and send it back.
>
>This is an unusual situation. I do not know of other workflows that
>introduce problems like this.
>
>Regards,
>Rick B.
>
>

Ronald W Latour

Re: MORE BLOCK PROBLEMS - EDITED

N/A
Ron,
I sent the fixed file directly to you.
Regards,
Rick B.