Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Community » U++ community news and announcements » 2020.1 alpha
Re: 2020.1 alpha [message #53265 is a reply to message #53264] Wed, 25 March 2020 14:51 Go to previous messageGo to next message
Tom1
Messages: 788
Registered: March 2007
Contributor
Well, it gives a whole bunch of these:

C:\upp-svn\upp.src\uppsrc\Core\InetUtil.cpp(333): warning C4927: illegal conversion; more than one user-defined conversion has been implicitly applied
C:\upp-svn\upp.src\uppsrc\Core\InetUtil.cpp(333): note: while calling the constructor 'Upp::String::String(const char *)'
C:\upp-svn\upp.src\uppsrc\Core\AString.hpp(310): note: see declaration of 'Upp::String::String'


63 warnings in Core...

And Microsoft is still 'Considering' this issue...

Best regards,

Tom
Re: 2020.1 alpha [message #53273 is a reply to message #53265] Wed, 25 March 2020 18:28 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 12497
Registered: November 2005
Ultimate Member
Tom1 wrote on Wed, 25 March 2020 14:51
Well, it gives a whole bunch of these:

C:\upp-svn\upp.src\uppsrc\Core\InetUtil.cpp(333): warning C4927: illegal conversion; more than one user-defined conversion has been implicitly applied
C:\upp-svn\upp.src\uppsrc\Core\InetUtil.cpp(333): note: while calling the constructor 'Upp::String::String(const char *)'
C:\upp-svn\upp.src\uppsrc\Core\AString.hpp(310): note: see declaration of 'Upp::String::String'


63 warnings in Core...

And Microsoft is still 'Considering' this issue...

Best regards,

Tom


Yes, these are the problem Sad

Mirek
Re: 2020.1 alpha [message #53274 is a reply to message #53241] Wed, 25 March 2020 18:29 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 12497
Registered: November 2005
Ultimate Member
omari wrote on Tue, 24 March 2020 18:19
Thanks, the toolbar is split on two lines.

by the way, please check the toolbar's tooltips textcolor in dark mode.


Should be now fixed. Thanks for reporting.

Mirek
Re: 2020.1 alpha [message #53286 is a reply to message #53274] Thu, 26 March 2020 12:48 Go to previous messageGo to next message
koldo is currently offline  koldo
Messages: 3120
Registered: August 2008
Ultimate Member
Please review install instructions in https://www.ultimatepp.org/www$uppweb$uppx11$en-us.html as it says to install libgtk2.0-dev.

Best regards
Iñaki
Re: 2020.1 alpha [message #53287 is a reply to message #53286] Thu, 26 March 2020 13:09 Go to previous messageGo to next message
koldo is currently offline  koldo
Messages: 3120
Registered: August 2008
Ultimate Member
koldo wrote on Thu, 26 March 2020 12:48
Please review install instructions in https://www.ultimatepp.org/www$uppweb$uppx11$en-us.html as it says to install libgtk2.0-dev.
Reviewed for Ubuntu. Please check if it is right for Fedora and other distros.


Best regards
Iñaki
Re: 2020.1 alpha [message #53300 is a reply to message #53287] Thu, 26 March 2020 22:25 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 12497
Registered: November 2005
Ultimate Member
Should that be rewritten to use buildrequires?
Re: 2020.1 alpha [message #53301 is a reply to message #53287] Thu, 26 March 2020 23:53 Go to previous messageGo to next message
Novo is currently offline  Novo
Messages: 975
Registered: December 2006
Experienced Contributor
koldo wrote on Thu, 26 March 2020 08:09
koldo wrote on Thu, 26 March 2020 12:48
Please review install instructions in https://www.ultimatepp.org/www$uppweb$uppx11$en-us.html as it says to install libgtk2.0-dev.
Reviewed for Ubuntu. Please check if it is right for Fedora and other distros.

I always thought that this release is gtk3-based ...
Am I missing something?
What gtk2 is needed for?


Regards,
Novo
Re: 2020.1 alpha [message #53306 is a reply to message #53246] Fri, 27 March 2020 17:08 Go to previous messageGo to next message
busiek is currently offline  busiek
Messages: 46
Registered: February 2011
Location: Poland
Member
Tom1 wrote on Wed, 25 March 2020 10:53
Hi,

I just noticed that the current version has a visualization issue with the edge rectangle of entryfields, lists, etc. I confirmed all these issues on UWord with current version. This can be seen in e.g. standard FileSel where the file and directory lists and the File entryfield all lack vertical edges. Additionally, if the width of the FileSel is increased by dragging, the horizontal edges do not extend all the way to the right edge of each panel. There are also some other corner effects that look strange on UWord main window.

TheIDE does not show these problems for me possibly because I have 'Dark' theme selected there.

Best regards,

Tom


I have the same problem on Windows with the newest trunk. Just checked 2 hours ago. I am using MSVC 2019 and default theme. Simply edit fields seem to have too narrow painting rectangle.

Jakub
Re: 2020.1 alpha [message #53307 is a reply to message #53306] Fri, 27 March 2020 17:19 Go to previous messageGo to next message
Tom1
Messages: 788
Registered: March 2007
Contributor
busiek wrote on Fri, 27 March 2020 18:08
Tom1 wrote on Wed, 25 March 2020 10:53
Hi,

I just noticed that the current version has a visualization issue with the edge rectangle of entryfields, lists, etc. I confirmed all these issues on UWord with current version. This can be seen in e.g. standard FileSel where the file and directory lists and the File entryfield all lack vertical edges. Additionally, if the width of the FileSel is increased by dragging, the horizontal edges do not extend all the way to the right edge of each panel. There are also some other corner effects that look strange on UWord main window.

TheIDE does not show these problems for me possibly because I have 'Dark' theme selected there.

Best regards,

Tom


I have the same problem on Windows with the newest trunk. Just checked 2 hours ago. I am using MSVC 2019 and default theme. Simply edit fields seem to have too narrow painting rectangle.

Jakub


Hi Jakub,

The problem is in the recent version of MSVC2019 / MSBT2019 compiler:

https://developercommunity.visualstudio.com/content/problem/ 912723/recent-version-of-visual-c-compiler-might-have-ove.ht ml

Please try MSVC2017 / MSBT2017 instead. (Or the newly available CLANG-MINGW combo, which is looking promising...) Smile

Best regards,

Tom
Re: 2020.1 alpha [message #53308 is a reply to message #53306] Fri, 27 March 2020 17:21 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 12497
Registered: November 2005
Ultimate Member
busiek wrote on Fri, 27 March 2020 17:08
Tom1 wrote on Wed, 25 March 2020 10:53
Hi,

I just noticed that the current version has a visualization issue with the edge rectangle of entryfields, lists, etc. I confirmed all these issues on UWord with current version. This can be seen in e.g. standard FileSel where the file and directory lists and the File entryfield all lack vertical edges. Additionally, if the width of the FileSel is increased by dragging, the horizontal edges do not extend all the way to the right edge of each panel. There are also some other corner effects that look strange on UWord main window.

TheIDE does not show these problems for me possibly because I have 'Dark' theme selected there.

Best regards,

Tom


I have the same problem on Windows with the newest trunk. Just checked 2 hours ago. I am using MSVC 2019 and default theme. Simply edit fields seem to have too narrow painting rectangle.

Jakub


Are you getting these warnings? If yes, you are too victim of broken compiler...

Mirek
Re: 2020.1 alpha [message #53309 is a reply to message #53308] Fri, 27 March 2020 17:23 Go to previous messageGo to next message
busiek is currently offline  busiek
Messages: 46
Registered: February 2011
Location: Poland
Member
mirek wrote on Fri, 27 March 2020 17:21
busiek wrote on Fri, 27 March 2020 17:08
Tom1 wrote on Wed, 25 March 2020 10:53
Hi,

I just noticed that the current version has a visualization issue with the edge rectangle of entryfields, lists, etc. I confirmed all these issues on UWord with current version. This can be seen in e.g. standard FileSel where the file and directory lists and the File entryfield all lack vertical edges. Additionally, if the width of the FileSel is increased by dragging, the horizontal edges do not extend all the way to the right edge of each panel. There are also some other corner effects that look strange on UWord main window.

TheIDE does not show these problems for me possibly because I have 'Dark' theme selected there.

Best regards,

Tom


I have the same problem on Windows with the newest trunk. Just checked 2 hours ago. I am using MSVC 2019 and default theme. Simply edit fields seem to have too narrow painting rectangle.

Jakub


Are you getting these warnings? If yes, you are too victim of broken compiler...

Mirek


I'll check that the next time I will be under Windows.
Re: 2020.1 alpha [message #53336 is a reply to message #53309] Sun, 29 March 2020 22:04 Go to previous messageGo to next message
Novo is currently offline  Novo
Messages: 975
Registered: December 2006
Experienced Contributor
It would be great to add support of "Use unique output directory per assembly (append assembly name to output directory)" to umk. I tried to do that by myself, but got lost in different variants of SaveVars/LoadVars. I couldn't figure out how to force umk to use assembly name as a folder name. I was always getting a different folder name.
TIA


Regards,
Novo
Re: 2020.1 alpha [message #53337 is a reply to message #53336] Sun, 29 March 2020 22:55 Go to previous messageGo to next message
Sender Ghost is currently offline  Sender Ghost
Messages: 299
Registered: November 2008
Experienced Member
Novo wrote on Sun, 29 March 2020 20:04

I couldn't figure out how to force umk to use assembly name as a folder name. I was always getting a different folder name.

There is a possibility to specify output directory/file for umk. Just need to use absolute path to available output directory or create it before umk usage.
For example:
% mkdir -p out/uppsrc
% ./umk uppsrc ide CLANG -brs +GUI ${PWD}/out/uppsrc/theide
<..>
% ./umk uppsrc ide CLANG -brs +GUI ${PWD}/out/uppsrc
<..>
% ls -1 out/uppsrc
ide
theide
Re: 2020.1 alpha [message #53339 is a reply to message #53337] Mon, 30 March 2020 01:26 Go to previous messageGo to next message
Novo is currently offline  Novo
Messages: 975
Registered: December 2006
Experienced Contributor
Sender Ghost wrote on Sun, 29 March 2020 16:55
Novo wrote on Sun, 29 March 2020 20:04

I couldn't figure out how to force umk to use assembly name as a folder name. I was always getting a different folder name.

There is a possibility to specify output directory/file for umk. Just need to use absolute path to available output directory or create it before umk usage.
For example:
% mkdir -p out/uppsrc
% ./umk uppsrc ide CLANG -brs +GUI ${PWD}/out/uppsrc/theide
<..>
% ./umk uppsrc ide CLANG -brs +GUI ${PWD}/out/uppsrc
<..>
% ls -1 out/uppsrc
ide
theide

Thanks. I knew that it is possible to pass to umk an absolute path to an output directory.
But it is much more convenient to pass an extra-option and get behavior identical to TheIDE.


Regards,
Novo
Re: 2020.1 alpha [message #53352 is a reply to message #53339] Mon, 30 March 2020 13:43 Go to previous messageGo to next message
amrein is currently offline  amrein
Messages: 272
Registered: August 2008
Location: France
Experienced Member
It would be great to have an extra umk parameter to specify the configuration folder instead of having to pass the absolute path.
With absolute path, the generated Makefile is static (it uses absolute path within).

[Updated on: Mon, 30 March 2020 13:43]

Report message to a moderator

Re: 2020.1 alpha [message #53354 is a reply to message #53352] Mon, 30 March 2020 14:57 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 12497
Registered: November 2005
Ultimate Member
amrein wrote on Mon, 30 March 2020 13:43
It would be great to have an extra umk parameter to specify the configuration folder instead of having to pass the absolute path.
With absolute path, the generated Makefile is static (it uses absolute path within).


Sorry, right now I am a bit confused here... What exactly do you mean by config folder? ~/.upp/umk?

Example of absolute path in Makefile?

Mirek
Re: 2020.1 alpha [message #53361 is a reply to message #53354] Mon, 30 March 2020 22:02 Go to previous messageGo to next message
amrein is currently offline  amrein
Messages: 272
Registered: August 2008
Location: France
Experienced Member
mirek wrote on Mon, 30 March 2020 14:57
amrein wrote on Mon, 30 March 2020 13:43
It would be great to have an extra umk parameter to specify the configuration folder instead of having to pass the absolute path.
With absolute path, the generated Makefile is static (it uses absolute path within).


Sorry, right now I am a bit confused here... What exactly do you mean by config folder? ~/.upp/umk?



Yes exactly.

Quote:

Example of absolute path in Makefile?


In my memory, the .bm absolute path was inside the Makefile. I tested umk today and apparently I was wrong.


Re: 2020.1 alpha [message #53367 is a reply to message #53361] Tue, 31 March 2020 13:02 Go to previous messageGo to next message
Tom1
Messages: 788
Registered: March 2007
Contributor
Hi Mirek,

I'm using the wonderful new Xform2D::Map() to render a raster map image over a specific area with specific corner coordinates. This is a great feature, but BufferPainter::Fill(image) suffers from edge effects at the borders of the image fill. The fill leaves narrow gaps between the filled triangles. Both FILL_FAST and FILL_EXACT exhibit this problem. Even a simple BufferPainter::Fill(Blue()) exhibits this issue, although the gap seems slightly narrower then.

At this time I would like to be able to use at least FILL_FAST. Can you take a look at this?

Here's a testcase:

#include <CtrlLib/CtrlLib.h>

using namespace Upp;

class PainterImageMapping : public TopWindow {
public:
	typedef PainterImageMapping CLASSNAME;
	
	PainterImageMapping(){
		Sizeable();
	}
		
	virtual void Paint(Draw &draw){
		ImageBuffer ib(GetSize());
		{
			ImageBuffer imb(500,500);
			{
				BufferPainter iw(imb);
				iw.Clear(Black());
			}
			
			Image img(imb);

			// image coordinates
			Pointf iNW(0,0);
			Pointf iNE(img.GetWidth(),0);
			Pointf iSW(0,img.GetHeight());
			Pointf iSE(img.GetWidth(),img.GetHeight());
			
			BufferPainter w(ib);
			w.Clear(White());
			
			dword flags=FILL_FAST;
			//dword flags=FILL_EXACT;
			{
				Pointf nw(100,100);
				Pointf ne(700,100);
				Pointf sw(100,700);
				Pointf se(650,750);
				w.Move(nw).Line(ne).Line(se).Fill(img, Xform2D::Map(iNW,iNE,iSE,nw,ne,se), flags);
				w.Move(nw).Line(sw).Line(se).Fill(img, Xform2D::Map(iNW,iSW,iSE,nw,sw,se), flags);
			}
			{
				Pointf nw(700,100);
				Pointf ne(1400,120);
				Pointf sw(650,750);
				Pointf se(1300,720);
				w.Move(nw).Line(ne).Line(se).Fill(img, Xform2D::Map(iNW,iNE,iSE,nw,ne,se), flags);
				w.Move(nw).Line(sw).Line(se).Fill(img, Xform2D::Map(iNW,iSW,iSE,nw,sw,se), flags);
			}
			{
				Pointf nw(100,700);
				Pointf ne(650,750);
				Pointf sw(100,1200);
				Pointf se(650,1350);
				w.Move(nw).Line(ne).Line(se).Fill(img, Xform2D::Map(iNW,iNE,iSE,nw,ne,se), flags);
				w.Move(nw).Line(sw).Line(se).Fill(img, Xform2D::Map(iNW,iSW,iSE,nw,sw,se), flags);
			}
			{
				Pointf nw(650,750);
				Pointf ne(1300,720);
				Pointf sw(650,1350);
				Pointf se(1300,1220);
				w.Move(nw).Line(ne).Line(se).Fill(img, Xform2D::Map(iNW,iNE,iSE,nw,ne,se), flags);
				w.Move(nw).Line(sw).Line(se).Fill(img, Xform2D::Map(iNW,iSW,iSE,nw,sw,se), flags);
			}

			w.Finish();
		}
		SetSurface(draw,Rect(ib.GetSize()),ib,ib.GetSize(),Point(0,0));
	}
};

GUI_APP_MAIN
{
	PainterImageMapping().Run();
}


Best regards,

Tom

[EDIT] - Expanded testcase to include another row of tiles. This effectively adds (nearly) horizontal facing edges.

[Updated on: Tue, 31 March 2020 13:23]

Report message to a moderator

Re: 2020.1 alpha [message #53368 is a reply to message #53367] Tue, 31 March 2020 13:38 Go to previous messageGo to next message
Tom1
Messages: 788
Registered: March 2007
Contributor
Hi,

Here's a zoomed in detail from the image rendered by the above test case. The center of the image shows the common point of six triangles.

index.php?t=getfile&id=6033&private=0

Best regards,

Tom
Re: 2020.1 alpha [message #53370 is a reply to message #53367] Tue, 31 March 2020 15:15 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 12497
Registered: November 2005
Ultimate Member
Tom1 wrote on Tue, 31 March 2020 13:02
Hi Mirek,

I'm using the wonderful new Xform2D::Map() to render a raster map image over a specific area with specific corner coordinates. This is a great feature, but BufferPainter::Fill(image) suffers from edge effects at the borders of the image fill. The fill leaves narrow gaps between the filled triangles.


I am afraid this is just a feature of antialiased rendering. Problem is gradual composition of those edge points I think.

FILL_FAST unfortunately is still based on the same method, just rounding values to 0/1.

Mirek
Previous Topic: U++/Win32 is now using CLANG toolchain
Next Topic: svn/github now has auto-generated Makefile
Goto Forum:
  


Current Time: Fri May 29 22:24:11 CEST 2020

Total time taken to generate the page: 0.01802 seconds