No Minimize/Maximize buttons in Gnome 3

Question

I'm having trouble figuring out the problem with the following code. I'm trying to change the prop animating on a ProgressBarAndroid, and make it toggle every second. The code works as intended if I set loading to true in my constructor, but not if it's set to false (which is what I want, I don't want it to start animating right away). When it's set to false, the progressbar stays invisible all the time. Any ideas?

import React, { Component } from 'react';
import { ProgressBarAndroid } from 'react-native';

export default class App extends Component {
  constructor(props) {
    super(props);
    this.state = {loading: false}; // works if it is set to true here instead

    // Toggle the state every second
    setInterval(() => {
      this.setState({loading: !this.state.loading});
    }, 1000);
  }
  render() {
    return (
        <ProgressBarAndroid animating={this.state.loading}></ProgressBarAndroid>
    );
  }
}

Solution

hm... Actually there's an option for minimize/maximize it's kinda hidden, when you click on nautilus top panel you get:

I'll add more solutions, when/if I find.

Comments

[Hamed Kamrava]

I know that, not interesting...

[JoKeR]

window placement has nothing to do with buttons:-)

[JoKeR]

so, I did some deep research including Gnome official sources, and currently it's not possible to do with Gnome 3.10+ only the way like on the screenshot, not even adding extensions will help you to add minimize/maximize buttons. Only if you install/replace to other file browser. I guess this be fixed but it's a question to Gnome developers.

[OdinRW]

I use native windows placement plus keyboard shortcuts and I never felt like I need these buttons :p I already said with Nautilus it can't be done in Gnome 3 ;)

[OdinRW]

Apparently your research is 3 hours late than my answer :p

[Ron]

A little explanation would be useful. What does the command do, why it will work..etc.

[Admin]

Yeah this works, although it does mess with the positions of other components a bit. Another dirty workaround I just found, which doesn't affect the position of other components, is to first set loading to true, but then by using a setTimeout with a delay of 1 ms immediately set it back to false.

[ReyHaynes]

@user2227486 That method works as well, it was actually my initial solution, but you'd have to continuously increase the delay based on how many moving parts are happening synchronously...and while I didn't have position issues you can control the position issue by styling View.

[trixn]

@user2227486 You do not need that 1ms timeout. Just put that into componentDidMount() because that will be called after the initial render.