Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

The Code Repository

33 views
Skip to first unread message

Scott Hibbs

unread,
Jul 18, 2013, 9:50:23 PM7/18/13
to fd...@googlegroups.com
Alan,

   I'm not sure if I'm using the TortoiseHg Workbench correctly... I committed some changes I made to the GUI... I'm far from finished with it... Anyway, I wanted to make sure you got it. Could you email me?

  And to let you know that the test version is not reading from the sequel equivalent of what used to be the "fdlog.dat" file.

I've used the program for the last two years and love it.

I really hope you like my changes.

Thanks!

Alan Biocca

unread,
Jul 20, 2013, 10:13:12 AM7/20/13
to fd...@googlegroups.com
Hi Scott,

Just noticed your email.

The .dat file is being retired.

What changes did you make?

-- Alan




--
You received this message because you are subscribed to the Google Groups "HS-FDLog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fdlog+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Scott Hibbs

unread,
Jul 20, 2013, 11:20:10 AM7/20/13
to fd...@googlegroups.com
Hi Alan,

    I committed the changes using TortoiseHg but not sure I'm using it right.
I need to know if you got my changes with TortoiseHg.

I've done the following:
rearranged text to show where to type log entries (I didn't know on my first load)
Added red to the buttons to show these need values before logging contacts
Added database protection against no band, no power, no op, or no logger
   Even testing, there is no reason to enter incomplete records into the log
Switched operator buttons and logger buttons for station qso counts 
Added Qso count for the operator and log count for the logger.

   I did all of the changes using the stable release and then noticed the 
new sequel edition when I set up TortoiseHg. When I say I switched buttons,
I simply mean that I made the "Operator" button and "Logger" button
to be after the names so that they could update with the qso counts.

   Since then, I've started going through some of the "to do" list at the bottom
of the code. I've made even more changes to the GUI (hoping to eventually have a box
or entry window to type entries) and I've played around with making a 1D version
but it seems that Tkinter displays the 1D at the top but takes the global value
of "2A" instead from the code and not from what used to be the dat file.
Also, the GUI now takes the value of already having a
operator and logger present (from the newer dat file?) if there is one but
doesn't turn the buttons grey like it used to. Otherwise it works.
It could be something I've changed but I'll find a way to fix it.

I'm having a blast with the program and learning Python. And I hope you like my changes.

73
Scott KD4SIR

Alan Biocca

unread,
Jul 20, 2013, 11:38:39 AM7/20/13
to fd...@googlegroups.com
Hi Scott,

I haven't checked the Google Code repository but I suspect your changes may just be in your local repository. It is a bit tricky to get them published into the Google Code repository.

Sounds like some nice changes. The version we used on FD this year is beyond the version in Google Code, I've added a TCP capability that allows synchronization over the internet, and added Cabrillo output for the VHF contest.

I've run out of time to work on it at the moment, but hope to get back to it soon.

Python is very nice. I enjoy what little time I get to spend with it. It has evolved significantly since FDLog was written, I need to update the whole code at some point.

One bug that we need to find is intermittently it seems to miss a dup log entry. I have seen it happen but haven't been able to reproduce it on cue.

73, Alan



Scott Hibbs

unread,
Jul 20, 2013, 12:09:52 PM7/20/13
to fd...@googlegroups.com
Alan,

   I found the button to "push" my changes to the repository but it is asking for a username and password which I don't have. So instead I've zipped the file which I
attached.

Scott


--
You received this message because you are subscribed to a topic in the Google Groups "HS-FDLog" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/fdlog/_6CX7Itdzj8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to fdlog+un...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
Scott

I get $3 trades at Sogotrade and recommend them for you. Live the American dream. Own Stock.
https://www.sogotrade.com/NewAccountSetup/Step1.aspx?rf=563893
fdlog.zip

Scott Hibbs

unread,
Jul 25, 2013, 9:59:22 PM7/25/13
to fd...@googlegroups.com
Alan,

    I figured it out. Looks like I need to be added as a user of your group (with committer priviledges) to send code to the group...  Otherwise no one will be able to help you unless they did what I did and zip the file and email it to you. (see http://code.google.com/p/support/wiki/Permissions - the second paragraph for more info)

    Let me know if you liked the changes.

Scott
fdlog.zip

Alan Biocca

unread,
Jul 25, 2013, 10:57:36 PM7/25/13
to fd...@googlegroups.com
Hi Scott.

Sorry, haven't had a chance to look at them yet.

-- Alan


Reply all
Reply to author
Forward
0 new messages