I've noticed that when using Jxbrowser's default print dialog (using JxBrowser version 6.7) and printing a document with many pages, the page selection only goes up to 100 pages.
When you type in more than 100, it reverts back to the previously set number and you can't increment to more than 100.
Is this just me?
I am here to inform you that we’ve just released JxBrowser 6.14 where the mentioned issue has been resolved.
This version is available for downloading at https://www.teamdev.com/jxbrowser
I'm writing you to let you know that the issue has been fixed. You can download EAP build with the fix from https://storage.googleapis.com/cloud.teamdev.com/downloads/jxbrowser/eap/jxbrowser-6.14-b13-eap-cross-desktop-win_mac_linux.zip
The fix will be included in official 6.14 release probably this month.
Related
I am using Maximo 7.6.1.1 and Birt (eclipse 4.3.1). The requirement is to add some page related text with a field from the report into the footer on each page, so I am attempting to update the master page footer. The master page is local, not extended.
I have tried to repeat this from 2013 (https://www.youtube.com/watch?v=lw_k1qHY_gU&t=4s) without success.
So using page level variables as described by the link did not work - it appears that the page event for the variable I chose (when the variable is about to be updated on the page) did not seem to be getting invoked.
Has this possibly changed (since 2013) or does someone know of another work around?
I tried to add a number of data elements to the footer without success.
I did see that if I added a value to the footer element in the initialization event for the report, that we could see that but we never got any updates even though the field we wanted to use was updated as it is normally.
I don't know Maximo, but these page variables only work if BIRT is running in 2 steps: RunTask, then RenderTask. If the program is using the single-step RundAndRenderTask, page variables don't work. This behaviour has not changed with "newer" BIRT releases.
I had been happily using Java live reload while debugging my Vaadin application over the past few months.
Today, after I started my browser and directed it to my locally running Vaadin application I got a popup in the lower right corner stating:
Java live reload unavailable. Live reload for Java changes is currently not set up. Find out how to make use of this functionality to boost your workflow. Read more
Clicking onto the read more link (pointing to 'https://vaadin.com/docs/v14/flow/workflow/workflow-overview') just brings me to a "404 Page Not Found" error page.
So - two or actually three questions:
what could cause my live-reload functionality go missing? I am using MS Edge and the Live-reload plugin is enabled (and it used to work until yesterday).
where has the page gone explaining how to set that up?
and finally: Any idea, what to check or fix to get this working again? I consider that pretty essential functionality for efficient UI development!
For question 2, you can find the documentation here: https://vaadin.com/docs/v14/guide/live-reload
Currently i am facing issue with URL automatic redirection after the update Wordpress version 5.5 from 5.4. my URL is like http://localhost/testpage/214554 and last segment(214554) is my custom number that I have stored in database. and I have assigned one page template on testpage and through this number segment I have fetch data from the database and it was working fine till version 5.4 but after the updated version 5.5, When I try to load above url then last number segment is gone automatically and redirecting to the http://localhost/testpage instead of http://localhost/testpage/214554 so can you please help me to resolve my issue. It will good for me if anyone know how can I overcome from this issue.
in my app I use webview with many local HTML files. When the app is running over Android version 4.4.X or newer, the performance of scroll worsened and the text selection ceased to function properly. Looking for a solution, I saw that to solve this problem the Appcelerator docs recommend to set borderRadius property to a value greater than zero (the problem is associated with rendering on Chromium). Indeed, when I set borderRadius to 1, the scrolling performance is better and the text selection works well, but the quality of text (pixel) worsened and the users are complaining rightly. I'm using Titanium SDK 5.0.2GA and 23 platform API. I tried too using 5.2.2GA and 5.3.1GA but with the same results. I spent many hours to find a solution but without success. Please, someone can help me? I have been desperate. Many thanks in advance.
I found the problem and solution. In tiapp.xml, in the tag manifest, there were parameter android:anyDensity with value to "false". When I changed to "true", the scroll of webviews became very quick. In other hand, I needed to change all app's interface because this change caused change of all UI reference. But, after many hours of adjusts, finally the app is OK. Thanks.
After upgrading Jenkins from 1.547 to 1.583, when viewing a job's Console Output, it stopped updating the text automatically. That is, in order to see the latest text, I now have to continuously refresh the page.
The issue was with the plugin TimeStamper.
It needed to be upgraded to 1.5.13, and the issue was documented here: https://issues.jenkins-ci.org/browse/JENKINS-23867
I am posting the solution here so that others will know what to do.