When using the Ctrl+I Implement Methods dialog and choosing "Show abstract
methods only" and then selecting a couple of methods to implement, netbeans adds
these methods to the current source file in reverse order. Example:

I have an abstract super class containing two methods
	public abstract List<V> getSelectedValues();
	public abstract void removeDeletedValues(List<V> deletedValues);

These methods are listed in this order because they are invoked in this order -
first the getSelectedValues method is invoked and then removeDeletedValues is
invoked. However, when implementing these methods using Ctrl+I you get the
following source code:
	public void removeDeletedValues(List<V> deletedValues) {
	}
	public List<V> getSelectedValues() {
	}

You might argue that the code above is still correct code, but I will argue that
it is less readable. If your abstract base class has several methods, ordering
them in a logical manner becomes crucial and therefore NetBeans should not
tamper with the order specified by the developer.

Yours
Randahl