Logger32 - Mały problem

[quote=sp5it]ZL2IFB opublikował na liście dyskusyjnej L32 trochę szczegółów na temat nadchodzącej wersji 5: Behind the scenes, finding itself at a loose end, Logger32’s “support” team has kept busy by elaborating on potential functional requirements for the next major release. Here is the outline spec so far … Enhanced callsign filtering Logger32 users will be able to filter out a wider range of 'unwelcome' callsigns from the bandmaps, such as: Novices Extras Stations known to be using robots Stations suspected of being robots Operators that should be in bed, fast asleep Anyone who doesn't upload logged QSOs to LoTW/QRZ/eQSL/another other log within [N] milliseconds Known cheats Suspected cheats Alleged cheats Potential cheats Anyone called “Vlad” DX spots with offensive comments DX spots with inoffensive comments DX spots with "funny" comments or “cute” callsigns DX spots without comments Artificial intelligence capabilities An AI capability that learns: Which kinds of DX spot we normally click, and clicks them for us if we are 'otherwise engaged' Which kinds of DX spot we don't normally click, and quietly drops them from our bandmaps The style of our DX spot comments, generating and posting realistic DX spots automatically for us The kinds of errors we normally make while logging, and makes more of them to 'customise' our logs Voice commands Using a PC headset or mike (as well as the one on the radio, if any), users can tell Logger32 what to do e.g. "Go to one-sixty" QSYs to the 160m band "Go to topband" QSYs to the top-most band on the bands-n-modes table "Go to hell" puts the rig into tune mode for 30 seconds "Call FO0L on 14030 CW" generates and sends the CW message on the stated frequency "Call FO0L spleeeet" figures out where FO0L is currently listening and starts calling him split “Call FO0L” chains 6 messages calling FO0L on her frequency "Log P5DX" logs a QSO with P5DX, regardless of which station we are allegedly working "Insurance contact" makes another call to the station we’ve just logged, just in case "UP, YOU IDIOT, UP!" temporarily disables our transmitter for a mandatory cooling-off period, quietly ensuring that we are operating split "Bedtime" closes down the station and PC in an orderly fashion “Night night” puts the PC into sleep mode, dims the lights and plays gentle muzak “Wakey wakey” fires up the coffee machine, clears the decks, checks SolarHam.net, updates all software and data files, optimises all databases, cleans the register, connects to a dozen DXclusters plus SDR Skimmers, strokes the CAT, reviews the overnight activities and cluster spots for anything of interest or concern, sends QRV messages on all known social media, checks which satellites might be coming into range, prepares QSL labels for yesterday’s QSOs, prints another QSL card box and generally gets itself ready for what little remains of the day’s DXing ahead “Stop messing me about” forces Logger32 to reconsider its purpose, its very being, it’s id "Oh shit!" stops and reverses whatever Logger32 was doing at the time "No, not that" re-does whatever it was doing before and stops/reverses something else instead “Not that either!” does the same again, only this time stopping and reversing twice as many things as before “OH FFS!!” installs Windows Vista with the /noninteractive parameter, then bricks the BIOS “Turnitoffandonagain” closes and restarts Logger32, sending a vague complaint and veiled threat to the Hamlogger reflector Further v5 suggestions are very welcome. Those written on Famous Grouse tokens qualify for “special” consideration. 73 Gary ZL2iFB[/quote] Zapomnieli o interfejsach do ekspresu do kawy i lodówki

  PRZEJDŹ NA FORUM