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.

Exactly the problem I've been having, and the simple answer is that you can't. The only way to increase the font size in the new Whatsapp is to increase - unnecessarily and pointlessly - the font size for everything on your PC. It's ridiculous that the older version supported changing font sizes, and the new one does not. After the new version was forced on me, I managed to redownload an older version, and despite the fact that it's glitchy and shows as "outdated", I'll keep using it as long as possible. The new version is useless to me - even with my reading glasses on, I struggle to read the text unless I increase the font size for the computer through the accessibility settings, which affects everything else negatively. I won't be using it once the update is finally forced on me, it's no longer fit for purpose for me.


How To Download Whatsapp In Pc Windows 10


Download Zip 🔥 https://urloso.com/2y3hfd 🔥



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.

@stuka85 I Had the same problem and I can confirm that disabling enhanced security for web.whatsapp.com fixed it. You may try that and see. However, I hope this help the dev team in troubleshooting the issue.

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.

I try again (double-click, "Run anyway"), this time keeping an eye on the task manager.

Six WhatsApp.exe processes appear in the task manager, then the same (I believe) error message as before. I click OK again. But the WhatsApp processes do not disappear. I can't see any WhatsApp window anywhere but apparently it's running. But how to actually see it and use it? Or if not, shut it down?

Can you share some more details. Basically the policy is being applied on user level and device level. I have tried to remove policy being applied at user level but still no success. users/ devices connected to this same web policy are able to use web.whatsapp without any issue but on this particular user after allowing web.whatsapp. Whatsapp page opens and after scanning QR code doesn't show the chats screen and get stuck on loading chats.

Protecting the privacy of your messages remains the driving force behind what we're building at WhatsApp. While End-to-end encryption is the foundation to ensure your calls and messages are secure, we continue to add more layers of privacy on top including the recently launched Chat Lock to protect sensitive chats behind a password, Disappearing Messages that vanish, screenshot blocking for View Once, and the ability to keep your online presence private.

Similar to how we build messaging, we don't believe Channel updates should have to stick around forever. So we'll only store channel history on our servers for up to 30 days and we'll add ways to make updates disappear even faster from follower's devices. Admins will also have the option to block screenshots and forwards from their channel.

Status is a popular way to share ephemeral updates with friends and close contacts on WhatsApp. They disappear in 24 hours and may include photos, videos, GIFs, text, and more. Just like your personal chats and calls, your WhatsApp status is protected by end-to-end encryption so you can share privately and securely. ff782bc1db

download wordpress app

internet explorer 8.0-later versions download

ganap na buhay biblia free download

camera fv-5 lite app download

download game one finger death punch mod apk