Recommended Posts

hey guys, i jus finished my dock for desktop x, but i cant seem to make it auto-hide..

i have it set down the bottom of the screen, but when i open a window in full, it covers it, well i actually set it to be 'always on top' but i really want it only visible on the desktop so, what i want it to do is when i move my mouse cursor all the way down to the bottom, i want it to pop up..

anyway of doing this??? btw i am a desktopx n00b :D :D

oh and also, b4 i forget, is it normal for the animations to go on for more then they should? what i mean by this is, sometimes when i move over an icon in the dock, it bounces up and down a few times instead of one, like for a few seconds, is there a way to fix this or is this just normal??

thanx in advance guys... :D

Link to comment
https://www.neowin.net/forum/topic/40869-desktopx-dock-help/
Share on other sites

Originally posted by daoutlawz  

oh and also, b4 i forget, is it normal for the animations to go on for more then they should? what i mean by this is, sometimes when i move over an icon in the dock, it bounces up and down a few times instead of one, like for a few seconds, is there a way to fix this or is this just normal??

THAT my friend is the reason I deleted the dock 5 minutes after I installed it. I couldn't stand the erraticness. If there's a way to fix that, I'm all ears.

Link to comment
https://www.neowin.net/forum/topic/40869-desktopx-dock-help/#findComment-412103
Share on other sites

To get a dock to autohide is a long procedure involving animations, parent relations with objects and basically more than I want to go into. Maybe my autohide dock will be out soon and you can tear it apart and check it out. Otherwise, I suggest you hit the Stardock newsgroups; that's where I finally found the answer to the very same question.

I'm thinking that the new 'jitteryness' of the zoomer objects people are seeing with DesktopX 1.2 comes from a mix of the alpha blending and animation speeds. Let me explain;

If you have a zoomer with transparent areas those areas do not count as an activation area for mouseover. Think of any transparent holes in a zoomer as a "no mouseover zone".

When someone does activate a zoomer it grows larger, including the transparent areas. If a mouse crosses one of these areas as the zoomer grows during it's animation, then the mouseover animation stops and the mouseaway animation begins, causing the zoomer object to shrink. Once the mouse hits an opaque activation area the mouseover animation begins again, causing the zoomer to grow again, repeating the effect. So it appears the zoomer is jumping up and down.

I suggest adjusting placement of the zoomers in the animation frames to make certain that the mid center of an object contains almost no alpha blended (transparent) areas. If it does, take the .png into an image editor and fill those areas with black at a 20% transparency level and then re-save the .png animation.

Also, watch what speed you are setting your animations at. DesktopX 1.2 has a much, much faster engine running it now. I've found I've had to double my animation time in most cases. Animations that used to run fine at 15ms now move to fast to be seen, so I've upped the speed to 35ms.

Alot of this can also be fixed by limiting your size difference between a zoomers at rest state and it's final mouseover state. An object at rest with transparent areas that zooms to 4 or 5 times it's normal size is just asking for problems. Depending on the path of the mouse over an object you have a much greater chance of switching between mouseover opaque areas and mouseaway transparent areas.

Changing the mouseover area from "image shown" to another type has the potential to fix this problem, but in a dock like scenario this can create other problems.

Hope that helps.

Link to comment
https://www.neowin.net/forum/topic/40869-desktopx-dock-help/#findComment-414248
Share on other sites

Originally posted by daoutlawz

yeh, thanx m8, appreciate the help..

i should have jus emailed u.. :D :D

You should see my email inbox...something like 42 unanswered emails asking for help, themes, icons, wallpapers and other crap.

Hmmm, maybe I should answer some of them...

Link to comment
https://www.neowin.net/forum/topic/40869-desktopx-dock-help/#findComment-414391
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
    • OpenAI is making Codex more useful in Chrome and the cloud by Pradeep Viswanathan OpenAI's Codex now has more than 5 million users, up nearly 4x from earlier this year. To further accelerate Codex's growth among developers, OpenAI today announced that it has agreed to acquire Ona, a company that builds secure cloud execution and orchestration technology for developers. Ona will enable developers to run Codex with persistent and controlled cloud infrastructure for long-running agentic workflows. Right now, most Codex execution happens locally on developers' laptops and PCs, and the agents work continuously for hours. Through Ona, OpenAI aims to make Codex agents keep working for days without being tied to a user’s local machine or an active session. This will be an important capability for enterprises that want to deploy AI agents in production while maintaining control over infrastructure, data, security boundaries, credential scope, logging, and review workflows. Like any acquisition, the deal is still subject to customary closing conditions, including regulatory approvals. Until the deal closes, OpenAI and Ona will continue to operate as separate companies. After closing, Ona’s team will join the Codex team to improve developer workflows. Alongside the Ona acquisition announcement, OpenAI today introduced a few Codex updates. Developers can now save Codex rate limit resets and use them later instead of losing them when they are not needed immediately. OpenAI is also adding a referral option where users can invite a friend to Codex and get a saved rate limit reset. OpenAI today also announced a developer mode for browser use in Chrome and the Codex in-app browser. With this mode, Codex can use the Chrome DevTools Protocol to debug web apps, inspect pages, and work more directly with browser-based development workflows. Developers can use this when they want Codex to profile JavaScript, inspect console output and network traffic, examine web page states including the DOM and applied styles, and more.
  • Recent Achievements

    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
    • One Year In
      slackerzz earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      509
    2. 2
      PsYcHoKiLLa
      186
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!