Just LOST 13 hours of work ... Horrifical Level Sheets... LOL


#1

All of my prior projects have fit on one schematic sheet.

After searching and reading I “thought” I knew what I was attempting to do; it appears now that I did NOT.

WHY is one even allowed to block copy a sheet? … when it breaks things?

Oh, I’m 100 percent certain that I caused even more issues with my attempt to manually modify the sheet files in a text editor…

I simply did not expect the rabbit hole to go down that deep.

Anyways, 100 percent MY fault… but it would have been nice if I had NOT been let to going down that hole…


Purpose of unit path entries in schematic
Assigning different footprints in otherwise identical hierarchical sheets
#2

You know what back up copies are, right?

If not, it’s time.

PS: my condolences. :head_bandage:


#3

Modular design. One can have multiple instances of the same sheet. (I use that all the time.)

It never broke something for me. Can you give more information what exactly happened such that other people can learn from your mistake? (In other words: You have me worried right now.)

Always bacup before you do that! :wink: (git or svn is your friend)


#4

Well, a combination of block copying, renaming, and creating new sheets when the old schematic files were still in the project directory.

I think that if you know what you are doing, there won’t be any problems.


#5

My sincerest sympathy for your loss. :sob:

I suspect that anybody who has worked with any kind of CAD, CAE or EDA tool for more than 6 months has experienced something similar. The most practical solution to the problem is “backups” or “archives”. I have trained myself to create fall-back copies at least twice a day when I’m actively engaged with a project. The automatic backup feature in many programs is of limited help, unless it lets you retain those backups at least 3 or 4 deep.

(Consider: You set the automatic backup to operate, say, every 15 minutes. After you do something stupid, you typically spend the first 10 minutes just verifying that you did something stupid. Then you spend 10 minutes trying to un-do your stupidity. Then you spend 10 minutes trying to calm down, cover up, and deny your stupidity. By this time, the automatic backup feature has preserved your stupidity twice over.)

In exchange for a serving of my preferred malt beverage, you can be assured that neither your co-workers nor your supervisor will learn of your mistake from me.

Dale


#6

So, after giving it some thought, I think I know what started me down the rabbit hole.

I created the first sheet (1 sheet) then block copied it (2 sheets).
Then block copied those two sheets (4 sheets).
Then block copied one of those sheets (5 sheets).
Then I renamed the sheets… DOH…

So, if one does NOT do ^^^THAT^^^ it probably works as expected.


#7

What address do I put on the shipping label?


#8

ROTFLMAO!!! I was to irked with myself, and the discussion to real, for me to see the humor in it.

Unlike you, I was “In Denial” of my stupidity for at LEAST 15 minutes before going into the verification stage.

The rest of that paragraph is SPOT ON, and I did not see the humor in it at all last night.

Maybe three times in my case. :confused:

They say comedy is only funny if it is a least partly true…

I wish I could have yesterday back.

Thanks for the laugh tonight! :+1:


#9

Forty-four years ago this month, my wife’s aunt started arranging for us to meet. Supposedly, my sense of humor reminded her of her brother-in-law (my wife’s father), and this in turn suggested compatibility between my wife and I. You’ll have to ask my wife for examples of dumb jokes I’ve pulled on her across almost 43 years of marriage.

Dale


#10

That’s a malt, not a milkshake. From Steak-and-Shake, of course.

Dale


#11

A good example of why you should use revision control. Nowadays I don’t start any serious project without revision control. It also helps that all kicad files are text based.


#12

There is no reason for people to not use a proper source-code control system. There are many free options for repository hosting.