Since the new version of RapidPHP 2022 v17.2 I noticed, that if a hex value is double-clicked, the hash (#) is not selected anymore. This is something I somewhat hate about Notepadd++ and it was never the case in versions of RapidPHP before (hence I liked RapidPHP from the start).
But now it is and copy&paste HEX values from i.e. the colorpicker is now _EXTREMELY_ annoying because when copying from there, all is copied, also the hash.
So, when you copy a hex value from the colorpicker and want to insert it onto an existing value, double clicking the old value selects only the six characters. If you are too fast with pasteing, you maybe not noticing the resulting double hash (##FFFFFF) or you have to first double backspace before pasteing. Both versions are NOT helpful when editing CSS and stop workflow/speed.
Please change this back.
HEX selection crippled
Moderator: kfury77
Forum rules
Please try to follow these guidelines. This will help to receive faster and more accurate response.
Please try to follow these guidelines. This will help to receive faster and more accurate response.
- Check the Support section of the corresponding product first. Chances are you will find your answer there;
- Do not create new topics for already reported problems. Add your comments to the existing topics instead;
- Create separate topic for each problem request. Do NOT post a number of non-related problem reports in a single topic;
- Give your topic a meaningful title. Titles such as "A question," "Bug report" and "Help!" provide others no clue what your message is about;
- Include the version number of the software you are using;
- This is not an official customer support helpdesk. If you need a prompt and official response, please contact our support team directly instead. It may take a while until you receive a reply in the forum;
Re: HEX selection crippled
This appears to be a bug. We'll try to fix it in the next update.
Blumentals Software Programmer
-
- Posts: 68
- Joined: Tue Aug 12, 2014 5:01 pm
Re: HEX selection crippled
Thanks.Aivars wrote:This appears to be a bug. We'll try to fix it in the next update.