|
|
Home » Community » U++ community news and announcements » 2020.2 'upcoming'
2020.2 'upcoming' [message #54649] |
Tue, 25 August 2020 10:46  |
 |
mirek
Messages: 14257 Registered: November 2005
|
Ultimate Member |
|
|
I believe it is time to release again! Please help me extend this list (so far I have only added parts that I have commited...)
Release highlights
* This release is mostly about optimizations, using SIMD and multithreading.
Core
* memset*, memcpy*, memeq*, memhash SIMD optimised inlined routines (* = 8, 16, 32, 64, 128)
* String comparison is yet again optimised
* Using 64 bit hashes on 64 bit CPUS
Draw, Painter
* SIMD optimizations (Intel SSE2 and ARM NEON) of graphics related routines
Ide
* C++ Assist parser in TheIDE is now multithreaded and some parts run in background
* Navigator now can search for files too
* The errors now can be directly googled
SQL
* plugin/Sqlite3: Updated to 3.33
uppsrc
* Improved support for OpenSolaris derived systems, FreeBSD and OpenBSD
|
|
|
|
|
|
|
|
Re: 2020.2 'upcoming' [message #54732 is a reply to message #54649] |
Fri, 04 September 2020 10:55   |
 |
Klugier
Messages: 1099 Registered: September 2012 Location: Poland, Kraków
|
Senior Contributor |
|
|
Hello Mirek,
I observed some issues with Assist++ in bazzar/GoogleMockExample. If I modify it like this the problem is fully reproducible:
TEST(CarRepairShopTest, ServiceChecksAllMainCarElements) {
MockCar car;
CarRepairShop repairShop;
repairShop.// Asist++ from here - nothing happens!!!
EXPECT_CALL(car, ReadRegistrationNumbers()).WillOnce(::testing::Return(String(CAR_REGISTRATION_NUMBER)));
EXPECT_CALL(car, OpenHood()).Times(::testing::AtLeast(1));
EXPECT_TRUE(repairShop.Service(car));
}
It seems that Assist++ doesn't understand TEST and TEST_F macros very well.
Klugier
U++ - one framework to rule them all.
[Updated on: Fri, 04 September 2020 10:56] Report message to a moderator
|
|
|
|
|
Re: 2020.2 'upcoming' [message #54931 is a reply to message #54930] |
Tue, 29 September 2020 12:50   |
 |
Klugier
Messages: 1099 Registered: September 2012 Location: Poland, Kraków
|
Senior Contributor |
|
|
Hello Mirek,
I will do not touch anything to the release date I will target this "minor" improvements in the 2020.2 release and now let's focus only on major issues (like compilation warnings, crashes etc.).
Klugier
U++ - one framework to rule them all.
[Updated on: Tue, 29 September 2020 12:50] Report message to a moderator
|
|
|
Re: 2020.2 'upcoming' [message #54981 is a reply to message #54931] |
Sat, 03 October 2020 17:15   |
Novo
Messages: 1430 Registered: December 2006
|
Ultimate Contributor |
|
|
BTW, Upp is currently broken.
reference/SqlArray
/home/ssg/.local/soft/bb-worker/worker/l-upp/build/uppsrc/plugin/sqlite3/Sqlite3upp.cpp:440:23: error: use of undeclared identifier 'retval'
ASSERT(SQLITE_OK == retval);
^
Regards,
Novo
|
|
|
|
|
|
Re: 2020.2 'upcoming' [message #55052 is a reply to message #55001] |
Wed, 07 October 2020 14:23   |
Tom1
Messages: 1303 Registered: March 2007
|
Ultimate Contributor |
|
|
Hi,
I have not been printing in a while and now I just found myself in trouble with it. Here's a testcase:
#include <CtrlLib/CtrlLib.h>
#include <Painter/Painter.h>
using namespace Upp;
GUI_APP_MAIN
{
PrinterJob job;
if(job.Execute()){
Draw &draw=job.GetDraw();
draw.StartPage();
draw.BeginNative();
Size size=draw.GetPagePixels();
Size DPI=draw.GetPixelsPerInch();
Rect drawrect=size;
PaintingPainter dp(size);
dp.Clear(White());
dp.Move(0,0);
dp.Line(size.cx,size.cy);
dp.Stroke(3,Black());
dp.Move(0,size.cy);
dp.Line(size.cx,0);
dp.Stroke(3,Black());
dp.Move(0,0).Line(size.cx,0).Line(size.cx,size.cy).Line(0,size.cy).Line(0,0);
dp.Stroke(3,Black());
dp.Circle(size.cx/2,size.cy/2,min(size.cx,size.cy)/2).Stroke(2,Black());
/* // It nearly works via ImageBuffer
ImageBuffer ib(size);
BufferPainter w(ib);
w.Paint(dp.GetResult());
draw.DrawImage(0,0,Image(ib));
*/
// But clearly fails via direct DrawPainting
draw.DrawPainting(drawrect,dp.GetResult());
draw.EndNative();
draw.EndPage();
}
}
Using DrawPainting results in a catastrophic mess. DrawImage is just a little bit 'edgy' on PDF prints, but just fine on laser printer.
I guess this issue has been around at least since 2020.1.
Best regards,
Tom
|
|
|
|
|
Re: 2020.2 'upcoming' [message #55056 is a reply to message #55054] |
Wed, 07 October 2020 15:33   |
Tom1
Messages: 1303 Registered: March 2007
|
Ultimate Contributor |
|
|
Hi Mirek,
Thanks for the prompt reaction! The non-ImageBuffer version is now at least as good as the ImageBuffer version.
The PDF printing was done through Windows print to PDF. Please find attached the result. When viewing and zooming in severely on Edge or Firefox, you can see some continuity issues especially on the nearly horizontal parts of the circle. I think this could be somehow related to compression of blocks and anti-aliasing on the block edges.
Best regards,
Tom
|
|
|
|
|
Goto Forum:
Current Time: Sun May 11 20:14:28 CEST 2025
Total time taken to generate the page: 0.01149 seconds
|
|
|