998 replies to this topic

[IanSav]

Hi Persian Prince and other skin developers,

 

It looks like my cursor image in the 1080 image set for the VirtualKeyBoard is incorrect.  The cursor is coloured yellow rather than white.  Please use the attached version in ALL 1080 sized skins.

 

Regards,

Ian.

 

Attached Files

•  vkey_sel.png   149bytes   1 downloads

[IanSav]

Hi,

 

To make it easier for skin designers and maintainers I have attached a zip file of all the 720 and 1080 images used by the VirtualKeyBoard.  Please make sure that the appropriate images are placed in a directory called "buttons" in the home directory of the skin you are updating.

 

Regards,

Ian.

 

Attached Files

•  VirtualKeyBoardImages.zip   22.51KB   2 downloads

[littlesat]

Why not pitting them in skin_default?

[Abu Baniaz]

Isnt "skin_default" an "emergency skin"

Sent from my Moto G (5S) using Forum Fiend v1.3.3.

Edited by Abu Baniaz, 17 August 2018 - 18:15.

[IanSav]

Hi Littlesat,

 

Why not pitting them in skin_default?

 

If you would allow use of SCOPE_ACTIVE_SKIN or better still fix SCOPE_CURRENT_SKIN to also search skin_default when looking for images then this would be easily possible.  The images can't be forced into skin_default as that would mean that skin developers would never be able to reskin the VirtualKeyBoard.  For example, skin_default is for 1280x720 skins.  1920x1080 skin developers would need to use different images.

 

I raised this issue with you earlier (start reading from post #87) but you said you didn't understand me and never followed up with me when I tried to explain this to you.

 

Regards,

Ian.

Edited by IanSav, 17 August 2018 - 18:44.

[littlesat]

Inwas more thinking about having different default_skin for sd,
1280x720 and 1920x1080 skins

[ims]

E.g. here...

https://github.com/l...1772fb27fb17563

Ok, If you want not VK in center, revert it then...

Edited by ims, 17 August 2018 - 22:19.

[ims]

Very nice argument, if there was more than 11 years used buttons, but new users want deferent buttons (if they know what they want ... VIX ?) ... are we in M$ ?

Could be VK switcheable, pls ? Old/new ?

 

PS: some people cannot count square content yet... cancel the square!

[littlesat]

Isn’t it possible to keep the cursor move with the channel buttons!

[ims]

Isn’t it possible to keep the cursor move with the channel buttons!

Do what you want. Fortunately, in homebuild it is possible ...

 

Btw. will somebody update font's date in enigma.bb or no ?

[Persian Prince]

Isn’t it possible to keep the cursor move with the channel buttons!

Do what you want. Fortunately, in homebuild it is possible ...
 
Btw. will somebody update font's date in enigma.bb or no ?

PR created: https://github.com/O...e-core/pull/515

[IanSav]

Hi Littlesat,

 

Inwas more thinking about having different default_skin for sd,
1280x720 and 1920x1080 skins

 

The skin_default was intended as an emergency fall back skin with a resolution of 1280 x 720..  I don't think we should play with it.

 

Perhaps a better idea would be to create an image library directory within Enigma2.  The library could have sub directories called 720, 1080, 2160 and 4320 for HD, FHD, 4K and 8K resolutions.  Within those directories could be a range of directory to match the usual directories found in skins like "buttons", "countries", "icons" etc.  The SCOPE_CURRENT_SKIN could then be updated to look for images in the current skin, if the image is not found then look in the image library using the subdirectory that matches the current resolution to find the image.  If this also fails then fall back to looking in the skin_default for the image.  If all this fals the the image will not be found and the skin can report an error.

 

If all the images managers agree then perhaps this image library could become the updated and modern replacement for skin_default.

 

What do you think?

 

Regards,

Ian.

[IanSav]

Hi Ims,

 

Very nice argument, if there was more than 11 years used buttons, but new users want deferent buttons (if they know what they want ... VIX ?) ... are we in M$ ?

Could be VK switcheable, pls ? Old/new ?

 

PS: some people cannot count square content yet... cancel the square!

 

You guys have been very fast to criticise my proposed changes.  Often I feel that you haven't even considered what I am saying and/or you don't test the sample code I provide.  Please give this new system a try and watch how all the changes come together.  You will see that I am working towards a bigger, and better, picture.

 

If people really don't want to use the proposed consistent mapping of buttons the why not have those users copy the keymap.xml file to /etc/enigma2 and then customise it as they want?

 

Regards,

Ian.

[littlesat]

It is a new concept with risks... that was why also Ims was sceptic. And as a lot did change it might need another thread of adjustments

[Persian Prince]

Hi Persian Prince and other skin developers,

 

It looks like my cursor image in the 1080 image set for the VirtualKeyBoard is incorrect.  The cursor is coloured yellow rather than white.  Please use the attached version in ALL 1080 sized skins.

 

Regards,

Ian.

 

Done: https://github.com/l...-PLiHD/pull/687

 

[IanSav]

Hi Persian Prince,

 

Does the fixed image make the display look better?  You should now find the LOC button and the position cursor look different! 

 

Thank you for promptly attending to the problem.

 

Regards,

Ian.

[IanSav]

Hi Littlesat,

 

If it helps you to understand more of my vision here is the current development version of the action map from the new ConfigList.py redevelopment.  This will be the UI for ALL the updated configuration screens.

self["config_actions"] = HelpableNumberActionMap(self, "ConfigListActions", {
	"cancel": (self.keyCancel, _("Cancel any changed settings and exit")),
	"close": (self.closeRecursive, _("Cancel any changed settings and exit all menus")),
	"save": (self.keySave, _("Save all changed settings and exit")),
	"ok": (self.keyOK, _("Select, toggle, process or edit the current entry")),
	"menu": (self.keyMenu, _("Display selection list as a selection menu")),
	"top": (self.keyTop, _("Move to first line")),
	"pageUp": (self.keyPageUp, _("Move up a screen")),
	"up": (self.keyUp, _("Move up a line")),
	"first": (self.keyFirst, _("Jump to first item in list or the start of text")),
	"left": (self.keyLeft, _("Select the previous item in list or move cursor left")),
	"right": (self.keyRight, _("Select the next item in list or move cursor right")),
	"last": (self.keyLast, _("Jump to last item in list or the end of text")),
	"down": (self.keyDown, _("Move down a line")),
	"pageDown": (self.keyPageDown, _("Move down a screen")),
	"bottom": (self.keyBottom, _("Move to last line")),
	"toggleOverwrite": (self.keyToggleOW, _("Toggle new text inserts before or overwrites existing text")),
	"backspace": (self.keyBackspace, _("Delete the character to the left of cursor")),
	"delete": (self.keyDelete, _("Delete the character under the cursor")),
	"1": (self.keyNumberGlobal, _("Number or SMS style data entry")),
	"2": (self.keyNumberGlobal, _("Number or SMS style data entry")),
	"3": (self.keyNumberGlobal, _("Number or SMS style data entry")),
	"4": (self.keyNumberGlobal, _("Number or SMS style data entry")),
	"5": (self.keyNumberGlobal, _("Number or SMS style data entry")),
	"6": (self.keyNumberGlobal, _("Number or SMS style data entry")),
	"7": (self.keyNumberGlobal, _("Number or SMS style data entry")),
	"8": (self.keyNumberGlobal, _("Number or SMS style data entry")),
	"9": (self.keyNumberGlobal, _("Number or SMS style data entry")),
	"0": (self.keyNumberGlobal, _("Number or SMS style data entry")),
	"gotAsciiCode": (self.keyGotAscii, _("Keyboard data entry"))
}, prio=-1, description=_("Common Setup Functions"))

self["VirtualKB"] = HelpableActionMap(self, "VirtualKeyboardActions", {
	"showVirtualKeyboard": (self.KeyText, _("Display the virtual keyboard for data entry"))
}, prio=-2, description=_("Common Setup Functions"))

These navigation options will then move to other UI elements like list boxes, menus etc.  Can you see how a unified plan for navigation will make the UI more predictable and usable for everyone?

 

Regards,

Ian.

[littlesat]

You take a risk... e2 people are used to how it works now... and a lot of them do not want to change what they are used to for 15 years and more... so do these kind of thinks with care... the virtual keyboard is not that invasive as this one... please describe the changes and discuss before you start coding...

[IanSav]

Hi Littlesat,

 

It is a risk but I am working hard on making this change one make things better.  If users see that the new way is better they might embrace it. 

 

The coding is already about 95% complete.  If you want to have discussions about the new Setup system then please start a new thread and we can talk about it.

 

Regards,

Ian.

[Rob van der Does]

 e2 people are used to how it works now... and a lot of them do not want to change what they are used to for 15 years and more...

If we adhere to that thought nothing will ever change....

E2 is meant for hobbyists, not for people who want a working-out-of-the-box experience; they should stick to decoders provided by their providers.

And hobbyists only want one thing: improvement(s)!

Edited by Rob van der Does, 18 August 2018 - 17:32.