Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
VTOY_TEXT_MENU_VER in grub.cfg not working?
#1
/grub/grub.cfg

Code:
if [ "$grub_platform" = "pc" ]; then
    set VTOY_TEXT_MENU_VER="Ventoy $VENTOY_VERSION BIOS  www.ventoy.netXXXXXXX"
else
    set VTOY_TEXT_MENU_VER="Ventoy $VENTOY_VERSION UEFI  www.ventoy.netYYYYYYY"
fi


Menu text is not changed?
Reply
#2
This is only used in txt mode.
For GUI mode, it's a easter egg in the source code.
https://www.ventoy.net/en/plugin_theme.html
Reply
#3
yes - I can't find it in source code.
I want to modify source code so that my version is not confused with yours.
Where is the easter egg laid?
Reply
#4
I suggest that:
1. you put a new background image.
2. You can set a variable in grub.cfg  set VTLE_CLR=#0000ff  or call  grub_env_set("VTLE_CLR", "#0000ff"); in source code. 
This will change the color of this version string. Modify the color value to let it the same with the background where is displayed.
Then the string will not be visible.

As for the easter egg, I still wait for someone to find it  Big Grin
Reply
#5
Thanks for the tip.
I have used cccdce which just about works, but it also makes the version number and the UEFI\Legacy text disappear.
Also, if a user defines his own theme, he will see the text as light grey on his wallpaper again.


/grub/grub.cfg
Code:
...

#export necessary variable
export theme
export gfxmode
export gfxpayload
export vtoydev
export vtoy_path
export vtdebug_flag
export vtoy_iso_part
export vtoy_efi_part
export VENTOY_VERSION
export VTOY_CUR_VIDEO_MODE

set VTLE_CLR=#cccdce
Reply
#6
Yes. 
You can define another hbox in theme.txt and ask user to remain this hbox when they define new theme (like the hotkey tip hbox)
Code:
+ hbox{
    left = 5
    top = 95%
    width = 10%
    height = 25
    + label {text = "1.0.29 BIOS This is a New Ventoy release" color = "red" align = "left"}
}


As for the easter egg, I will point it out at some time if still nobody find it.
Reply
#7
at end of all_in_one.sh I get some errors - see screenshot.
It is does not affect the  .zip file, but I just wondered if there is a problem in the sh file or maybe I am missing something?
P.S. Still not found easter egg


Attached Files Thumbnail(s)
   
Reply
#8
Big Grin 
The eggs are very good. They are very deep. Big Grin
Reply
#9
(11-27-2020, 12:57 PM)Steve2926 Wrote: at end of all_in_one.sh I get some errors - see screenshot.
It is does not affect the  .zip file, but I just wondered if there is a problem in the sh file or maybe I am missing something?
P.S. Still not found easter egg

https://github.com/ventoy/Ventoy/blob/fb...oy.c#L1382
Reply
#10
(11-27-2020, 12:57 PM)Steve2926 Wrote: at end of all_in_one.sh I get some errors - see screenshot.
It is does not affect the  .zip file, but I just wondered if there is a problem in the sh file or maybe I am missing something?
P.S. Still not found easter egg
Did you ever get an answer for the errors in the screenshot.
I am also getting the same errors.  no such file or directory for /ISO_TMP/EFI/ventoy/ventoy.gz
As for the Xorriso cmd not found.  I installed the Xorriso package.
I get the same errors in 1.31 and 1.32 when making the live cd.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)