v3.1.1 Support targets and the "Treadmill"
@kiki-ja @tidebre67 @DenB10
So as was pointed out in
- #294 , TB137 was just released. This is the Treadmill. For the release channel we are a day late and a dollar short as the American saying goes.
I did some testing on v137 and v139a0. While it was not exhaustive, so far everything worked including our more advanced features. Fortunately PrintingTools, unlike ImportExportTools has less exposure to core changes. For instance I already know ImportExportTools breaks in v137 which means I will probably lose a bunch of users.
If we can determine that v3.1.1 works through Thunderbird v138, then that buys us at least two months reprieve, at least you guys, I have to go like crazy on the ImportExportTools rewrite.
So I am asking if you guys are up to testing against v137 and I will do v138. I don't have the energy to make a real test plan, but we could split up by some bullet points. No new translations and key different features only.
As I said before, this RC is a good way to burn out developers and their crews (you Guys) and lose users on the RC channel.
So I am asking you for your opinions and thoughts. Thanks as always Christopher
@cleidigh b11 not compatible with v136 , therefore cannot make further tests at this moment.
Can understand that it will take a lot of energy to make monthly updates therefore i think to concentrate on current status of PNTNG. I am ready for further testings.
@tidebre67
@cleidigh tested b12 in TB128 and TB137. In general b12 works in both versions, only 1 issue, pdf-output in an OPEN message shows TB print style and not PNTNG style. Issue in both versions 128 and 137.
@tidebre67
@cleidigh, i cannot find the beta version to be tested in thunderbird 137 (windows 11). I'll be pleased to do my part of job
@tidebre67 thankss I'll start to test
@tidebre67 Thanks. When you say open, do you mean in its own window? I did test all the views and the thought they were good so once I understand what you mean I will jump on it. @cleidigh
@cleidigh , yes, open in a new Window. Pls look here, hope that clarifies.
@tidebre67
@tidebre67 Ok couple important things. First, we have two buttons in the independent message windo. Button one (your left arrow) is on what I will call the main toolbar (note we should find the correct terminology). Second is your right arrow in the message pane.
My first issue is I can't get the first button on the main toolbar. How did you? No PTNG shows in customize so I can't test that.
Button 2 works fine for me. @cleidigh
@cleidigh Christopher, all under customize.
in new open window Menu and Mail Toolbar:
on main screen (hope that is the correct naming) see the orange arrow:
on so-called main screen with orange arrow pointing to "Drucken NG" the print-out works correct, in both other options not. As mentioned the prints via Print Preview are working correct in all .
@tidebre67
@tidebre67 I don't get the ptng icon in the customize dialog at all, so I can't test that. The button in the message pane in a separate window works for me in both preview and pdf output. So we definitely have some debugging to do. I'm surprised at this big difference in behavior. Did you ever do a fresh install and use the customize buttons? I have mostly fresh installs and am wondering if the button got through an update on your side?
I'm getting an update out v14.1.8 IETNG for Thunderbird v137-138 tomorrow, then can totally focus on Ptng.
Do you get any console errors when the pdf output fails? And, can you move the button back and forth from the dialog to toolbar? @cleidigh
@tidebre67 I did some experiments and no luck. Then I was thinking, that button is completely redundant, why should we clutter that toolbar when it doesn't do anything extra for us? We still need to debug why your message pane button half works, but what do you think? @kiki-ja @DenB10 @pechh Any thoughts and do you see the problems @tidebre67 has? @cleidigh
@cleidigh @tidebre67
PrintingTools NG 3.1.1-b12 Thunderbird 137.0.1 64bit Windows 10 Pro 22H2 64bit
Any thoughts and do you see the problems @tidebre67 has?
Is it correct that problems means the following?
In general b12 works in both versions, only 1 issue, pdf-output in an OPEN message shows TB print style and not PNTNG style. Issue in both versions 128 and 137.
I tested the above in my environment.
This is an environment with only PTNG 3.1.1-b12 installed in the new profile.
The results of PDF Output by PrintingTools NG 3.1.1-b12 were normal.
Reproduction procedure:
-
Select a message in 3pane and click the Print NG icon button.
-
Click OK in the Autosave PDF dialog window.
-
A PDF file is output by PTNG and saved in the specified location.
Also, the PrintingTools NG icon button appears correct in the Customize Toolbars window.
On the other hand, if the same message is run through PDF Output again with the same procedure, nothing happens.
The error console log is attached.
[Console log] console-export-2025-4-6_18-30-11.txt
Thanks.
@kiki-ja
@tidebre67 I don't get the ptng icon in the customize dialog at all, so I can't test that. The button in the message pane in a separate window works for me in both preview and pdf output. So we definitely have some debugging to do. I'm surprised at this big difference in behavior. Did you ever do a fresh install and use the customize buttons? I have mostly fresh installs and am wondering if the button got through an update on your side?
I'm getting an update out v14.1.8 IETNG for Thunderbird v137-138 tomorrow, then can totally focus on Ptng.
Do you get any console errors when the pdf output fails? And, can you move the button back and forth from the dialog to toolbar? @cleidigh
@cleidigh no fresh installation always via updates. in general i only use printing via PRINT NG via the icon marked with orange arrow, and there is no issue. The issue only occurs in a new open window tab and When pushing the icon button the subject line appears for a short time in TB status bar at the buttom of the screen. All very strange.
@kiki-ja May you please make a check when open a message in a new window tab.
Btw:
On the other hand, if the same message is run through PDF Output again with the same procedure, nothing happens.
Presume that the same message cannot be stored in same folder at same date & time twice. @cleidigh , kindly check
@tidebre67
@cleidigh @tidebre67
PrintingTools NG 3.1.1-b12 Thunderbird 137.0.1 64bit Windows 10 Pro 22H2 64bit
May you please make a check when open a message in a new window tab.
The problem was reproduced only when the message was opened in a new window.(not 3pane and tab)
[Screenshot]
It did indeed become a Thunderbird Print.
[PDF Output screenshot]
Presume that the same message cannot be stored in same folder at same date & time twice.
Thunderbird Print can repeat the same message at the same date and time. And a sequential number is added to the end of the file name. I assumed that PTNG could do the same, but I guess I was wrong.
Thanks.
@kiki-ja
@kiki-ja @tidebre67 Well I think we are all confused given we have differing results, some that really confuse me. In particular the fact that both of you get the button in your customize dialog. I can't in any version or install.
We need to break out these into separate issues so we can track them better. I would like to eliminate one set related to the mail toolbar(the top of a open mail in separate window. As stated above it's redundant and unnecessary. So let's limit our concerns to the message window button right above the message. Marked with the blue arrow in @kiki-ja post above.
I think I will make a new issue for that button showing standard Thunderbird print not PTNG formatted AND failing on second print.
@cleidigh
@cleidigh @tidebre67 @kiki-ja
I must say I'm a bit confused. To tell the truth, I didn't understand everything.
I did some tests with PTNG 3.1.1-beta12 under Win7 with TB115 and under Win10 with TB128&136. In the main 3-pane window, whether using the main toolbar button or the message toolbar button, I get the expected result, but only once. If I repeat the action with the same message, nothing happens. I then have to change message or restart TB for it to work.
If I open a message in a new window, it's different. But I'll describe the behavior in the new issue that Christopher has opened.
@DenB10