[Gambas-user] Very strange printing problem + SHELL

[Eilert]

Benoit Minisini schrieb:
> On Thursday 04 May 2006 12:08, Eilert wrote:
>> This turned out much too complicated, as my printing module is way too
>> large and has many (strange) ways of printing here and there... ;-)
> 
> It is not too complicated, it just one line of code more. 

In this case, unfortunately it's more than that. I tested it. Using 
several ways of printing for 1 print, several prints, and lists, with a 
copy or a second page or several pages etc. makes the printing module of 
my app somewhat tricky. So, for example, kprinter popped up, claimed 
some bug ("cannot be done this way..."), but at the same time it printed 
in the background, kprinter popping up several times, writing only the 
last page into the file and so on... :-)

With the help of an access control list I could achieve that my app 
writes files with correct rights into its directories, so the problem 
seems to be solved for now.

> Anyway, printing to 
> a printer may disappear in a next release, you will be able to only print to 
> a file. And other components will add support for printing and configuring 
> printers.

In a next release of 1.0 or of 1.9?

I still cannot get the 1.9 edition appear on the screen here. The last 
one which I got and is running without problems is 1.9.24. The problem 
appeared with the last two releases (I think when you introduced MDI).

>> I think you know that program, we've discussed this before. I just
>> wanted to tell that it still doesn't run flawlessly.
> 
> Can you send me this application again?

Not necessary anymore. Yesterday I invented a new method of handling: 
Now a script calls "who" every 10 seconds and writes the output into a 
file. My app reads this file every 10 seconds. After an hour or so, the 
script (!) stopped, the Gambas app continued going on, reading from the 
same old file again and again. So it seems to be a bug or a feature :-) 
of "who" to hang after so and so many calls.

Currently, I'm running the script with "set -x" to watch where it might 
stop if it does. The system runs on full load, but both the script and 
my app are still running since about 8:45.

Regards

Rolf