Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Dimitrij
    @Kvarkas
    image.png
    ah one moment
    you mean cant see table?
    Vestik
    @vestik:matrix.org
    [m]
    I have added the new resource, but
    I don't have this AmazonInstance property.
    Dimitrij
    @Kvarkas
    you should add it first to Language.resx
    image.png
    Vestik
    @vestik:matrix.org
    [m]
    I did, but the line didn't appear. does it appear for you?
    Dimitrij
    @Kvarkas
    have you saved a project changes once added?
    dont see any issue, perhaps rebuild?
    Dimitrij
    @Kvarkas
    Fyi - 1.77.2-dev updated with fix for broken links
    Vestik
    @vestik:matrix.org
    [m]
    guys, what do you think, is this change good, or bad (useless):
    *Amazon Instance was added as a new section after "misc"
    Joe Cefoli
    @jcefoli
    Can we use native OS checkboxes in the settings dialog? It takes a long time to open, btw... Why would we be using some sort of custom checkboxes from a library, rather than the native OS implementation?
    11 replies
    Vestik
    @vestik:matrix.org
    [m]
    The comment of that piece of code says that it requires optimization.
    Dimitrij
    @Kvarkas
    @vestik:matrix.org technically its good, but i want separate parent group "Cloud instances" and then Amazon
    in version 1.777.3 I would like to replace that section with html page, so it should load fast and independent of lib
    we keep old method for compatibility but will be new option use Web gui
    4 replies
    david-sway
    @david-sway
    I made pull request mRemoteNG/mRemoteNG#2125 to remedy a problem with the Quick Connect toolbar, but I polluted the PR by making an additional commit to my forked branch. I'm not comfortable enough with my knowledge of Git to untangle this situation, can someone advise?
    david-sway
    @david-sway
    nvm figured it out
    Joe Cefoli
    @jcefoli

    Bugs in the about dialog in 1.77.3 (I compiled the latest)

    1) It tries to load markdown directly from GitHub. Specifically, the develop branch which was removed (btw it's really confusing to change the default branch every release)
    2) The icon is the default Visual studio one and not mR

    Joe Cefoli
    @jcefoli

    I just checked. It's not hard coded to develop, but wherever this is being set, it evaluates to develop which is wrong. Is there updated documentation on the new branching strategy?

    private void llCredits_LinkClicked(object sender, LinkLabelLinkClickedEventArgs e) { OpenUrl("https://raw.githubusercontent.com/mRemoteNG/mRemoteNG/v" + Assembly.GetExecutingAssembly().GetName().Version.ToString().Substring(0, Assembly.GetExecutingAssembly().GetName().Version.ToString().Length - 2) + "-" + Settings.Default.CurrentUpdateChannelType + "/CREDITS.md"); Close(); }

    david-sway
    @david-sway

    I was looking at mRemoteNG/mRemoteNG#2128 when I discovered two settings configuration scenarios that can brick the app.

    If "reconnect to previously opened sessions on startup" and "always show panel selections dialog" are both set True, then on startup when the app tries to reconnect it will present the panel selection form, which cannot be interacted-with because the startup-splash-logo is still present.

    If "Informations" Popups are checked, then when one such popup is displayed, dismissing it will cause a panel focus event, which triggers another popup, which then will cause the same thing to happen when it is dismissed.

    I have two simple and safe solutions to these problems. We can skip the "reopen connections" step if the panel selections dialog setting is true, and we can simply remove the panel focus message entirely. In my mind, though, both of these solutions compromise on functionality
    david-sway
    @david-sway
    Pull request created mRemoteNG/mRemoteNG#2133
    Dimitrij
    @Kvarkas
    Thanks for that, merged
    Bugs in the about dialog in 1.77.3 (I compiled the latest)
    thanks :)
    1) It tries to load markdown directly from GitHub. Specifically, the develop branch which was removed (btw it's really confusing to change the default branch every release)
    it was like that as its will change from version to version so need to be sure it will stay unchanged for released version because develop branch will not stay forever its always moving forward.
    2) The icon is the default Visual studio one and
    will check that, as for now still some merging is happening between 1.77.2-dev and 1.77.3-dev something perhaps was escape from my eye
    Dimitrij
    @Kvarkas
    @jcefoli branching strategy as for now:
    active - default - develop branch is 1.77.3 -dev - all new functionality goes into it.
    sub active - develop (for migration period) is 1.77.2-dev - to merge with 1.77.3 with fixes of current bugs
    pre-release is 1.77.2-preview, and release 1.77.2-release
    Logic as follows: we do coding once we got enough changes we clone 1.y.x-dev branch to 1.y.x-preview, rename branch to 1.y.x+1-dev so we can continue working on new changes. All bug fixes will go to 1.y.x-preview, and if no big complains about bug we clone it to 1.y.x-release branch, after couple of month if we don't get any report about bugs - 1.y.x-preview branch will be deleted, if still any bug will be found it should be addressed in new version. -release branch will be staled for memories :)
    Let me know if you think its not useful optimal or you have you own ideas about branching - I don't try to dictate but want to have clear view what the hell we have on what branch :)
    Joe Cefoli
    @jcefoli
    makes sense, thanks for the explanation. You can branch however you want as the project maintainer. Just trying to get some understanding
    I normally just compile whatever dev branch has unreleased changes, so if these names are going to change all the time, my script will need to be updated, but it's not a big deal

    i usually like when master/main matches the stable release, so if there's an emergency fix needed (and the dev branch features are not ready yet), you can branch off master/main, make the release hotfix and then re-release... Then merge that into the develop branch and then when dev is ready, it merges to master/main and gets released again. And use tags to specify versions

    But please use whatever workflow makes sense for you

    Dimitrij
    @Kvarkas
    well issue we have its a lot of bug/suggestions/feature request - if we keep fixing them all we never release stable version, so what i try to is make a breake point so we can still keep working on new stuff what is needed but stop making that in prerelease so we can release it one day :)
    master branch is a bit to generic and its will have unchangible stuff perhaps but we will see, we may change approach again but we use such kind of versioning at work with a team of 20ish coders and its very easy track cnages and releases so trying as welll implement similarity, hope will not jump to agile methodology to deep :D
    Joe Cefoli
    @jcefoli
    image.png
    I cannot reproduce this, so I cannot file it, but this happens to me constantly... Usually when I use normal built in RDP to RDP to a jump server, and I use mRemoteNG on that jump server. The window class gets detatched from the tab, and you cannot close the tab at all, even though there is no RDP session in it:
    Usually happens when I leave all the connections connected and minimize the main RDP from my local laptop, then go back to it later. The first tab in mRemoteNG has messed up scale, where the start menu is off the screen, and you cannot close the tab or reconnect it. And finally, you get that error message. Only way to clear the condidion is to restart the program
    Was a bug from when all the tabs were refactored with the new lib version
    Joe Cefoli
    @jcefoli
    Still cannot reproduce this but I may have stack traces now: mRemoteNG/mRemoteNG#2166
    Dimitrij
    @Kvarkas
    interisting
    Joe Cefoli
    @jcefoli

    I was testing this feature that was just added and I cannot get it to work. Trying it on Win Server 2019, with the protocol version set to RDC9 and Fit To Panel and Autommatic Resize set to yes mRemoteNG/mRemoteNG@37fc611

    It always reconnects and usually fails reconnecting

    Joe Cefoli
    @jcefoli
    Yeah, something is seriously buggy with whatever was done with autoconnect because I'm getting random disconnects now, and it goes to automatically reconnect and fails until I reconnect manally
    Joe Cefoli
    @jcefoli
    I really don't like the Wix dependency
    I don't want to install the antique .net 3.5 framework on my system
    I read the dev docs and saw you can unload the installer project in Visual Studio to not build the installer. I build the portable version for local testing and it still requires wix.
    Joe Cefoli
    @jcefoli
    and I do this from the CLI like this:
    nuget restore C:\Git\MremoteNG\mRemoteNG.sln
    
    "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\msbuild.exe" /nologo /p:Configuration="Release Portable";Platform=x64 C:\Git\MremoteNG\mRemoteNG.sln
    Joe Cefoli
    @jcefoli
    I installed it just to get unblocked, it's no big deal