xfpager, and general observations

Dmitry DELTA Malykhanov d726f6e at SDF.LONESTAR.ORG
Mon Aug 19 07:52:42 CEST 2002


OK, just a short explanation. Those prefix numbers are just xfpager
process id. I've added this to distinguish output of the differnt xfpager
instances. Please see below my comments to the output.

On Sun, 18 Aug 2002, Harry Putnam wrote:
> Dmitry DELTA Malykhanov <d726f6e at SDF.LONESTAR.ORG> writes:
>
> > Once you will have the modifed xfpager installed, just do the usual thing
> > -- restart xfwm/xfce (keep your xfwmrc file the same, and keep checkbox
> > checked), and post the XFPAGER.LOG here. NOTE: my code will create
> > XFPAGER.LOG file in /tmp
>
> For the record.  A restart shows this in the log.
> Should the prefix number be the same like that?
>
> cat /tmp/XFPAGER.LOG
>
>   22517: ClickTime 300
>   22517: length = 14
>   22517: *xfpager.geometry 170x120+1141+1050
xfpager was able to establish communication with xfwm process and
request configuration parameters

>   22517: length = 36
>   22517: ParseOptions geometry spec '*xfpager.geometry 170x120+1141+1050
>   '
it found string describing the desired geometry

>   22517: ParseOptions() geometry '170x120+1141+1050'
>   22517: *xfpager.font 9x15
>   22517: length = 19
>   22517: MyName = 'xfpager'
>   22517: ParseOptions() window_x = 1141 window_y = 1050
internal variables have been initialized with the proper values (it
matches the geometry description from above)

>   22517: initialize_pager() hasConfig = 1
>   22517: initialize_pager() window_x = 1141 window_y = 1050
this happened right before asking X server to create a new window for
xfpager. requsted location matches the geometry specification.

Everything works as expected!

--
It's me -- Delta at SDF Public Access UNIX System - http://sdf.lonestar.org

"I don't advise it, citizen, mn-e-eh... I don't advise it. You'll be eaten."




More information about the Xfce-dev mailing list