Jump to content

gitit20

Member
  • Posts

    37
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by gitit20

  1. I knew this was going to die before it even did. I am annoyed he just walked away and didn't give a reason. So many people donated and or paid to have it working properly, and then just cuts and runs without a single reason as to why. I understand sometimes you just can't do something anymore. But you just don't give a big middle finger to your supporters and walk away. 

  2. I loved this for a long time, used it a lot. The only thing that PMO is he never checked back in to say hay guys sorry but do to (whatever) I can no longer support it. or something like that, I mean if he passed on or something that would be diff, but if not and he just up and said screw it and never let us know. I think that is just crappy to do. 

  3. On 9/25/2019 at 4:17 AM, innuendo33 said:

    Did you have a look in Chrome settings ? it should display you set a custom theme if so , then you can set it to default one. ( I can't screen it as I'm not using a custom theme to show you  :/ 

    I set a theme then set it back to default, sadly it didn't work. not sure why but nothing works at all now on chrome zero zip nata. I have even done a complete reload of windows and still cant get it to work with chrome wont work with Firefox or edge.  it works everywhere else though. not sure what the deal is. 

     

  4. On 7/31/2019 at 1:31 PM, JTB3 said:

    For anyone that's using AeroGlass with Chrome Browser (v76+) configured to startup with windows and run in the background, you've probably noticed that the command line switch --disable-windows10-custom-titlebar is NOT remembered at startup time.  Unfortunately, if you manually edit the ChromeAutoLaunch registry key, it will get overwritten every time Chrome exits.

    To address this issue, I created a simple AutoHotkey script that is run 'on login' as a Scheduled Task that automatically adds the necessary startup switch to the required 'ChromeAutoLaunch...' registry key (which has a custom suffix for different users).  I also added a 2nd useful switch --save-page-as-mhtml as well.

    For the benefit of the AeroGlass community, I've attached the complied script and source code in a Zip file.
    Installation Instructions:  1) Create directory:  C:\System\Scripts  2) Copy ChromeAutoLaunch.exe into this directory  3) Open Windows 'Task Scheduler' and import and save the ChromeAutoLaunch.xml task file.

    The scheduled task will run both at startup and every time the registered user logs in and will insert the switch(s) into the reg key before chrome starts.  If one manually exits Chrome, the shortcut used to relaunch (as mentioned previously) must also contain the additional startup switch(s).

    Feel free the edit the code (+task) and recompile it if you would like to customize either the script directory or the switches to be inserted.
    Cheers, -JT :cool:

    ChromeAutoLaunch_AHK.zip 434.23 kB · 46 downloads

    I am not sure if I am missing something or have done this wrong but I have tried this a few times and am not able to get it to function. Is there something I am missing?

    I see 4 files in the folder. One if the app for launch other is the script and the 3rd one is the icon and the last file I am not sure what to do with? does it all need to go into the same created directory as the EXE file? 

    Sorry if I am sounding dumb I just cant get this to work lol I have also imported the task and can confirm its there in the list. 

    I am on Chrome 76 with 1903 Windows  

    I also notched you said to make the scripts 2 directory but in the script it says just scripts. I have tried both folder ways and no luck lol  

    <?xml version="1.0" encoding="UTF-16"?>

    -<Task xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task" version="1.4">


    -<RegistrationInfo>

    <Description>Inserts switch: --disable-windows10-custom-titlebar Into Registry Key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run Value Modified: GoogleChromeAutoLaunch...</Description>

    <URI>\ChromeAutoLaunch</URI>

    </RegistrationInfo>


    -<Triggers>


    -<BootTrigger>

    <Enabled>true</Enabled>

    </BootTrigger>


    -<LogonTrigger>

    <Enabled>true</Enabled>

    </LogonTrigger>

    </Triggers>


    -<Principals>

    <Principal id="Author"> </Principal>

    </Principals>


    -<Settings>

    <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>

    <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>

    <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>

    <AllowHardTerminate>true</AllowHardTerminate>

    <StartWhenAvailable>true</StartWhenAvailable>

    <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>


    -<IdleSettings>

    <StopOnIdleEnd>true</StopOnIdleEnd>

    <RestartOnIdle>false</RestartOnIdle>

    </IdleSettings>

    <AllowStartOnDemand>true</AllowStartOnDemand>

    <Enabled>true</Enabled>

    <Hidden>false</Hidden>

    <RunOnlyIfIdle>false</RunOnlyIfIdle>

    <DisallowStartOnRemoteAppSession>false</DisallowStartOnRemoteAppSession>

    <UseUnifiedSchedulingEngine>true</UseUnifiedSchedulingEngine>

    <WakeToRun>false</WakeToRun>

    <ExecutionTimeLimit>PT1M</ExecutionTimeLimit>

    <Priority>7</Priority>

    </Settings>


    -<Actions Context="Author">


    -<Exec>

    <Command>C:\System\Scripts\ChromeAutoLaunch.exe</Command>

    </Exec>

    </Actions>

    </Task>

     

     

  5. On 7/31/2019 at 1:31 PM, JTB3 said:

    For anyone that's using AeroGlass with Chrome Browser (v76+) configured to startup with windows and run in the background, you've probably noticed that the command line switch --disable-windows10-custom-titlebar is NOT remembered at startup time.  Unfortunately, if you manually edit the ChromeAutoLaunch registry key, it will get overwritten every time Chrome exits.

    To address this issue, I created a simple AutoHotkey script that is run 'on login' as a Scheduled Task that automatically adds the necessary startup switch to the required 'ChromeAutoLaunch...' registry key (which has a custom suffix for different users).  I also added a 2nd useful switch --save-page-as-mhtml as well.

    For the benefit of the AeroGlass community, I've attached the complied script and source code in a Zip file.
    Installation Instructions:  1) Create directory:  C:\System\Scripts  2) Copy ChromeAutoLaunch.exe into this directory  3) Open Windows 'Task Scheduler' and import and save the ChromeAutoLaunch.xml task file.

    The scheduled task will run both at startup and every time the registered user logs in and will insert the switch(s) into the reg key before chrome starts.  If one manually exits Chrome, the shortcut used to relaunch (as mentioned previously) must also contain the additional startup switch(s).

    Feel free the edit the code (+task) and recompile it if you would like to customize either the script directory or the switches to be inserted.
    Cheers, -JT :cool:

    ChromeAutoLaunch_AHK.zip 434.23 kB · 19 downloads

    Big thanks to you on this. I got it to work again for a bit now it wont work again :(

     

     

  6. 16 hours ago, JTB3 said:

    Yes! - I have similar window/control refreshing issues related to the blur effect.  I'm running the latest FCU with an Intel i7-7700K using only the onboard graphics.  Several programs are now intermittently leaving residual artifacts on the desktop after the app windows close. Also, several of my installed programs (Like MindManager 2018) will not display the ribbon properly while Aero Glass 1.5.7 is running. These blur-related/refresh glitches are almost a show-stopper. Would really appreciate you looking into this @bigmuscle

    Mine did this a time or two and it was my video card driver after the update it never did it again. Not sure if this would be your problems as well just thought I would let ya know. 

×
×
  • Create New...