Feel free to discuss the current beta release of client 3.1.2
Beta Announcement
We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020
-= TeamSpeak Team =-
Feel free to discuss the current beta release of client 3.1.2
Beta Announcement
When sending PMs please make sure to include a reference link to the thread in question in the body of your message.
-= TeamSpeak Fanatic =-
People will care even less now I guess.TSDNS deprecated dialog is now a message in the server tab.
Both help with the bug that drains laptop batteries on Intel IGPs.(experimental) added command line arguments to let users with broken gfx drivers force using Angle DirectX backend or software rendering: --force-opengl-angle --force-opengl-soft
Still noone of TeamSpeak could explain to me why on earth OpenGL is used at all. Just a waste of disk space (20 MB or so) and RAM (~350% compared to 3.0) for absolutely no advantage at all.
RAM Private Bytes / Working Set (x86 on Windows 7 x64, not connected to anything)
- 3.0.20: 22 MB / 35.5 MB (had no other version without OpenGL available for testing)
- 3.1.2 OpenGL Software: 45.5 MB / 55.5 MB
- 3.1.2 OpenGL Angle: 65.5 MB / 52 MB
- 3.1.2 OpenGL (default): 78.5 MB / 44 MB
-= TeamSpeak Team =-
You never askedOriginally Posted by numma_cway
(at least not that I'm aware)
OpenGL is a requirement of QtWebEngine, which is used.
In your opinion.
When sending PMs please make sure to include a reference link to the thread in question in the body of your message.
-= TeamSpeak Fanatic =-
I did ask in some threads. What is the advantage of Qt web engine? Being used for browsing addons?
-= TeamSpeak Team =-
The statement that it is being used for the addon browser is correct, indeed.
However the statement that it is being used exclusively for the addon browser would be incorrect, as it is also being used in the first-start popup.
-= TeamSpeak Addict =-
Did a simple popup have to be rendered in a web engine?
With client 3.1.0 - 3.1.2 we started using the web engine for "Options -> Addons" and the "myTeamSpeak dialog" on client start.
There will be more in the future that will use the web engine. The options dialog and the myTeamsepak dialog are just the beginning.
Last edited by dante696; March 17th, 2017 at 02:15 PM.
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
-= TeamSpeak Addict =-
Is this partially because you believe that qt can't provide you with the solution to do what you want?
Or is there another reason?
Not directly. The web engine is from Qt, but yes Qt alone has it's limits.
We use the QtWebEngine as an extension and do have more options now to add or change things in our GUI.
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
-= TeamSpeak Fanatic =-
In other words, the whole client will soon be implemented in QtWebEngine and TeamSpeak will be renamed into TiScord.
-= TeamSpeak Lover =-
Got a minor bug to report. You fixed the UTF8-BOM issue in the plugin installer, however it now seems to be impossible to have multi-line text enclosed in double quotes (") in package.ini. Lets assume the following content in package.ini:
The plugin installer then just displays:Code:Description = "Awesome plugin version 1.3.3.7 This really is an awesome plugin, you will see."
So the first quote (which normally is INI file standard conform I guess) is printed as literal and all stuff following a newline is discarded.Code:"Awesome plugin version 1.3.3.7
It also doesn't help to delete the spaces around the equal sign after Description or to convert package.ini from UTF8-w/o-BOM to UTF8-BOM.
-= Banned =-
Try \n maybe
-= TeamSpeak Addict =-
This works for multiline descriptions:
Code:Description = "line 1\nline2 \nline3"
-= TeamSpeak Addict =-
SlackSpeak3 :v
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
