PureBasic Forums - English

Wow! You've outdone yourself TI-994A!

I've not used PB in a while now but I could have really used this tool a few years back.

I quickly tested in with the free demo version of PB and was surprised that it worked. Keep up the magnificent work.

Anyone familiar with the CUPS API can help me with using this function to set the default printer:

cupsSetDefaultDest

http://www.mit.edu/~mkgray/project/silk ... efaultDest

Thank you in advance!

PB5.42LTS x86, Win7x86
Well, I expected problems to arise because PB usually expects a Start to be followed with a Stop, but I don't know if that is the case in this instance. Certainly if another StartPrinting() is called after getPaperSize(), no harm seems to have been done, but since the print ...

If the first set of results you show on OSX really is with a 600 dpi setting then that must go down as a bug. I'd report that if I were you.
If the settings are correct. There is no default settings as with Windows, but the default print settings being used show the dpi as 600. I could only check ...

On Windows:
PrinterPageWidth() = 4760
PrinterPageHeight() = 6814

VectorOutputWidth() = 4771
VectorOutputHeight() = 6803

The Windows results are not accurate if the DPI is exactly 600 (is it 600dpi for Height also?).
.... and the VectorOutputWidth() should not be greater than PrinterPageWidth ...

wilbert wrote:It could have to do with a retina display where there's a difference between physical and logical pixels.

Would the retina display make a difference with the printer resolution though?

Why does VectorOutputWidth and VectorOutputHeight give different results for the same printer having the same paper settings for #PB_Unit_Pixel at 600dpi?
On Windows:
PrinterPageWidth() = 4760
PrinterPageHeight() = 6814

VectorOutputWidth() = 4771
VectorOutputHeight() = 6803

On OS-X ...

You would expect it to be a problem (by the way, your procedure does call StopPrinting())
If the app is only for Windows, a wealth of information can be collected from the printer via the API.
Hi IdeasVacuum. StopPrinting is not called because the procedure exits before reaching it. And the ...

This code works to return the printable area but exits without calling StopPrinting so as not to eject a blank page. The print job flashes briefly in the spooler window but gets removed as soon as the procedure returns: Procedure getPaperSize()
If PrintRequester()
If StartPrinting("Vector Printing ...

I agree that it is good to check the events before sending to the window. But I do not underatnd the flickering part and I have not seen this before. Do you have a example to show this because it might be a bug.

Not just good to check events but to check that the event is a valid PureBasic event ...

If there's flickering on any unintended gadget or window:

i. the event did not fall through

ii. it's the result of poor or faulty programming

iii. it's an error to be rectified; not an effect to be overcome

i. The event did fall through. That is one of the points.

ii. When you consider it all ...

Hit a problem, I noticed some strange effects on some windows and in tracing what was happening I asked for help and found that the return value of EventWindow() is only valid after a Valid PB event. Waitwindowevent and windowevent return ALL window events whether valid PB events or not, but these ...

@collectordave: Why do you check for valid pb events? I am trying to understand the reason.

...why do you open the window and image gadget twice?
Thanks, fromVB. Glad you find it useful.

Rather than fiddling with desktops, the simplest approach would be to obtain the full-screen dimensions from a maximized window. This saves a lot of hassle, especially if there are multiple desktops ...

deseven wrote:My attempt to create a notification system.

Thanks deseven. Great code!

One question: what is CreateMutex used for in your code?