We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

Update 39.0.3 disabled programmable keys on Logitech G700s mouse . . . How to get them back?

  • 1 trả lời
  • 3 gặp vấn đề này
  • 5 lượt xem
  • Trả lời mới nhất được viết bởi ttii

more options

The G700s provides customized buttons collected in a profile pertaining to a specified application . . . My profile for for T-bird works . . . as well as those for wordprocessing and even windows explorer . . . and the Firefox one worked too, until this latest update.

I've already deleted and re-written the profile, uninstalled and reinstalled the mouse software . . . to no avail.

The same mouse and software still work on my other computer, which has not updated to 39.0.3. Mainly I assigned keyboard shortcuts -- CTRL-W to close a tab, "middle click" to open in a new tab -- nothing elaborate, just to have control of the screen from the mouse in one hand.

Any one know what the update did to disable them?
The G700s provides customized buttons collected in a profile pertaining to a specified application . . . My profile for for T-bird works . . . as well as those for wordprocessing and even windows explorer . . . and the Firefox one worked too, until this latest update. I've already deleted and re-written the profile, uninstalled and reinstalled the mouse software . . . to no avail. The same mouse and software still work on my other computer, which has not updated to 39.0.3. Mainly I assigned keyboard shortcuts -- CTRL-W to close a tab, "middle click" to open in a new tab -- nothing elaborate, just to have control of the screen from the mouse in one hand. Any one know what the update did to disable them?

Tất cả các câu trả lời (1)

more options

This may have been cured in update 40.0. Has anybody else found relief?