lucidity | A framework for managing filesystem

You don't need all that complex server-side C# code to wrap text in a listbox in asp.net. All you need is some special CSS. For example, the below CSS will automatically wrap text in an asp.net listbox.

Wrapping will automatically occur if the width you mention in below CSS is not enough to fit the text of listbox option.

CSS to wrap text in Listbox

It sounds to me like you want to use some kind of exponential or logarithmic scale to represent the relative magnitudes between the values. This will effectively give small numbers a 'boost'. In your code, you'll need to calculate the min and max based on the scaling method instead of their original values.

Picking a method that looks 'good' for your circumstances would be subjective and I don't know the context of the data you're graphing, but here are some examples of how a few methods might look (plotted using data bars in Excel).

• On the first row, we have Math.pow(x, y) for 0 > y > 1.
• On the second line we have Math.pow(Math.log10(x + 1), y) for y > 1

This is standard SQL behavior.

https://mariadb.com/kb/en/library/sql-99/order-by-clause/ says in part:

An ORDER BY clause may optionally appear after a query expression: it specifies the order rows should have when returned from that query (if you omit the clause, your DBMS will return the rows in some random order).

(emphasis mine)

It'd be more accurate to say it will return the rows in some arbitrary order, instead of random order. Random implies that the order will change from one execution to the next.

• In the case of InnoDB, the order tends to be the index order in which the rows were accessed. The index it reads is not necessarily the primary key. So the order is unchanging and somewhat predictable if you know something about the internals. But it's not random.

• In the case of MyISAM, the order tends to be the order the rows are stored in the table, which can vary depending on the order the rows were inserted, and also depending on where there was space in the file at the time of insertion, after row deletions.

• In the case of NDB, I don't know as much about its internals, so I can't describe its rule for "default" order, but it's still true that without an explicit ORDER BY, the storage engine is allowed to return rows in whatever order it wants to.

It should be:

How would this be turned back into a BouncyCastle ... PGPSignature object?

Extracting the relevant code from org.bouncycastle.openpgp.examples.DetachedSignatureProcessor provided in the bcpg jar and specializing it to your case (armored, uncompressed):