File Locking Fix on Mac Eagle 7.5.0

On 12/24/2015 7:14 PM, lisa fredrickson wrote:

Hi Jorge,

 

I think I fixed the file locking problem on my Mac running Yosemite OS X

and Eagle 7.5.0.

I posted about it online earlier.

 

I'm wondering if the fix could be as simple as requiring the user to

open his schematics and

boards through the Eagle console while in an an open project, and

defeating the user's ability

to open the schematic or board directly by clicking on it in the OS X

Finder and thereby

bypassing opening the project.

 

Perhaps the schematic and board's System Open File With... Attribute

could be set to an

auxiliary program that instead of opening it , tells the user to open it

using Eagle in an open

project to not disturb the lock mechanism.

 

Could you check my post and see if there's a simpler solution in there?

 

Lisa

 

--

To view any images and attachments in this post, visit:

http://www.element14.com/community/message/170103

 

Hi Lisa,

There were a number of file-locking issues reported for the Mac

platform. These have been addressed in our latest beta 7.5.1, if you

could try it out and let me know if everything working that would be

very helpful.

Any feedback on the file-locking or any other feature of EAGLE is always

welcome.

Best Regards,

Jorge Garcia

I noticed another bug leftover from installation.  I had Eagle 6.4

installed on

my machine then installed 7.5.0.  I would create a new project in Eagle

7.5.0.

However, if I later started Eagle by clicking on the eagle.epf in the

project folder,

it started the earlier version of Eagle instead of the current version, and

I could

even end up with two versions running at the same time.  When you quit from

the wrong

version, it gives an error message about over-writnig the eagle.epf from

another version

of Eagle.

On Mon, Dec 28, 2015 at 10:51 AM, lisa fredrickson <

I noticed another bug leftover from installation.  I had Eagle 6.4

installed on

my machine then installed 7.5.0.  I would create a new project in Eagle

7.5.0.

However, if I later started Eagle by clicking on the eagle.epf in the

project folder,

it started the earlier version of Eagle instead of the current version, and

I could

even end up with two versions running at the same time.  When you quit from

the wrong

version, it gives an error message about over-writnig the eagle.epf from

another version

of Eagle.

On Mon, Dec 28, 2015 at 10:51 AM, lisa fredrickson <

On the Mac, you change file association as follows:

1. a. click on file, invoke File -> Get Info or b. right-click on file, ->

Get Info

2. the current (attempted) file association is shown in the Get Info dialog

3. unlock the lock at the bottom of the Get Info dialog (requires admin or

owner password)

4. change the file association in the Get Info dialog

5. if it won't change it:

a. Check that the new association application is an allowed source in

Applications -> System Preferences -> Security and Privacy

b. If not, Allow from Anywhere

c. change the file association in the Get Info dialog

6. Lock the lock at the bottom of the Get Info dialog

7. Go back to Applications -> System Preferences -> Security and Privacy

and allow sources from identified developers only

On 12/28/2015 8:00 PM, lisa fredrickson wrote:

If I save a file with Eagle 7.5.0, and quit Eagle, and later click on

the file to open it,

I expect Eagle 7.5.0 to open it, not an earlier version of Eagle.

Hi Lisa,

Thank you for the clarification, ignore my earlier reply. I know how to

do this in Windows but Im not quite sure how to do it on the Mac.

Hopefully someone can chime in.

In Windows there's a setting in the Control Panel which controls which

programs are assigned to which file extension. If eagle is associated

with .sch Windows will call the executable that was installed at the

time of setting up the association. It's not aware of any newer versions

of the program.

I think something similar is going on under the Mac OS.

Let me know if there's anything else I can do for you.

Best Regards,

Jorge Garcia

If I save a file with Eagle 7.5.0, and quit Eagle, and later click on the file to open it,

I expect Eagle 7.5.0 to open it, not an earlier version of Eagle.

On 12/28/2015 1:57 PM, lisa fredrickson wrote:

I noticed another bug leftover from installation.  I had Eagle 6.4

installed on

my machine then installed 7.5.0.  I would create a new project in Eagle

7.5.0.

However, if I later started Eagle by clicking on the eagle.epf in the

project folder,

it started the earlier version of Eagle instead of the current version,

and

I could

even end up with two versions running at the same time.  When you quit

from

the wrong

version, it gives an error message about over-writnig the eagle.epf from

another version

of Eagle.

Hello Lisa,

This is probably not a bug but actually the intended behaviour. The .epf

file stores all of the info about the last time the designed was opened,

version of EAGLE, window positions, libraries in use, etc. If the last

time that design was opened it was opened with 6.4 then the eagle.epf

file would likely call for 6.4 to open it.

Personally, I usually just open EAGLE and then from there open whatever

I want to work on. When you have multiple versions of EAGLE installed

this is usually easier than relying on the OS to figure out which

version of EAGLE to call.

hth,

Jorge Garcia