openrcforums

While you were sleeping... R316 is out.

Lotsa new stuff:
XML based save data.
File info showing a summery of the sizes in the file.
Nicer kinder gentler fuse settings dialog. Push a button - get it done!
Bug fixes galore. Should actually work .


Oh yeah,
Linux i386 and amd64 .DEB packages now work properly and can be used!

Just when you thought it was safe to connect to the internet. It's been a long night and the Gin is making the code wobboly.

But here's R317.

Change?

Notes!
Finally. This one was truly difficult for various reasons which are not important now.

Doesn't matter. You can enter notes and they will be saved in the .EEPE file. They will not, however; be saved in your radio. Can't help you there....


Hiccup.




Now excuse me while I crash gracefully (un) in my bed and wake my better half by snoring louder than her. See ya 2morrow.

Erez, as always you're tha man...

Erazz the notes are still not working well. I found a bug by coincidence. just installed the latest version from eepe.
Created a new basic model, channel 4 is ailerons and added a note. then inserted the sticky throttle cut template and the note junped to one of the lines of the throttle channel. deleted the model and did it again, this time prog also another channel with a switch and created a note. inserted the same template and the same happened. the note from the last channel went to the aileron liné and the one from the aileron also jumped up to the throttle channel..

I think that if you insert the note for example on the 5th line, when you insert more lines before that line, the note will jump to the line that is on the 5 th place now..nothing to do with the templates.. You just have to insert a line on one of the channels above that note and it will jump.. I don't know if I explained it well enough..

João

Yes you have.... I'll take a look at it.

HOORAY for notes! Many, many thanks erraz. Now, I don't have to rely on my lousy memory. Even with the glitch mentioned by Joao it's a big step forward.

I noticed another minor glitch in the EEPROM Data. The byte data per model has slipped down a notch compared with the numbers shown in the model select screen. Also, if there is a non-sequential model, say in slot 16, it doesn't show up in the summary.

Question; is there a byte limit per model or is it just the total that counts. If so, it would be nice to have a reminder of it on the model select screen, referring to eepe.

As has been said many times erraz, your efforts are greatly appreciated.

Bill

I noticed that error an already fixed it. It'd be out on the next release, I just figured it was too small to warrent the inconvenience.

There is no byte limit per model. IINM the max is around 400 bytes. That's not a limit but just how much the data structure can hold.
I'll look into adding a "total bytes free" somewher on the model select screen.

Eraz, thanks for implementing the info about wrong set switches with the default switch warning

So there is just another wish for EEPe
When trying to use more than 32 mixes (happened lately to me), the last mixline disappears without a warning.

There should be a warning instead of deleting the last mix


Reinhard

K!

I think I have seen that the code, in er9x, to save model data and general data actually writes a new copy to the EEPROM BEFORE removing the old copy. This means that you need enough free EEPROM to hold the largest model, or you cannot save it. I may be wrong, I haven't checked it that closely.

Mike.

IIRC the reason to write and then copy is to speed up the write procedure.
We can take a look at that but I think that when I looked at it it seemed resonable and prudent to do.

OK,
I get it. The reason for this is to prevent corruption. If the radio would be switched off while the file was writing then the data would be corrupted. This way, you first write all the data and then you actually tell the radio to go to the file. If you switch off your radio then the changes would be lost but the model would still be there.

Clever.

See, I can't fault Thomas. His system is very very good. Perhaps we need to change the memory warning to alert the user that no more data can be written.
btw. this is the reason for the inconsistencies when editing a model. When you edit a large model you need a large temp file. When it's a small model you need a smaller file.

I think I fixed most of the issues with the mixers and notes.
The notes do not work while copying and/or pasting. I know this. It's not simple to do (the whole copy/paste mechanism isn't simple), I will try to solve it in the future. No need to make a point of it

Release will be up shortly.

Wow, ok I'm gonna save all the Thank You's and just get straight to the point.

Erazz, and others, have done alot of really brilliant work, for the love of the hobby, and the continuation of others enjoyment.

Click the link below and send him a couple bucks! I would'nt ask if I didnt already do it.!

https://www.paypal.com/us/cgi-bin/websc ... 7fb2afeca3

When Mike and Skynorth put a donate link up, I will copy and paste and promote that too. THEY HAVE EARNED A LUNCH FROM US AT LEAST!!!

Pat

Thanks Pat
They certainly do deserve it!



I've made more changes to the .deb files.
1) Now we have dependencies. Ubuntu software center and gdebi make wonderful use of this. To install in Ubuntu now you just need to click the link off of the code page. Neat!
2) I also enabled checking for updates under linux and Mac. Since we now have automatic builds this makes sense.
3) I moved the executable to the /usr/bin directory so that you could run it off of any command line by just typing eepe.


Now onto automated Mac builds. Let the new headache begin

Erazz, did you remove the er9x manual icon from eepe?

Thanks,

João

I removed it from the toolbar to prevent clutter.

It's still under "Help"

yes, I saw it.. just checking that you did it intentionally.. Could be another bug

João

I've just made some small changes to eepe, and asked Erazz to build a release. I'm not very familiar with QTcreator so changes are slow going at the moment. If there is anyone else out there who could help with eepe, I could spend more time on er9x/ersky9x instead!
I'd like to have a version of eepe that supports ersky9x, either integrated into eepe, or built as a separate program, but it will take time.

Mike.

I would love to.. just for the sake of learning qt. But am so busy.

I forgot how time consuming having a baby is!

Sent from my Nexus 7 using Tapatalk 2

OK, so r345 is now available, thanks Erazz. I'm going to try to get eepe more up to date with er9x over the next few weeks, time permitting. This may mean fewer changes/updates happen to er9x while I do this, but I think it is important that eepe reflects er9x.

Mike.

Thanks Mike..

João

After installing Eepe on my Mac I get a message that there is an update(R345) available.
If I use the link which is mentioned in this message, I can't find any downloadable update R345, only the one that I just installed.
How is this possible?



Sent from my iPad using Tapatalk

Unfortunately the update notification doesn't differentiate availability of Win and Mac versions. There have been Win updates so you get the notification, but nobody built a Mac version after r339 so there isn't one to download...

I actually followed the instructions, checked out the code with svn, and compiled it myself. Worked like a charm. You need to get xcode (can be had for free) and install it first.

I tried the same with companion9x, but some of the mac requirements weren't up to date, so no luck there.

If you don't want to compile your own, PM me and I can send you the version I made.

Dan

Hmm indeed, I tried to compile eepe before but didn't manage, turns out I was looking (way) too far, being used to building companion9x.
No problem building eepe here either then.

You've succeeded in building companion9x on the mac? Got any tips?

r347 now available, I managed to find time to update it a bit more. Thanks Erazz for compiling and releasing it, he is still active, just overworked at present (11 hour days).

Mike.

Hippo wrote:You've succeeded in building companion9x on the mac? Got any tips?

I remember writing a post right after it with some comments about what I had done, but I haven't been able to find it again after a quick search. Leave me a moment and I should find it!

Found it: viewtopic.php?f=28&t=906&p=12455#p12399

One thing is you need to use Xcode 4.1, later versions won't work. And as 4.1 won't run on Mountain Lion - if you've upgraded, you're screwed. I use a Lion virtual machine.