Peter,
Export is essentially a batch process, you want this to attempt to
complete if possible. We don't however want 500 popups of warnings if
your 5000+ entries are flawed.
I'm more inclined to export what we can then create a "not imported"
file with the error entries, and a final popup with a info and a link
to it.
You get the export, plus known problem entries to fix before you try
again.
I need to dig in the code to see for sure though.
Comments?
Chris K6RWJ
Sent from my iPhone
On Mar 8, 2010, at 17:49, "Peter N. Spotts" <[email protected]> wrote:
On Mon, 2010-03-08 at 09:36 -0600, Christopher Story wrote:
We need to get this one in Savanna bug reporter, so it doesnt get
overlooked.. also if possible to create a sample for testing it would
be great. understanding of course that we *could* create our own
test
file, there is nothing like a real one..
http://savannah.nongnu.org/bugs/?group=xlog
Chris
K6RWJ
Hi Chris,
Since the "bug" was of my making, perhaps the only way of dealing with
this (short of me improving my typing!) is to have text in the
frequency
field show up in red if a user enters an out-of-band frequency --
something akin to the response a spell checker gives in a
word-processing program. Other than that, I'll mind my fingers and
thumbs!
With best regards,
Pete
--
Peter N. Spotts -- W1PNS
http://www.w1pns.net
Email: [email protected] | Skype: pspotts
QCWA #34679 | SKCC #4853T | QRP-ARCI #4174
NEQRP #714 | NAQCC #2446 | WARC-CC #147
_______________________________________________
Xlog-discussion mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/xlog-discussion
