Jump to content


Photo

HOTKEY - problems / suggestions


  • Please log in to reply
579 replies to this topic

Re: HOTKEY - problems / suggestions #261 ims

  • PLi® Core member
  • 13,764 posts

+214
Excellent

Posted 10 November 2014 - 09:29

Yes, it is not happy to have translated RC's button names.


Kdo nic nedělá, nic nezkazí!

Re: HOTKEY - problems / suggestions #262 littlesat

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 10 November 2014 - 09:39

OK, then I will revert it...

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: HOTKEY - problems / suggestions #263 ims

  • PLi® Core member
  • 13,764 posts

+214
Excellent

Posted 10 November 2014 - 10:13

I think, it will be better...


Kdo nic nedělá, nic nezkazí!

Re: HOTKEY - problems / suggestions #264 Taapat

  • PLi® Core member
  • 2,345 posts

+121
Excellent

Posted 10 November 2014 - 10:13

But do not forget that it is also not necessary: (_("Red long"), "red_long", ""), which has existed from the beginning of Hotkey.



Re: HOTKEY - problems / suggestions #265 littlesat

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 10 November 2014 - 14:55

The color keys do not have e colors printed... So they could ve the only ones to translate...

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: HOTKEY - problems / suggestions #266 Dimitrij

  • PLi® Core member
  • 10,263 posts

+347
Excellent

Posted 10 November 2014 - 17:38

The color keys do not have e colors printed... So they could ve the only ones to translate...

It was my idea in this patch.

name key and long


Edited by Dima73, 10 November 2014 - 17:38.

GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: HOTKEY - problems / suggestions #267 Taapat

  • PLi® Core member
  • 2,345 posts

+121
Excellent

Posted 10 November 2014 - 17:41

At this, I think that if we agree that the buttons do not need translate, it is not necessary for all _(...) in hotkeys = [...]
But maybe that some of the buttons need to be translated, such as color or direction?


Edited by Taapat, 10 November 2014 - 17:45.


Re: HOTKEY - problems / suggestions #268 ims

  • PLi® Core member
  • 13,764 posts

+214
Excellent

Posted 10 November 2014 - 20:23

No button translate... maximaly translate text "long", imho


Kdo nic nedělá, nic nezkazí!

Re: HOTKEY - problems / suggestions #269 Dimitrij

  • PLi® Core member
  • 10,263 posts

+347
Excellent

Posted 10 November 2014 - 20:45

No button translate... maximaly translate text "long", imho

and name color key


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: HOTKEY - problems / suggestions #270 ims

  • PLi® Core member
  • 13,764 posts

+214
Excellent

Posted 10 November 2014 - 20:51

It is very strange, when 8 button's names are translated and all others are in english. More contrast it must be for 8 cyrilic + lat.

Better is all in original ... names on RC are in english all.


Kdo nic nedělá, nic nezkazí!

Re: HOTKEY - problems / suggestions #271 Bay

  • Senior Member
  • 87 posts

+1
Neutral

Posted 11 November 2014 - 11:50

ET9200 "Timer-Button(short,long)" no more working with "Hotkey".



Re: HOTKEY - problems / suggestions #272 ims

  • PLi® Core member
  • 13,764 posts

+214
Excellent

Posted 11 November 2014 - 12:45

If you need it now, change there in keymap.xml in line:

<key id="KEY_PROGRAM" mapto="timerSelection" flags="m" />

"m" to "b"

<key id="KEY_PROGRAM" mapto="timerSelection" flags="b" />

I will make patch for it soon.


Edited by ims, 11 November 2014 - 13:12.

Kdo nic nedělá, nic nezkazí!

Re: HOTKEY - problems / suggestions #273 ims

  • PLi® Core member
  • 13,764 posts

+214
Excellent

Posted 11 November 2014 - 13:39

Here is patch. I overlooked, that this buttons have own routine.

Attached Files


Kdo nic nedělá, nic nezkazí!

Re: HOTKEY - problems / suggestions #274 Bay

  • Senior Member
  • 87 posts

+1
Neutral

Posted 11 November 2014 - 15:01

THX all ok :)



Re: HOTKEY - problems / suggestions #275 littlesat

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 11 November 2014 - 17:50

Pushed...


WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: HOTKEY - problems / suggestions #276 umtauscher

  • Senior Member
  • 179 posts

+1
Neutral

Posted 11 November 2014 - 18:12

Hi everyone,

 

I just upgraded to 4.0 after a years wait. I have to say great work on the hotkeys, thanks a lot.

And as you would suspect, I have a little request:

 

Could it be possible to add the Mute button on the Vu+ models to the hotkey list?

This would be really great.

Thanks

Umtauscher



Re: HOTKEY - problems / suggestions #277 umtauscher

  • Senior Member
  • 179 posts

+1
Neutral

Posted 11 November 2014 - 18:22

As I am unable to edit the post I just entered:

 

2. It would be great, I we could disable a certain hotkey (I am thinking of the power button)

That way I could program a discrete ON/OFF by using the hotkey function.

At the moment I do this by manipulation the keymap file which is far less intelligent.

 

That really would be super.

Thanks

Umtauscher



Re: HOTKEY - problems / suggestions #278 ims

  • PLi® Core member
  • 13,764 posts

+214
Excellent

Posted 11 November 2014 - 20:52

"Radio", "Back", "Left", "Right", "Audio", "Play", "Stop", Pause",  "Timer", "Slow" and "Home" are translated


Kdo nic nedělá, nic nezkazí!

Re: HOTKEY - problems / suggestions #279 ims

  • PLi® Core member
  • 13,764 posts

+214
Excellent

Posted 11 November 2014 - 21:03

line:

self.list.append(ChoiceEntryComponent('',(_(x[0]), x[1])))

to

self.list.append(ChoiceEntryComponent('',(x[0], x[1])))

Then translating for "long" and color buttons works well and next string are in original, as was wanted. Patch on the way...


Edited by ims, 11 November 2014 - 21:11.

Kdo nic nedělá, nic nezkazí!

Re: HOTKEY - problems / suggestions #280 ims

  • PLi® Core member
  • 13,764 posts

+214
Excellent

Posted 11 November 2014 - 21:34

Here is patch for translating wanted texts only

 

and patch with removing KEY_REFRESH and place is under Back => Back/Recall and Back/Recall long, as is coded for F1 from today.

Attached Files


Kdo nic nedělá, nic nezkazí!


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users