I don't know if others are experiencing this, but unless minimized to the taskbar, UXPin consumes a lot of CPU even though it just sits in the background. Why is that?

The result of this "wasted activity" is a fan making noise like a roaming highway, a PC that runs slow in all other programs/apps, and a battery that's being drained (when not connected, obviously).

The CPU load is about the same on both my five-years old Surface Pro 4, and my two-years old HP 840GS, both with i7 CPU and 16GB RAM.

It is quite fine for UXPin to consume a lot of CPU when I'm actively using it (anything else is a pure benefit).  But when there is no activity, the program should just sit back and relax (once everything is synched online).

The funny thing is, when I minimize UXPin to the taskbar, CPU load from UXPin drops like a stone. But my activity with UXPin is identical in both scenarios: none.

So, UXPin: Can you please fix this performance bug?  Or rather, stop UXPin from being one...

Thanks.

Hi.

To make components useful as reusable things, please consider size override.

Nobody wants to make "all width versions" of a component for showing data in a particular way, right?

Hi.

I want to put a "page footer" in my prototype, and have it appear at the viewport bottom without knowing the browser window's height (or width, for that matter) when designing.

As it seems impossible to use "move to" with a calculated Y-position, I wonder if there is any other way to achieve this?

I tend to work on very complex prototypes with many interactions, and have double-digit years of experience from Axure. After half a year of experience with UXPin, one of the most time-consuming things I do (to make a prototype interactive) is to manually set up the same condition in order to do several things when the condition is met.

Imagine that you want to do three things when a condition is met. For example show an element (or change its state), update some content (because you want the user to feel that data follows his/her actions) and set a variable.  Currently, that involves creating three separate interactions with the same condition.  (And because of a bug, you may experience strange behaviour if you copy the interaction to save time setting up the condition, so you have to create each one from scratch.)

Now imagine that you have a second and third condtion, that should result in the same actions but with different content/behaviour.  Currently you are now working with no less than nine interactions, potentially "grouped" into three sets with if-else (to keep thing a little more organised).

And then you want to modify one of the three condtions.

It does work, but it takes a lot of time...

Hi all.

I want to change the font variant (weight) of a text in the prototype from an interaction (from "bold" to "regular" .  Is that possible?

I suspect it is not...