• Options
• Login
• Register
• Desktop Style
• Accelerated Mobile Pages Theme

[BUG] Unable to use 0 at beginning of Snippet's name when it is a macro

• Index

  • Jean Lalonde Support Forum
  • QUICK ACCESS POPUP FORUM
  • QAP SUPPORT
  • [BUG] Unable to use 0 at beginning of Snippet's name when it is a macro
• [BUG] Unable to use 0 at beginning of Snippet's name when it is a macro

• [BUG] Unable to use 0 at beginning of Snippet's name when it is a macro

  Popleft > 2023-08-01 09:51

  How to recreate:
  
  1] Create something as basic as Snippet with Short name for menu entitled 01
  
  2] Select it and switch it to
  
  Edit > Advanced Settings > Macro mode
  
  and OK it
  
  3] Take notice as 01 has turned into 1
  
  
  
  I am using version 11.6.2.2 portable on Windows 10 Enterprise 20H2 x64

• RE: [BUG] Unable to use 0 at beginning of Snippet's name when it is a macro

  Horst > 2023-08-01 10:38

  Confirmed

• RE: [BUG] Unable to use 0 at beginning of Snippet's name when it is a macro

  Jean Lalonde > 2023-08-08 15:24

  In fact, this is not specific to snippets. This happens for any type of favorite. But there is an easy solution.
  
  This happens because AHK (development platform used to build QAP) is very permissive regarding variables types. In this case, if you enter only "01" as name, AHK will consider it as a number and will automatically remove the leading zero. This happens ONLY if the name starts with a number and does not contain any text after.
  
  If you need a favorite name to be "01", "002", etc. the simple solution is to add a space at the end of the name: "01 ", "002 ", etc. Because of the space (or any other text) added to the name, this will be considered as text and will not be altered.
  
  Should it be considered as a QAP bug or not? I won't argue about that but I'm happy to suggest a solution that will not require any coding from my part :-)

• RE: [BUG] Unable to use 0 at beginning of Snippet's name when it is a macro

  Popleft > 2023-08-18 04:09

  (2023-08-08 15:24)Jean Lalonde Wrote: [...]
  
  If you need a favorite name to be "01", "002", etc. the simple solution is to add a space at the end of the name: "01 ", "002 ", etc.
  
  [...]

  
  It has worked for me only once, when I wrote
  
  

  Code:

  01___

  
  
  [i.e. with 3 pauses] and switched to
  
  Edit > Advanced Settings
  
  tab. I tried adding more on less pauses, leading pauses, more zeros, switching through tabs - and I did not manage to sustain newly adjusted names
  
  
  This trick apparently works only for newly created entries- so if a user will make some sort of mistake or forgets to include something then there is in other way to correct this other than deleting such ill entry and creating it from scratch

• RE: [BUG] Unable to use 0 at beginning of Snippet's name when it is a macro

  jason2080m > 2023-08-19 03:07

  Confirmed

• RE: [BUG] Unable to use 0 at beginning of Snippet's name when it is a macro

  Jean Lalonde > 2023-08-23 16:34

  > This trick apparently works only for newly created entries
  
  True.
  
  This bug is now fixed in my dev environment. This will be included in the next release.

• RE: [BUG] Unable to use 0 at beginning of Snippet's name when it is a macro

  Jean Lalonde > 2023-08-29 11:05

  Now available in v11.6.2.3
  https://forum.quickaccesspopup.com/showt...p?tid=2584

• RE: [BUG] Unable to use 0 at beginning of Snippet's name when it is a macro

  dr Winchell > 2023-08-29 11:19

  (2023-08-29 11:05)Jean Lalonde Wrote: Now available in v11.6.2.3
  https://forum.quickaccesspopup.com/showt...p?tid=2584

  
  Hi Jean,
  
  I think that linked post for the download is missing:
  
  "You can download the new release here:
  
  https://www.quickaccesspopup.com/downloa...ess-popup/"
  
  Best Regards, Dale

• RE: [BUG] Unable to use 0 at beginning of Snippet's name when it is a macro

  Jean Lalonde > 2023-08-29 13:02

  > I think that linked post for the download is missing:
  
  Fixed. Thanks.

• RE: [BUG] Unable to use 0 at beginning of Snippet's name when it is a macro

  Popleft > 2023-09-14 05:19

  (2023-08-23 16:34)Jean Lalonde Wrote: [...]
  This bug is now fixed
  [...]

  
  And so it seems
  
  Thank you
• Next Oldest Next Newest