[ocemp-devel] Upcoming OcempGUI release notes.

[Marcus v. A. <ma...@sy...>]

Hi,

The OcempGUI API seems to be fairly stable, the most widgets are nearly
complete and the manual is in progress. Anything seems to be fine,
except that the next release will include some changes, which could
break exisiting code relying upon OcempGUI.

As you might have seen in the recent CVS notes, I changed some signal
type names to match the naming scheme. The following signal names changed:

SIG_FOCUS      -> SIG_FOCUSED
SIG_LISTCHANGE -> SIG_LISTCHANGED
SIG_VALCHANGE  -> SIG_VALCHANGED
SIG_SELCHANGE  -> SIG_SELCHANGED

It should be not a big deal as those signals are usually not heavily
used besides the OcempGUI internals.=20

Another substantial change was made in the signal handling. Low level
signals such as SIG_MOUSEDOWN, SIG_KEYDOWN, etc. now will send the event
data to the callbacks as well. Thus, code like

def mouse_callback ():
    ...

button.connect_signal (SIG_MOUSEDOWN, mouse_callback)

will not work anymore. Instead change the callback handlers to something
like

def mouse_callback (event_data):
    ....

so that the event data can be received by the callback. Take a look at
the ocempgui.widgets.Constants doc strings for details about which
signals send the event data.

Those will be the last changes, which break the API. All versions from
0.1.0 to <0.2.0 will at contain compatibility layers, that will not be
removed before 0.2.0, if incompatible changes, which might break
existing code, are introduced. I will try to avoid such changes, but if
they are necessary, you will not be in the need to adjust your code ;-).

The recent Pygame GUI comparision[0] of David Keeney brought up some of
those issues and to satisfy him a bit more, I added an ImageMap widget
class. Basically it is not very different from the ImageButton class,
but stores the last event it received and offers an absolute <-> relative
position conversion property. In a later version it also will
contain a keyboard control to move the cursor via the keyboard (on
demand), but this will not go into 0.1.0 anymore.

The last substantial changes were some heavy improvements in the drawing
logics. Some people reported a heavy CPU load on their linux systems,
which are fixed in CVS and thus should be vanished in 0.1.0 and later.

[0] http://pitchersduel.iuplog.com/default.asp?mode=3Dblog&month=3D10&year=
=3D2005

Regards
Marcus