LCDproc development and user support list

Text archives Help

[Lcdproc] lcd-nut patches offered; made to work with NUT v2

Chronological Thread 
  • From: joris AT (Joris Robijn)
  • Subject: [Lcdproc] lcd-nut patches offered; made to work with NUT v2
  • Date: Sat Mar 18 17:16:02 2006

On 18 Mar 2006 at 6:26, Andrew Foss wrote:

> It could the priority your client is setting.
> In 0.4.5, the priority scale was 0-250, 0 being highest, now it's 0-6, 6
> being high. I'd try removing the Priority statements from your client,
> let the server give you the default priority, otherwise you can try

Currently it is a enum. The docs state:

screen_set -priority pri_class

Sets the screen's priority. The following priority classes exist:

screen will never be visible

only visible when no normal info screens exist

normal info screen, default priority

an active client

screen has an important message for the user

the client is doing interactive input

An int is also supported for backwards compatibility, but it only maps to
the background, info, or foreground classes.

Success with your app.


Joris Robijn
<joris AT>
Mobile: +31 6 288 41 964

Archive powered by MHonArc 2.6.18.

Top of page