there is a bug in your editor. When I install it into the default path, it can’t write to some of the files it needs.
For instance, create a new project:
Access to the path C:\Program Files (x86)\Nextion Editor\ca.ca is denied.
Open a new project:
Access to the path C:\Program Files (x86)\Nextion Editor\data.xml is denied.
I am running Windows 8.1 x64. It works OK if I install it to a non-standard directory, e.g.
The problem is that you have to run it as admin, or it won’t work.
The proper way is for the data to be stored somewhere else, since only admin can write to Program Files.
That is not safe.
This issue should be solve in v0.20
Windows programs should NEVER demand write access to the "Program Files" folder!
As posters before have mentioned, all dynamic files should be saved into user folders.
No matter if there are workarounds (Admin privs, alternative install folder, ...), this should be done the intended way.
An official statement ragarding this issue would be appreciated.
I get the "access denied" error even when running as admin. Using current download available 7/19/2015. Any work-arounds?
As stated in the other thread
I had a similar problem, till I realized that my `ca.ca` somehow got set to read-only - maybe due to a non-complete uninstall of the previous version.
After correcting that it worked.
Another workaround is to close Nextion Editor, delete the `ca.ca` file and let NE rebuild it.
That's also what I thought the first time, but I don't get this error message when I run Nextion Editor as an adminstrator.
Scruff.r, Thanks, that did the trick.
Thanks Scruff.r mine was also read only. Fix now.
In windows 7, 8 do not install programs in folders defined by the system, install in folders on disk C root, this prevents denial of access.
C: \ Program Files (x86) not to install, use eg C: \ users_program
for example: C: \ 0_Programas_Eletronica \ Nextion
It's no good practice for software to demand being installed in a non-default directory (especially if this software is written for that specific OS).
But the current version (and a few before) has already addressed that issue and does behave as MS demands of software for their OS:
Files that are to be written to during program run must not be placed in the program install path.
For (non-user) files, like settings, the `%appdata%` path should used.
In fact, the server is always on line..... strange things....
We will try to fix it.
Its been working for me the last two days now ,before it was doing it so I assumed that was the case
It might have just been an internet lag timeout