Minimizable and non-maximizable window

michyo

I want to open a window that has a minimize button but no maximize button (or disabled). This is because I want my app to be minimizable for user convenience, but I don't want it to be maximizable because I don't want the extra space in the window I designed.

I have tried 4 different styles: dialog, fixed, float, single, but none of them achieve this. And, I have looked for properties, but have not found anything that would help me achieve this.

Is it possible to enable this?
Thank you.

Samir

Hi Michyo,

Welcome to LuaRT Community.
For now, the ui module don't provide this kind of functionnality.

I will see how it can be implemented.

michyo

Hi Samir,

I understand currently it doesn't have that function.

I'm really looking forward to the day when LuaRT will have that feature.

I find LuaRT such a great tool that I have no regrets about switching my main development environments to LuaRT, as long as It has this feature and full screen with no title bar. 😉

Thank you.

Samir

You're welcome Michyo !

As a side note, full screen Window is implemented and will be available in next update 👍🏻

michyo

Hearing it makes me even more excited for the next release.

I teach programming in Japan and have already started rewriting all my basic courses that I used to teach using other tools to use LuaRT.

I will continue to look into this place with excitement. 🙂

Samir

michyo I teach programming in Japan and have already started rewriting all my basic courses that I used to teach using other tools to use LuaRT.

Wow, well, I'm very honored by that! Thank you!

Samir

Update :

The "single" Window style will disable the maximize button.
It also makes sense that this Window style cannot be maximized since it is not resizable.

It will be available in next LuaRT release.

michyo

How wonderful!
I'm waiting with great anticipation for the day of the next release.

Thank you! 😆

michyo

I have tried Version 1.4.0.
I find these features implemented in it very attractive.

However, I found it a little inconvenient that the window size is changed from the original size when app returns to the original windowed mode from the full screen mode. (In my environment, after returning to windowed mode, it was fixed to 625x451.)

I can manually restore it to its original size, but when doing so, it flickers for a moment.

Anyway, thank you for implementing these very wonderful features! 😆

Samir

Yes I'm working on a better implémentation 👍🏻

Samir

Update :

The Window.fullscreen property now works as expected.
When returning from fullscreen, the original Window position will be restored.

It will be available in next bugfix release, and will be committed today on the GitHub repository

michyo

Thank you very much!
Immediately I tried to build it from source code, but I couldn't get past the make error like these.

[@MinGW]
X:\xxxxxx\LuaRT\src>make PLATFORM=x86 ▸ Building Lua 5.4.5 VM ■■■■■■■■■■■■■■■■■■■ ▸ Building LuaRT core framework Makefile:145: recipe for target 'libsensapi.a' failed make[1]: *** [libsensapi.a] Error 1 Makefile:21: recipe for target 'core/.' failed make: *** [core/.] Error 2

[@MSYS2]
xxxxx@XXXXXXXX MINGW64 /x/xxxxxx/luart/src $ make make: *** [Makefile:21: core/.] Error 127

Something I must be making a simple mistake, but I don't have much more time to fight this now, so I'll look forward to your next release. 😅

Samir

You must probably compile LuaRT on an x86 version of Windows.
Try replacing line 145 with the following in the Makefile in src\core\ :

@gendef $(call normalize-path,$(firstword $(wildcard $(windir)\syswow64\SensApi.dll $(windir)\system32\SensApi.dll))) >nul 2>&1

(the check with the $firstword macro don't seem to work as expected)

Sorry for this !

PS: Msys2 build is not supported

michyo

1️⃣ I have tried it. And it still output similar error.

▸  Building Lua 5.4.5 VM
▸  Building LuaRT core framework  Makefile:145: recipe for target 'libsensapi.a' failed
make[1]: *** [libsensapi.a] Error 1
Makefile:21: recipe for target 'core/.' failed
make: *** [core/.] Error 2

2️⃣ Next I installed MinGW-W64-binaries and tried. It caused yet another error.
[Login to see the link]

━━━━━━━━━━━━━━━━━━━━  Building LuaRT 1.4.0 for x64  ━━━━━━━━━━━━━━━━━━━━

▸  Building Lua 5.4.5 VM          ■■■■■■■■■■■■■■■■■■■
▸  Building LuaRT core framework  ■■■■■■■■■■■■■■■■■■■■■sys\File.c: In function 'File_getbuffered':
sys\File.c:582:44: error: 'FILE' {aka 'struct _iobuf'} has no member named '_flag'
  582 |         return lua_self(L, 1, File)->stream->_flag & 0x100 ? _IOFBF : _IONBF;
      |                                            ^~
sys\File.c:583:1: warning: control reaches end of non-void function [-Wreturn-type]
  583 | }
      | ^
make[1]: *** [Makefile:140: sys\File.o] Error 1
make: *** [Makefile:22: core/.] Error 2

I have tried many things but have not been able to solve the error.

▶️ I am beginning to think that maybe this is caused by the MinGW-W64 I installed is UCRT ver. and not MSVCRT ver. I would like to see if that hunch is correct, but now my time is up...😢

michyo

I read this and changed my environment to WinLibs standalone build and tried.
[Login to see the link]

But now, I got another error...

â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”  Building LuaRT 1.4.0 for x64  â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”

▸  Building Lua 5.4.5 VM          ■■■■■■■■■■■■■■■■■■■
▸  Building LuaRT core framework  ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■
▸  Building LuaRT toolchain       ■C:/apps/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.1.0/../../../../x86_64-w64-mingw32/lib/../lib/crt2.o:crtexe.c:(.xdata+0x2c): relocation truncated to fit: IMAGE_REL_AMD64_ADDR32NB against symbol `__C_specific_handler' defined in *UND* section in C:/apps/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.1.0/../../../../x86_64-w64-mingw32/bin/ld.exe generated
C:/apps/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.1.0/../../../../x86_64-w64-mingw32/lib/../lib/crt2.o:crtexe.c:(.xdata+0x50): relocation truncated to fit: IMAGE_REL_AMD64_ADDR32NB against symbol `__C_specific_handler' defined in *UND* section in C:/apps/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.1.0/../../../../x86_64-w64-mingw32/bin/ld.exe generated
collect2.exe: error: ld returned 1 exit status
make[1]: *** [makefile:191: luart.exe] Error 1
make[1]: write error: stdout
make: *** [makefile:22: core/.] Error 1

I'll try again when I have more time.

Samir

I'm very sorry for that...
I'm using mingw-w64 8.1.0 SEH from [Login to see the link]

I realize how unreliable this development environment is because of the different distributions and versions of mingw-w64...

I'm really wondering about switching to the Microsoft C compiler cl.exe...

michyo

Thanks for the information of the environment you are using. 😊
I downloaded it and tried, however unfortunately my situation did not improve much.

â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”  Building LuaRT 1.4.0 for x64  â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”

▸  Building Lua 5.4.5 VM          ■■■■■■■■■■■■■■■■■■■
▸  Building LuaRT core framework  ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■
▸  Building LuaRT toolchain       ■■■■■■■■■■■■■■■■■■
make[1]: write error
Makefile:21: recipe for target 'core/.' failed
make: *** [core/.] Error 1

At the moment I don't know what that is, but my environment may be under some unique kind of curse... In this matter, since I don't do anything patchy deal with MinGW and since I clean everything and install a new environment each time, I have a feeling that this is somehow a problem that is not caused by the individual MinGW environment. 🤔

Samir

The write error means the compiler have been prevented to generate a file... Maybe an antivirus issue ? 🤔

michyo

Since I do development all the time every day, the only antivirus tool I have is the standard Windows Defender. And I am confident that I'm not affected by it because I'm used to dealing with it. (In the past days, I was sick and tired of the days that every time I compile something, it is disinfected as a virus immediately...) 🙂

Until my previous post, I had been working on a Windows 11 PC, but now I tried the same process on another Windows 10 old PC and immediately the build succeeded with no error.

━━━━━━━━━━━━━━━━━━━━  Building LuaRT 1.4.0 for x64  ━━━━━━━━━━━━━━━━━━━━

▸  Building Lua 5.4.5 VM          ■■■■■■■■■■■■■■■■■■■
▸  Building LuaRT core framework  ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■
▸  Building LuaRT toolchain       ■■■■■■■■■■■■■■■■■■

▸  Building module audio 0.2      ■■■
▸  Building module canvas 0.3     ■■■■
▸  Building module crypto 1.0
▸  Building module json 0.5       ■
▸  Building module net 1.2
▸  Building module webview 0.5    ■■■

I seem to have gotten 6 EXEs and 1 DLL now in bin dir. I will try them. Thanks for your support‼😊

michyo

I am writing this for the benefit of those who follow me in trying the same thing.

1️⃣ I rewrited line 145 of src/core/Makefile as follows.

gendef C:\Windows\SysWOW64\SensApi.dll

2️⃣ I added these lines at the top of /src/modules/crypto/Makefile.

libsensapi.a:
	gendef C:\Windows\SysWOW64\SensApi.dll

3️⃣ I added these lines at the top of /src/modules/net/Makefile.

libsensapi.a:
	gendef C:\Windows\SysWOW64\SensApi.dll

▶️ With these 3 changes, and with this MinGW-W64 distro, I got 32-bit version of the LuaRT EXEs & DLL on the 64-bit Windows.

MinGW-W64 GCC-8.1.0 i686-posix-dwarf
[Login to see the link]

I hope this information is useful to someone‼😉

cos00kun

michyo
You write all the problems very neatly and very descriptively. Your students must be very lucky 🙂