Hi all need the latest thin basic issue. My last built I have downloaded couldn't show code view with scilexer... Cannot see any code line. Best regards Frank
Printable View
Hi all need the latest thin basic issue. My last built I have downloaded couldn't show code view with scilexer... Cannot see any code line. Best regards Frank
Hi all.. I am using and Testing latest Beta 1.11.7.0 of thinbasic. Using window 10 with my Notebook. But Something ist wrong with thinair cannot See any Code Line on Screen .. File however is running .. anybody can Help? See Pics below
OK found thinbasic Version 1.11.60 and its running Well Here
Ciao Renč
I and some of my colleagues use thinAir under Windows 10 and Windows 11 every day in different computer at home and office and never had that issue.
So difficult to replicate.
Anyway, I hope next week I will be able to publish a new 1.11.7 beta
Renč,
here you can find the latest beta 1.11.7 version I'm working on: https://www.thinbasic.com/public/__ForRene__/
Let me know if you have the same problems
Eros
Am not sure what problems have been repaired - guess you posted to the wrong thread here...
Still incorrect: horizontal scrollbar thinAir-codewindow
uncommented dash-line "---~...~---"when fast clicking the codewindow
Suggested improvements:
Add a "Users\"- subfolder to App_Path & "thinAir\"
Add subfolders in App_Path & "thinAir\Users\":
"_shared\" alias thinAir_sharedUsersPath,
"_default\" alias thinAir_defaultUsersPath
App.Environ.Username & "\" Alias thinAir_currentUsersPath
let thinAir check the presence of these folders and create the thinAir_currentUserPath when a new user launches thinAir
move all officially provided templates, tools (ini-files), theme-files etc. to thinAir_sharedUsersPath
compress the thinbasic-samples-folder (zip or 7z) and put it together with the already compressed SDK-archive into the
thinAir_sharedUsersPath.
Add one more tabpage where we have "explorer" and "codebrowser" with a tree that displays the content of the "Samples",
allow below the tree a small textbox provide a description-text for each sample-file and add an extract-button that will
unzip the selected sample and store it in thinAir_CurrentUserPath & "Samplescripts\..." using the same subfolder-structure
as the original Samplescripts-Archive, maybe add date & time to the extracted file + a copy of its description-text-file
and give the existing explorer some shortcut-node on top where the current user finds his files.
That will prevent the shipped samples from accidently getting changed and these remain in original condition in the archive.
Tools\Usertools - 2 inifiles actually - the officially shipped tools + Ini may be moved to the _shared-folder, the usertools-ini
should be moved to thinAir_default where for every new user that launches thinAir will be made a copy that goes to the
thinAir_currentUserPath if not present yet.
Same for the User-keywords-ini - that will prevent the user-files from getting overwritten when a new thinbasic-version is installed.
For the purpose of validation the ini- and xml-files should contain a version-number. When any improvements are made then
it can get checked if the previous version-settings still work the same way or - if there were a conversion-tool to update elder files
to a new format - it can be done programmatically.
Some- as themes, script-templates or other settings-files will be located in the _shared-folder for all users. ThinAir should allow to edit these but saves them to the same subfolders of the current user = the original will maintain as shipped, the user-customized files will never get overwritten
during a new installation, thinAir will prefer to load such from current users folder - so every user of the pc has his very own customized VIM-dark-blue- or monokai-theme.
For privacy: A separate thinAir-launcher that will remain in the background could supervize and monitor the thinAir-status - when it gets started, the
launcher could uncompress and decrypt the current users folder - keeps the file open and prevents from any unauthorized access.
When thinAir gets closed - or crashes - the launcher-supervisor will detect that the thinAir-process is not present anymore, so it could encrypt and compress the current users data again. That were an optional security feature for engines that are used by multiple users.
Altogether this would have the effect of thinbasic-scripts located in a subfolder of App_Path - and not within any system-folder as the OS-Users.
Also a thinAir\Users\<_current>\temp would allow more control and less needed privilege, especially when it is about bundling or running from bundle.