Seriously, I mean I've been using the whatsapp desktop version since it was released, and to be honest each update it received either acomplished two things, it was either a straight upgrade that allowed you to have higher connectivity or higher productivity, or it gave you an option to make your experience more enjoyable as in customization or compatibility with phones without hassles.
But the windows update is the black sheep, it seems as the team working on it didn't catch anything that made the desktop app good, which heavily surprises me considering how responsive and intuitive the original desktop app was and it still is UNTIL THEY MESSED THAT UP TOO.
I know that Meta wants you to use the new whatsapp version, but you shouldn't mess up the one that is perfectly working just to make people transition, as the new app IS NOT A FINISHED PRODUCT, as it lacks a lot of the functions that whatsapp desktop has and is a straight downgrade, so please give the option for people that enjoy the current whatsapp desktop version to do so without hassles until the windows app version is fixed.
-The background and text size are unchangable and very ugly, you either have generic dark mode, or blind my eyes white without the stylized nice whatsapp themed default background we are used to, and we lack any options to customize either of them.
-Sending videos and pictures its a hassle and it lacks the same options whatsapp desktop has while compromising QUALITY, CONSISTENCY, and EASE OF USE. Which is a downgrade and a liability the original desktop app doesn't have.
I could list a lot more issues but that is the things I could currently catch from the first 10 minutes I was exploring the app looking for features that DIDN'T EXIST that whatsapp desktop had and worked perfectly, while instantly deleting the app and reinstalling the old desktop app, that even with the issues THEY created with that dumpster fire of an app still is a far better product that whatsapp windows.
So even with the link issues I will keep using whatsapp desktop and might transition to web if the issues keep happening as im honestly getting really annoyed with them after messing a perfectly working app.
And even if im thoroughly dissapointed at the performance that the windows version currently provides, im hopeful that you can fix the issues as you already have a great example of how things should be done in the whatsapp desktop app, and that it will become a product worthy of being called an upgrade instead of the mess it currently is.
TLDR: Desktop app got messed up by the launch of the windows app, the windows app is a straight downgrade missing a ton of features the desktop has already implemented long ago, and the existing features it shares were tinkered with and made worse.
So I ask for the issues in the desktop version to be fixed and left alone until the issues in the windows version are fixed so we can all have a better product to enjoy and be productive with. Cheers
I tried uninstalling and reinstalling. I tried a Reset of the app from the advanced options for the Windows app. I tried rebooting. I tried killing the Whatsapp processes. All things multiple times.
Yes, I have. The program window closes, but when you check the running processes, Whatsapp is still running. And if someone sends a message, it pops up... that is intentional I suppose, but an option to actually shut it all down is missing.
While that works with every other program, whatsapp desktop does not close completely with that shortcut, it only closes the window, four other processes stay open. It does however close as expected, if I do File -> Quit.
As far as I understand from my own programming with Qt, a "close event" should implement whatever is necessary to do when the window (through whatever means) is closed. And my assumption here is, that whatsapp-desktop doesn't have this implemented.
Graphical "applications" are "clients" to the "display server". What a client does if you close one of its windows is completely up to the client and its implementation. Apparently WhatsApp follows an SDI model and therefore does not terminate if you close one of its windows. That this has not happened with random other clients you've been using in the past is meaningless.
I agree and understand this. And it was also my assumption; after all, whatsapp-desktop may have been designed to stay open without a window, so that messages can be received even when the user decided he just doesn't want the window open.
Using the mod4 key (usually the "Windows" key if I understand correctly) for WM key bindings is certainly the way to go. As a matter of fact, I have set up most of the Enlightenment keybindings with the mod4 key. So if I want to stick with 'Q', I should probably configure mod4+Q to close windows.
I realized today that whatsapp-desktop actually stays open if you close the window via its "X" from the window, as in the X icon of the window bar. So this just confirms that the idea of the whatsapp-desktop developers was to keep whatsapp running in the background, so that you can receive messages even if the window is closed.
Yes. And this is precisely the problem you are concerned about in this thread. Ctrl-Q when bound by the client generally means "quit", and you've stated that when you use Whatsapp's Quit menu entry it does indeed fully shut down.
I do want a window to close, not quit an application... for example, when using firefox, the Quit command from the file menu (or the shortcut Ctrl+Q, if it wasn't reconfigured as in my case), would close all firefox windows, e.g. quit firefox entirely. That is not what I would want. I may have two firefox windows open, but just want to close one of those windows.
I know i can run Whatsapp Web and Whatsapp Desktop, but the web's notification it's kinda useless if i miss it because i will have to keep checking on the Tab, i have my personal phone and a work phone so i would like to have both on Whatsapp Desktop, so if i get a new message i'll get the red icon with numbers on the taskbar and not in the browser's tab.
You may want to try waydroid, there is a tutorial in the tutorials and guides section of the forum on its installation. Similar to anbox, but it uses Linux system libraries to integrate Android applications into the system itself. While it is a solution, Android and windows are the two most targeted systems for ransomware and viruses. A good reason for her to suggest another software that can be found on Linux, even if her team remains on windows/android.
I had remembered seeing whatsapp on Opera and installed to check it out. I haven't used it in a while . Any browser can be a data miner depending on how it is used and set up. With the exception of Firefox most better known browsers are chromium based.
After losing time trying to understand whether or not I have/should use/can use/can learn PlayOnLinux, winetricks, wineprefixes etc to install the whatsapp-portable.exe I've downloaded, I say "f#$k it" and just right click on the .exe and click "Open with Install Windows Application".
Yay! A Windows installer wizard starts up. Looks like "Run anyway" was the right choice. I complete the installer's steps, and click "Finish" (leaving "Run Whatsapp Portable" unselected, as something I saw earlier in PlayOnLinux suggested avoiding launching app on finish).
Entire screen goes black for a bit. Eventually screens returns to as before, including the installer again waiting for me to click Finish.
I click it again, and the installer goes away, normal screen this time.
In Zorin menu (well, whiskermenu), I go to "Wine" and Whatsapp is not there. (WeChat, which I installed the same way, is there.) Whatsapp is not in "Internet" either, and is not found by a menu search.
In Nemo, I go to .wine/drive_c. I look in Program Files: not there. I look in Program Files (x86): not there either. Doh! I see portapps has created its own folder on drive_c top level, and inside that /whatsapp-portable.
There's a readme.md (nothing useful in it), a "whatsapp-portable.exe", changelog, portapp.json and a folder called "app". Looking in /app, more folders and "WhatsApp.exe". And in one of those folders, another "WhatsApp.exe".
OK, I'll try the whatsapp-portable.exe in /whatsapp-portable and see what happens.
I double-click on whatsapp-portable.exe and again I get the message with the headline "You can use WhatsApp on the web" and the two buttons at bottom: "Run anyway" and highlighted "Launch WhatsApp". (Before it was just "Launch", this time "Launch WhatsApp".)
I still don't know the difference between Run and Launch, but at least the Launch button this time mentions the name of the program I want to use. So I click "Launch WhatsApp".
And it does not launch WhatsApp. Instead it opens a new tab in Chrome. Heart sinks. WhatsApp Web page, QR code to scan. The same process I've already tried re every other WhatsApp "client" on Linux, and which never allows voice calls. I scan the QR code anyway (who knows? maybe this is just an initial step to get the actual whatsapp-portable running.) The QR code is accepted... and I'm in the regular WhatsApp Web page in Chrome. That's it. No way to make voice calls. All these steps and all those folders and files just to open a web page??? That can't be right.
I close the WhatsApp Web page in Chrome, and try double-clicking on the whatsapp-portable.exe but this time I choose "Run anyway".
New folders are created (/data and /log) but no program visible yet. Then a very long (Wine?) error message, headlined "A JavaScript error occurred in the main process." Then long gibberish and just an "OK" button at bottom. I click OK, the error message disappears. No WhatsApp. I open the Task Manager which shows two processes both called "winedevice.exe", and one "wineserver". But no WhatsApp.