On Mon, May 2, 2011 at 2:06 PM, Stefan Gofferje
<address@hidden> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/02/2011 03:58 PM, Tom Rondeau wrote:
> It's the way it is because it's the way that it's always been. But as
> I'm splitting out the various graphs to become their own stand-alone
> elements and will eventually allow you to create a GUI figure that
> doesn't have the box of "stuff" around it, you won't necessarily see the
> "display RF frequencies" check box. In that case, I think you're right
> that it makes more sense to default to what the user told it the center
> frequency is.
How about making it a parameter? The user can set it as needed then and
if desired create a QT radiobutton to change it in-app.
It is a parameter, or at least settable by sending the right signal through the QT API. My plan is to expose everything that we might want to adjust as a slot as well as a function in the GR block for these sinks. That gives us multiple ways to set and read these things. Setting this would be one of those functions/slots. I don't think that I would add it as an actual argument to the constructor, though; it doesn't really seem important enough for that. As these GUIs are improved, I think I will make the RF frequencies the default behavior and you can always call the "display_rf_freqs(False)" (or whatever) from the object you've created.
Tom
- --
(o_ Stefan Gofferje | SCLT, MCP, CCSA
//\ Reg'd Linux User #247167 | VCP #2263
V_/_ Heckler & Koch - the original point and click interface
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
iEYEARECAAYFAk2+rE4ACgkQbQKZlCdPOMMWoQCfbU20t+j/AWaV+c1MoQIrU+Qx
uNsAniGQTwph5n7fTQ19rsLDdqB2EbSL
=2Dq7
-----END PGP SIGNATURE-----