Leaderboard

..that #121212 was way too dark for my taste but the #202020 I like and is closer to Explorer_DarkMode background's color. and the S1 to S15 correlates to the SciTE colors so making something that edits the CSS would be simple from that.... or, Just use whatever is used as a base CSS ( by selecting a SciTE config ) and just add the Sxx to the CSS. Back to the web-darkMode-css. I'll use the 2nd one ( #202020 ) for the mockup page once I settle on how to implement it I'll hopefully get it done before Monday.

Ah, I see, I hadn't even seen that option before Thanks for pointing that out. Everything makes much better sense now. Sounds like a pretty good plan, that could end up pretty cool for sure. I suppose one thing Scite Config would need to add would be an "Import/ file chooser for the custom themes? Unless I'm missing it. I've found that out somewhat over time, but I keep finding it's more extensive than I thought. Thanks. I may not be done, but here is what I have so far for a dark theme for the site, maybe help with some inspiration? One is my own attempt, the other is attempting to copy Scite's dark theme as much as possible. (Once I found out about it 🙄) I may try to re-use more Scite colors in it, now that I understand better the main plan. (Sorry for the denseness. Thanks for your patience.) My Theme Scite based Theme Not sure if it will help any... Scite Dark default.css My dark default.css

Yes, that is understood. But if we take color editor and also apply that to the a css to have matching edits, then that's another story. ( that to be fair, I haven't look at anything yet. Just dreaming and guessing. )

I haven't looked at the details yet but when all it takes to change the colorscheme of the helpfile is to copy a file to the used ccs file, then my suggestion would be to create a matching filename to the current scite schemes which gets copied over when another scheme is chosen in sciteconfig. When there is no mathing helpfile scheme we just revert back to the default helpfile scheme. So what exactly is required for me to have a look at this and have a play?

What he agreed as far as I understood is that if there is a matching theme: then is not a big deal. If someone takes on replicating colors individually to also apply to a custom.css, then that would be awesome. But there are more colors in the css than there are in SciTE, so it would be tricky. That's why I said "Or a separate script. We'll have to brainstorm it.". If we are to edit the css with custom colors, we should start by creating a separate script just for that, with the form looking like the one we intend to merge with and similar coding style, for the same reason. Also, a user would find it familiar with what he/she knows how to work with. Then we can open an "after market" forum post for the themes that don't come with the standard distribution. Then maybe a WiKi entry with a sample pic. and an accompanying zip with 4 files ( the pic., css, SciTE and a readme.txt ). The wiki is because it'd be a showroom, ..because I know that the forum post is going to be full of chatter. Again. Baby steps. I don't want to scare anyone with a bunch of talk until we have something to show. Trivia time: did you know that many of the goodies that come standard with SciTE started as scripts in the Example forum ?

Done. Thanks

DO NOT post an image. Just Copy/paste the consolewrite from console content in here.

If I remember well some drivers don't handle well varchar(max) so if you have control over table definition just use varchar(8000). I tested with ODBC Driver 17 for SQL Server and works well. #include <Debug.au3> MsSqlQueryTest() Func MsSqlQueryTest() Local $sDatabase = 'master' ; change this string to YourDatabaseName Local $sServer = '(local)' ; change this string to YourServerLocation Local $sUser = 'sa' ; change this string to YourUserName Local $sPassword = 'test' ; change this string to YourPassword Local $sDriver = 'ODBC Driver 17 for SQL Server' Local $sConnectionString = 'DRIVER={' & $sDriver & '};SERVER=' & $sServer & ';DATABASE=' & $sDatabase & ';UID=' & $sUser & ';PWD=' & $sPassword & ';' Local $oConnection = ObjCreate("ADODB.Connection") $oConnection.ConnectionString = $sConnectionString $oConnection.Open Local $sQuery $sQuery &= "SET NOCOUNT ON" & @CRLF $sQuery &= "DECLARE @MyTable TABLE (id INT, myValue varchar(8000), pdata varchar(8000))" & @CRLF $sQuery &= "INSERT INTO @MyTable VALUES (123, '+OK', '<root><receipts><receipt><command name=" & '"REPORTDAY"' & " /></receipt></receipts></root>')" & @CRLF $sQuery &= "SELECT id, myValue, pdata FROM @MyTable" Local $oRecordSet = $oConnection.Execute($sQuery) Local $array = $oRecordSet.GetRows _DebugArrayDisplay($array) EndFunc Alternatively some drivers support DataTypeCompatibility in connection string, so you might give a try. If you don't have control over table definition, you can cast data in the query: #include <Debug.au3> MsSqlQueryTest() Func MsSqlQueryTest() Local $sDatabase = 'master' ; change this string to YourDatabaseName Local $sServer = '(local)' ; change this string to YourServerLocation Local $sUser = 'sa' ; change this string to YourUserName Local $sPassword = 'test' ; change this string to YourPassword Local $sDriver = 'ODBC Driver 17 for SQL Server' Local $sConnectionString = 'DRIVER={' & $sDriver & '};SERVER=' & $sServer & ';DATABASE=' & $sDatabase & ';UID=' & $sUser & ';PWD=' & $sPassword & ';' Local $oConnection = ObjCreate("ADODB.Connection") $oConnection.ConnectionString = $sConnectionString $oConnection.Open Local $sQuery $sQuery &= "SET NOCOUNT ON" & @CRLF $sQuery &= "DECLARE @MyTable TABLE (id INT, myValue varchar(max), pdata varchar(max))" & @CRLF $sQuery &= "INSERT INTO @MyTable VALUES (123, '+OK', '<root><receipts><receipt><command name=" & '"REPORTDAY"' & " /></receipt></receipts></root>')" & @CRLF $sQuery &= "SELECT id, CAST(myValue as varchar(8000)), CAST(pdata as varchar(8000)) FROM @MyTable" Local $oRecordSet = $oConnection.Execute($sQuery) Local $array = $oRecordSet.GetRows _DebugArrayDisplay($array) EndFunc