Tim: The tiny print problem is exactly the reason why the client wants to do the update. They've had people running it on Win10, unbeknownst to me, for about a year but, as you posit, those users aren't printing anything.
According to one on the support staff, 12.6 resolves that issue and, frankly, I'd much rather put out a release on V12.6 that has no code changes than change the code and stay in 12.5. They are planning to spend a month testing the new version to ensure that there are no new issues. -- Douglas von Roeder 949-336-2902 On Fri, Apr 7, 2017 at 12:23 PM, Tim Nevels via 4D_Tech < 4d_tech@lists.4d.com> wrote: > On Apr 6, 2017, at 2:39 AM,Douglas von Roeder wrote: > > > A client using V12.5 is starting to adopt Windows 10 and has asked about > > going to V12.6 since the newer version, apparently, resolves "the Windows > > 10 tiny print problem that 12.5 has." > > > > The Cert Matrix for 12.6 states that 12.6 is "not compatible" with 8.1 > and > > does not list Win 10. > > > > Is 12.6 OK to use on Win10? > > > > Bonus question - is there any difference in Win10 compatibility between > > 12.5 and 12.6? > > I don’t believe there is much difference between 12.5 and 12.6 in relation > to compatibility with Windows 8.1 and Windows 10. But I could be wrong. > > The big compatibility issues with v12 and Windows 8.1 and Windows 10 is > printing. So if you don’t do any printing, then you won’t notice any major > problems with v12 and Windows 8.1 and Windows 10. > > But if you print then font sizes will be super small. You can add code > that will change object font sizes, to like double what they were, and get > the printing to work with v12. But if you just upgrade to v13 printing > works again and zero code changes are needed. Windows 7, 8.1 and 10 all > print correctly. > > So the simple test is to get v12.6 and Run it on Windows 10 and print > something from 4D. If the printout looks great then I am wrong and v12.6 is > compatible with Windows 8.1 and Windows 10. But I’m pretty sure it was in > v13 that 4D changed to the new Windows printer API that make it compatible. > > Tim > > ******************************************** > Tim Nevels > Innovative Solutions > 785-749-3444 > timnev...@mac.com > ******************************************** > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: http://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ********************************************************************** > ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
