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 » U++ Library support » U++ Widgets - General questions or Mixed problems » two small bugs to check for GLCtrl
two small bugs to check for GLCtrl [message #61929] Fri, 20 February 2026 20:32 Go to next message
luoganda is currently offline  luoganda
Messages: 217
Registered: November 2016
Experienced Member
this was on older versions and also in v18458.
Tested only on Linux !!


When using w.DrawText with '-number'(eg -24.5) in it
that - before number is not drawn at all, is this the intent?
This is in GLCtrl/GLDraw ver, but i think in regular Draw ver works ok.
For workarround i now use + prepended in front of numbers, so when
- is in front of number, no + is drawn.
======


Not sure about this but worth checking.
In GLCtrl there is
private:
#ifdef PLATFORM_WIN32
...
public:
	GLPane() { NoWantFocus(); }
...
#endif

for winVer - allOk.
But for linux/gtk - no public(upper private still holds here) - is this the intent?
I make Sync public for myself becasue i need it sometimes - but would be worth
checking if for example one would subClass GLCtrl and would need some of the vars/funcs.
#ifdef PLATFORM_POSIX // we assume X11 or GTK

In linux ver - there are no public(or protected) methods whatsoever.
======

Not sure about this either - but worth checking:
On win11 same app worked, but on linux it doesn't
bool Key(dword key,int c){
  switch(key){
    case K_A:
      int abc=0;
      return true;
   }
  return false;
}

For workarround on linux - i now use "case K_A:case 'a':".
If correct would be "case 'a':case 'A':"(because it's character code and not key-code),
then case K_A should probably not work on winVer too.
Which is 'the way to go ver', case 'a'?
probably yes - if one reads the docs - in that case i guess K_A is only defined so
that it can be later used as a helper to eg K_CTRL_A or K_SHIFT_A etc.
====


By the way - i noticed this in newer uppVers:
using TcpSocket = Socket <= for backward compatibility,
but it should probably not be marked as just 'for backward compatibility',
since there are also UdpSockets - are they avail in Upp?

[Updated on: Fri, 20 February 2026 21:00]

Report message to a moderator

Re: two small bugs to check for GLCtrl [message #61930 is a reply to message #61929] Sat, 21 February 2026 11:10 Go to previous message
Oblivion is currently offline  Oblivion
Messages: 1254
Registered: August 2007
Senior Contributor
Quote:
By the way - i noticed this in newer uppVers:
using TcpSocket = Socket <= for backward compatibility,
but it should probably not be marked as just 'for backward compatibility',
since there are also UdpSockets - are they avail in Upp?


Hi,

The renaming happened because U++ (And former TcpScoket) has gained AF_UNIX (unix domain socket) support. So semantically the move is correct (Socket class can act as both a Tcp socket and unix socket). And there is no plan to have UdpSocket in Upp core (yet there is Urr package in UppHub). Frankly, there is no real reason to encapsulate them anyway, they are already very primitve and easy to use.

By the way, come join us also in our discord server, it is more active nowadays.

Best regards,
Oblivion


[Updated on: Sat, 21 February 2026 11:46]

Report message to a moderator

Previous Topic: GLDraw - 32/64-bit version
Next Topic: Add compilable testcases for nontrivial problems!
Goto Forum:
  


Current Time: Sat Feb 21 23:59:03 CET 2026

Total time taken to generate the page: 0.10740 seconds