Editing blocked in file.....

[frankriedel]

What has happen to my file... i suddentlig can not edit it....

Please try load this file and try edit the schematic...

ANY HELP.... a hell of alot of hours in it

[CoreStylerz]

What has happen to my file... i suddentlig can not edit it....

Please try load this file and try edit the schematic...

ANY HELP.... a hell of alot of hours in it

It works.. Maybe too CPU intensive 4 yours?
the main fact is that there are too much components for free version. And i suggest you to use one trigger connected to many not 200 triggers.

[frankriedel]

Thanks -
The limit is 25.000 - right - as i see it in static for my file it is around 7.500 components -
I have 2 PCs that can't edit the file - I have a Rental Activated Version

.... so it must be other prob on my side - right ??

Regards
Frank

[CoreStylerz]

What's your CPU and RAM.. Maybe it crash because it need time to load.

[support]

Sorry Frank - looks like a little bug has caused your module to become locked.

There's an easy fix. Select the parent module then press SHIFT+CTRL+ALT+L.

Go back inside the module and you should now be able to edit it.

The bug occurs when a component is positioned at a grid position of (255,255). At that moment the module locks. You're using a large area of schematic, more than most people would so it's not surprising this is the first time we've seen this.

In your schematic the 255,255 point is around the 4th String Compare down that connects into the green boxes. I would suggest keeping away from this area - maybe stick a module over the area so that you can avoid it.

If anyone else finds this happen to them you'll know straight away. Either you'll suddenly not be able to make any more edits or all the components will suddenly become hidden. You should immediately Undo the last operation (at this point any hidden components will reappear again). Then go up one level and perform the key combination described above.

In the meantime we'll get this fixed for the next release.

Apologies once again for any inconvenience caused.

[infuzion]

Sorry Frank - looks like a little bug has caused your module to become locked.
There's an easy fix. Select the parent module then press SHIFT+CTRL+ALT+L.

Is that lockable module code still in there?

[support]

Is that lockable module code still in there?

You mean so you can go the other way and lock a module intentionally? It's there but not enabled so you can't intentionally lock a module.

The module locking feature went so far but then there were concerns over whether people could hack it to see inside and peek at protected work so it got put to one side. It's one thing making lockable modules possible but it's a much bigger job to make it highly secure.

[frank-riedel]

THANKS ALOT FOR YOUR HELP ! ! !