Jump to content

Search the Community

Showing results for tags 'window'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General discussion
    • Hot topics
    • Enpass Support & Troubleshooting
    • Autofilling and Desktop Browser Extensions
    • Data Security
    • Announcements
  • Help us improving Enpass
    • Feature requests
    • Enpass Beta
    • Localization
  • General discussion

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 6 results

  1. Hi, Latest MacOS and Enpass up to date versions. I noticed that when I quit Enpass, the main app window reopens at the center of my screen, and not at the place I last put it. There's also some problems with the main app window resize function, sometimes it take it, sometimes no. It's not a big issue anyway, just annoying. Thanks.
  2. Hi, I am using the tiling window manage i3. I have a few workspaces (1-9) between which I switch via hotkeys. Windows are handled a bit different and each window is assigned to a workspace. After updating to Enpass6, I opened it on workspace 9. I also see the tray icon now in my polybar (also some custom menu bar app). When I'm on a different workspace now (for example 2) in the browser and click on the enpass browser extension icon, nothing happens. This is because the context window of Enpass (which shows all matching logins) is now opened on workspace 9 where the original enpass app was opened. This was different on Enpass 5 where this window was shown on top of the browser. I just tried downgrading to Enpass 5 now, but the updated Chrome extension now is not able to work with Enpass 5 again... So is there any recommended fix for Enpass 6 and until this: Where do I find an old version of the chrome browser extension until Enpass 6 works as expected? Thanks, foob
  3. After upgrading my One Plus 5 to the latest Android Pie build, I've encountered an issue when enabling the accessibility option for enpass. When enabled, the multi tasking windows gets extremely laggy and slow. As soon as I disabled the accessibility option, it works normal. Is this some kind of unintended bug?
  4. Im having difficulty with each window in Enpass. It does not fit my screen. Starting with the 'Welcome' page the bottom links could not be seen and the window couldn't be dragged up. So, I tried various screen resolutions and moved Windows taskbar from the right hand side. That helped but only a temporary solution. Im using Windows 10, and a recommended screen resolution of 1920 x 1080. I think this problem requires a bug fix.
  5. issue to sign-in with tradition windows client Dear Dev, I don know if someone already facing this issue, but last night i can not sign in with tradition client on windows, I'm very sure that my master password is correct because i still can sign in with other devices including android phone and a modern windows client. I'm sync with dropbox. I did uninstall and re-install a several times but still no luck it just keep saying that my password is wrong with no other error. Please advice, Best regards.
  6. Enpass on desktops should be split into two separate programs: EnpassCore.exe: This executable file constitutes the core Enpass service that browser plugins communicate with. It should have no window-based-UI whatsoever. This is also what users (and/or the installer) would add to the boot sequence. On boot, adding an icon to the tray (on Windows) or the menu bar (on OSX) would be the only clue it is running. EnpassUI.exe: This executable file constitutes the windowed UI. If EnpassCore isn't running, launching the EnpassUI would automatically launch EnpassCore as well. From any browser plugin, EnpassUI should never be more than a single click away. Benefits: EnpassCore has no windowed UI, so we could launch it as part of the boot sequence without having to deal with the annoying Enpass window being opened on every boot. A UI window should be in in one of the following states: opened, minimized, maximized, or closed. Since EnpassCore is always represented in the tray and EnpassUI is independent of that, there would be absolutely no need for the additional and unusual "minimized but in the tray" state Enpass currently employs. By separating what should be purely a background process from the front-end UI, we can eliminate the need for the quirky "minimize to tray" option and also say goodbye to the bothersome "Click here to restore Enpass" message that is shown every time Enpass is minimized to the tray on Windows 10. In a nutshell, how and when we require the UI for data lookup or data entry should have no affect on whether or not the Enpass service is running in the background. Because EnpassCore has no windowed UI, it could be very "lean and mean", thereby not noticeably impacting boot performance (assuming it's implemented as a native C/C++ application). For those people who are used to (or like) the way Enpass works now, there is no difference. Users can still add EnpassUI to the boot sequence and have the Enpass Window opened on boot if that is their preference. Technical thoughts: Architecturally, browser plugins and the EnpassUI would just be different clients of the same EnpassCore application. In the interest of a shared code base and developer productivity, EnpassCore would ideally be implemented as a C/C++ program that can be compiled on any of the platforms Enpass supports. I chose the filenames EnpassCore.exe and EnpassUI.exe only as a way to more clearly communicate their purpose. Nothing more. The filenames are not part of this suggestion. It would probably be best if EnpassUI is named enpass.exe, so that launching enpass.exe would open the windowed UI as it always has. In this way, people who don't know about, care, or want this change wouldn't be impacted by it at all.
×
×
  • Create New...