Version 2.0 beta released in a new topic [http://forums.winamp.com/showthread.php?t=396961]
Ultra-Modern UI
Collapse
X
-
Comment
-
-
Hi!
I need some help. I tried to compile my scripts with this Ultra-Modern User Interface to see how the installer look like. If I use the standard pages all works fine. But I have some small modifications in some pages, for example in the Finish page. I'm not familiar with this InstallOptions plug-in, but I saw how the page is created and similar to this, I made my modifications. As a result I see what I need and it works as expected, but the new text that I have added (I created one more field with a check-box) has different color - the background is grey instead of blue and the text is black instead of white. Probably there is an easy explanation about this, but as I already said, I'm not familiar with InstallOptions plug-in and I couldn't find the answer in the documentation and in the forum.
Comment
-
-
Meantime I fixed the problem by inserting of few lines like these for my new fields:
GetDlgItem $MUI_TEMP1 $MUI_HWND ${UMUI_INTERNAL_FIDSIXTH}
!insertmacro UMUI_IOPAGECTLTRANSPARENT_INIT $MUI_TEMP1
I don't know what they are doing (probably they make the field background transparent), but now all looks like it should be.
Comment
-
-
Fixes and Additions
In the last two years I used "NSIS 2.46.5 - Unicode" together with "UMUI 1.0b2" and did some additions and fixes for it (e.g. the PRE functions were not available for all pages).
Additionally I have some translated text in languages which were empty or incomplete.
I now had a look at UMUI 2.0b1 together with NSIS3 - and it seems that most of my changes (even the fixes) are still meaningful.
@SuperPat: are you interested in my changes?
If yes, how can I provide them to you? As a zip file with the whole package?
Step by step with small patches?
Shall I sign up to github and add it there (never did that)?
Comment
-
-
Bulgarian translation
Hey, SuperPat,
I have translated the UMUI 2 language file into Bulgarian using "Contrib\UltraModernUI\Language files\English.nsh" as a template.
I am attaching it to this post, but please tell me if there is some other way in which to submit translations, since I couldn't find any.Attached Files
Comment
-
-
Old UltraModernUI v1.0 Thread
Originally Posted by laterist View PostHey, SuperPat,
I have translated the UMUI 2 language file into Bulgarian using "Contrib\UltraModernUI\Language files\English.nsh" as a template.
I am attaching it to this post, but please tell me if there is some other way in which to submit translations, since I couldn't find any.
Comment
-
-
UltraModernUI MUI_UNPAGE_SERIALNUMBER and UMUI_UNPAGE_ADDITIONALTASKS
Among UltraModernUI's great custom pages are 2 that take function parameters: MUI_PAGE_SERIALNUMBER and UMUI_PAGE_ADDITIONALTASKS.
I may be doing something wrong, but the uninstaller versions, e.g., UMUI_UNPAGE_SERIALNUMBER and UMUI_UNPAGE_ADDITIONALTASKS don't appear to work because it seems to be trying to call the function parameters during the install ("non-uninstall") phase.
I've tried many variations, but no luck. Attached is a quick test script to show the behavior.
I know both functions seem a bit strange to include in an uninstaller, but I have a need for the former.code:
Call must not be used with functions starting with "un." in the non-uninstall sections.
Usage: Call function_name | [:label_name]
Error in macro MUI_INSTALLOPTIONS_WRITE_DEFAULTCONVERT on macroline 14
Error in macro UMUI_FUNCTION_SERIALNUMBERPAGE on macroline 16
Error in macro UMUI_PAGE_SERIALNUMBER on macroline 35
Error in macro UMUI_UNPAGE_SERIALNUMBER on macroline 7
Error in script "UnSerialTest.nsi" on line 23 -- aborting creation processAttached Files
Comment
-
-
Old UltraModernUI v1.0 Thread
you need to replace
!insertmacro MUI_UNPAGE_CONFIRM
by
!insertmacro UMUI_UNPAGE_CONFIRM
and all works fineAttached Files
Comment
-
-
Hi, @SuperPat. Yes, as you found, there were a few issues with that incarnation of my test file, but the main issue was with the missing MUI_PAGE_UNINSTALLER_FUNCPREFIX defines that I reported on GitHub and that you resolved on Oct 31.
Thanks again!
Comment
-
Comment