toner

2001-10-01 Thread vortex2



 VORTEX SUPPLIES 

YOUR LASER PRINTER TONER CARTRIDGE,
COPIER AND FAX CARTRIDGE CONNECTION

SAVE UP TO 30% FROM RETAIL

ORDER BY PHONE:1-888-288-9043
ORDER BY FAX: 1-888-977-1577
E-MAIL REMOVAL LINE: 1-888-494-8597


UNIVERSITY AND/OR SCHOOL PURCHASE ORDERS WELCOME. (NO CREDIT APPROVAL REQUIRED)
ALL OTHER PURCHASE ORDER REQUESTS REQUIRE CREDIT APPROVAL.
PAY BY CHECK (C.O.D), CREDIT CARD OR PURCHASE ORDER (NET 30 DAYS).

IF YOUR ORDER IS BY CREDIT CARD PLEASE LEAVE YOUR CREDIT CARD # PLUS EXPIRATION 
DATE. 
IF YOUR ORDER IS BY PURCHASE ORDER LEAVE YOUR SHIPPING/BILLING ADDRESSES AND 
YOUR P.O. NUMBER


NOTE: WE DO NOT CARRY 

1) XEROX, BROTHER, PANASONIC, FUJITSU PRODUCTS
2) HP DESKJETJET/INK JET OR BUBBLE JET CARTRIDGES 
3) CANON BUBBLE JET CARTRIDGES 
4) ANY OFFBRANDS BESIDES THE ONES LISTED BELOW.

OUR NEW , LASER PRINTER TONER CARTRIDGE, PRICES ARE  AS FOLLOWS: 
(PLEASE ORDER BY PAGE NUMBER AND/OR ITEM NUMBER)

HEWLETT PACKARD: (ON PAGE 2)

ITEM #1  LASERJET SERIES  4L,4P (74A)$44
ITEM #2  LASERJET SERIES  1100 (92A)-$44
ITEM #3  LASERJET SERIES  2 (95A)$39
ITEM #4  LASERJET SERIES  2P (75A)---$54 
ITEM #5  LASERJET SERIES  5P,6P,5MP, 6MP (3903A)--  -$44
ITEM #6  LASERJET SERIES  5SI, 8000 (09A)$95
ITEM #7  LASERJET SERIES  2100, 2200 (96A)---$74
ITEM #8  LASERJET SERIES  8100 (82X)-$115
ITEM #9  LASERJET SERIES  5L/6L (3906A)--$39
ITEM #10 LASERJET SERIES  4V-$95
ITEM #11 LASERJET SERIES 4000 (27X)--$79
ITEM #12 LASERJET SERIES 3SI/4SI (91A)---$54
ITEM #13 LASERJET SERIES 4, 4M, 5,5M-$49
ITEM #13A LASERJET SERIES 5000 (29X)-$125
ITEM #13B LASERJET SERIES 1200---$59
ITEM #13C LASERJET SERIES 4100---$99
ITEM #18   LASERJET SERIES 3100--$39
ITEM #19 LASERJET SERIES 4500 BLACK--$79
ITEM #20 LASERJET SERIES 4500 COLORS $125

HEWLETT PACKARD FAX (ON PAGE 2)

ITEM #14 LASERFAX 500, 700 (FX1)--$49
ITEM #15  LASERFAX 5000,7000 (FX2)$64
ITEM #16  LASERFAX (FX3)--$59
ITEM #17  LASERFAX (FX4)--$54


LEXMARK/IBM (ON PAGE 3)

OPTRA 4019, 4029 HIGH YIELD---$89
OPTRA R, 4039, 4049 HIGH YIELD---$105
OPTRA E310.312 HIGH YIELD$79

OPTRA E---$59
OPTRA N--$115
OPTRA S--$165
OPTRA T--$195


EPSON (ON PAGE 4)

ACTION LASER 7000,7500,8000,9000--$105
ACTION LASER 1000,1500$105


CANON PRINTERS (ON PAGE 5)

PLEASE CALL FOR MODELS AND UPDATED PRICES
FOR CANON PRINTER CARTRIDGES

PANASONIC (0N PAGE 7)

NEC SERIES 2 MODELS 90 AND 95--$105

APPLE (0N PAGE 8)

LASER WRITER PRO 600 or 16/600--$49 
LASER WRITER SELECT 300,320,360-$74
LASER WRITER 300 AND 320$54
LASER WRITER NT, 2NT$54
LASER WRITER 12/640-$79

CANON FAX (ON PAGE 9)

LASERCLASS 4000 (FX3)---$59
LASERCLASS 5000,6000,7000 (FX2)-$54
LASERFAX 5000,7000 (FX2)$54
LASERFAX 8500,9000 (FX4)$54

CANON COPIERS (PAGE 10)

PC 3, 6RE, 7 AND 11 (A30)-$69
PC 300,320,700,720,760,900,910,920(E-40)--$89


90 DAY UNLIMITED WARRANTY INCLUDED ON ALL PRODUCTS.

ALL TRADEMARKS AND BRAND NAMES LISTED ABOVE ARE PROPERTY OF THE 
RESPECTIVE HOLDERS AND USED FOR DESCRIPTIVE PURPOSES ONLY.







--
Visit the official FVWM web page at URL:http://www.fvwm.org/.
To unsubscribe from the list, send unsubscribe fvwm-workers in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]


Re: Notification: incoming/785

2001-10-01 Thread Dominik Vogt
On Fri, Sep 21, 2001 at 05:48:16AM -0500, fvwm-bug wrote:
 FVWM Bug Tracking notification
 
 new message incoming/785
 
 Full_Name: John Heaton
 Version: 2.4.2
 CVS_Date: 
 OS: SuSE 7.2 - kernel 2.4.9
 X_Server: xf86-4.0.3
 Submission from: (NULL) (194.82.103.145)
 
 
 I have just upgraded FVWM from 2.4.0 to 2.4.2 and have noticed that the
 image from FvwmBanner has aqquired a black background and a window border,
 in orther words the Shape extension handling seems to have been broken.
 
 I compiled up both 2.4.0 and 2.4.2 in exactly the same way without any
 special options on the configure stage.  The shape extension works fin with
 2.4.0 but not with 2.4.2.
 
 I have checked the FvwmBanner out with the standard .XPM file and one that
 I normally use, both show the black background/border with 2.4.2.

Thanks for the report, the bug will be fixed in the 2.4.3 release.

Bye

Dominik ^_^  ^_^

 --
Dominik Vogt, [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
--
Visit the official FVWM web page at URL:http://www.fvwm.org/.
To unsubscribe from the list, send unsubscribe fvwm-workers in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]


Re: Some Xinerama problems

2001-10-01 Thread Dominik Vogt
On Fri, Sep 28, 2001 at 05:23:18PM +0200, Olivier Chapuis wrote:
 Hello,
 I make some Xinerama test recently using Sls 1x2 on
 my poor 800x600 screen:
 
---
   |   |   |
   |   0   |   1   |
   |   |   |
---
 
 The support seems really great! (BTW, does there exits
 laptop with a double head video card?).
 
 I've noted a few problems with menu position and IconBox
 
 1. if WindowList is called without argument as well as
 if a menu key binding of the form
Key key Context Modifier Menu MyMenu _No_arg_
 is activate, then the window list (or the menu) always
 popup on screen 0.   

Fixed.  With just the WindowList commands without any options,
the screen was not set correctly.

 2. For testing let say we have the following binding:
 
Mouse 1 A M Menu MenuFvwmRoot Rectangle [EMAIL PROTECTED] +0 +0
 
 (the @c is not really important). So when I activate this
 bindings the menu popup at [EMAIL PROTECTED] but if I am on screen
 0 and I popup submenus (and subsubmenus) then the menu
 go into screen 1 (so it is exactly as if I've no XineramaSls
 support). This does not happen on screen 1 (but here the
 left limit is my monitor).
 Similarly if I use:
 
Mouse 1 A M Menu MenuFvwmRoot Rectangle [EMAIL PROTECTED] +0 +0
 
 (and MenuFvwmRoot is larger than 10p) the menu appear in between
 screen 0 and 1 as it should appear on screen 0 (as it will do
 with [EMAIL PROTECTED] on screen 1).

Fixed.  Originally, rectangles referred always to the global
screen.  Now, the screen part of the geometry also confines the
menu into that screen (defaulting to the primary screen).

 3. It seems natural for me that iconification happen on the
 current screen, so I test IconBox with 
 
 Style * IconBox [EMAIL PROTECTED], IconGrid 64 10, IconFill left bottom
 
 In normal use this work fine. However, if the above command
 is entered in a way or an other when the mouse cursor is on
 screen 1 the icons on screen 0 go in a random location (in the
 top of screen 0).

You are misinterpreting what your style line does: it creates an
icon box with the given dimensions on whatever screen the pointer
is on at the time the style command is issued.  It *does not*
create one icon box on each screen: this must be done manually.

What fvwm does is this:

 - Create a default icon box that covers the primary screen.
   (screen 0).
 - Create the given icon box on the screen with the pointer.
   (screen 1).

Whenever a window is iconified, fvwm looks for a suitable icon box
in this order:

 - Icon boxes that intersect with the screen of the window.
 - Any icon box other than the default icon box on any screen.
 - The default icon box.

So, what you are seeing is icons being placed in the default icon
box on the primary screen since this is the only box that
intersects the primary screen.  You have to specify a separate
icon box for each screen.

Of course it would be nice to have a way to specify the same icon
box for each screen in a single style command, but I don't see how
this can be done easily (most of the icon box calculations are
still in style.c).

 Similar things happen with
 
 All (CurrentScreen Iconic) RecaptureWindow
 
 Also if I have a window which is almost all in screen 1
 and if I Iconify it with a title button on screen 0, then
 the icon go in a random location. More important, if
 I have a window on screen 1 and if I Iconify it with IconMan
 which is on screen 0, then again the icon go in a
 bad location (in screen 0).
 
 In the above, screen 0 and 1 are interchangeable.
 
 I've not investigate problem 2.  3. I may take a look
 if no other (more competent than me for these) have the
 time to fix it (before 2.4.3?).

Bye

Dominik ^_^  ^_^

 --
Dominik Vogt, [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
--
Visit the official FVWM web page at URL:http://www.fvwm.org/.
To unsubscribe from the list, send unsubscribe fvwm-workers in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]


Re: RelieveRectangle: called with w = -10, h = 1

2001-10-01 Thread Dominik Vogt
On Sat, Sep 29, 2001 at 08:42:14PM -0700, Elliot Sowadsky wrote:
 fvwm prints out RelieveRectangle: called with w = -10, h = 1
 
 when i resize my mailtool winow.
 Message started w/ 2.4.2 i believe.

I added this debug output some time around then since I thought
calling functions with illegal arguments isn't a good idea.  Can
you try to find out which piece of decoration causes this message
by disabling the title buttons, the title and the border
successively?  Unfortunately I don't have access to mailtool
myself.

 The function works as intended tho.
 
 
 
 AddToFunc Max2Size
 + I Maximize
 + I ResizeMove $0p $1p $2p $3p
 + I Resize br w-10p w-27p  # account for borders and title
 
 AddToFunc Tile
 + I Resize 0 0
 + I Maximize grow grow
 + I Max2Size $[w.width] $[w.height] $[w.x] $[w.y]
 
 Mouse 1   T   SC  Tile

Bye

Dominik ^_^  ^_^

 --
Dominik Vogt, [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
--
Visit the official FVWM web page at URL:http://www.fvwm.org/.
To unsubscribe from the list, send unsubscribe fvwm-workers in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]


CVS domivogt: * Xinerama fixes for bugs reported by Olivier in menu code, WindowList.

2001-10-01 Thread FVWM CVS
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt01/10/01 16:07:03

Modified files:
.  : ChangeLog NEWS 
fvwm   : add_window.c builtins.c events.c fvwm2.1 
 icons.c menus.c move_resize.c placement.c 
 stack.c update.c windowlist.c 
libs   : FScreen.c FScreen.h 

Log message:
* Xinerama fixes for bugs reported by Olivier in menu code, WindowList.
* Applied Xinerama patches by Sidik (partially rewritten).
* Removed useless code pointed out by Suzanne Britton.
* Fixed flickering icon titles.

--
Visit the official FVWM web page at URL:http://www.fvwm.org/.
To unsubscribe from the list, send unsubscribe fvwm-workers in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]


re: RelieveRectangle: called with w = -10, h = 1

2001-10-01 Thread Elliot Sowadsky

 fvwm prints out RelieveRectangle: called with w = -10, h = 1

Resize generates the message if the sticky title text does not fit in the
resized title bar.

Non-sticky doesnt print the message.

Resize 0 0 was what i originally had that generated the message.

Resize 250p 0  was a little past the end of the text and gave
RelieveRectangle: called with w = -2, h = 1

Resize 260p 0  was further past then end and gave no warning.
--
Visit the official FVWM web page at URL:http://www.fvwm.org/.
To unsubscribe from the list, send unsubscribe fvwm-workers in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]